Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

current use of background-tasks leads to crashes #13

Open
bluegaspode opened this issue Jan 16, 2011 · 0 comments
Open

current use of background-tasks leads to crashes #13

bluegaspode opened this issue Jan 16, 2011 · 0 comments

Comments

@bluegaspode
Copy link

You currently use background tasks without expiration handlers.
If a background task expires while the App is in the background, it will be killed by iOS (from my observations it seems like this happens only after 24hours - or when the App is restarted later on)

From the documentation of the expirationHandler:

"A handler to be called shortly before the application’s remaining background time reaches 0. You should use this handler to clean up and mark the end of the background task. Failure to end the task explicitly will result in the termination of the application. The handler is called synchronously on the main thread, thus blocking the application’s suspension momentarily while the application is notified."

Futhermore it should be enough to start exactly one background task when the Queue is stopped. While playing the App will not be suspended (if the App declares 'audio' as it's background mode).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant