-
Notifications
You must be signed in to change notification settings - Fork 210
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
Make sure mService exists when we call start or stop #17
Conversation
Ok, thanks. It will be merged. However this is just fixing symptoms. Fundamental question is why mService becomes null. |
I haven't got to time extensively test what exactly causes this, but I think it is because the current code doesn't account about the fact that the service could stop unexpectedly between the Also it is not accounted about the fact that |
Merged. Thanks. |
Origin-PR: mauron85/background-geolocation-android#17 Contributed-By: @ivosabev Fixes: #257, #280
Origin-PR: mauron85/background-geolocation-android#17 Contributed-By: @ivosabev
This handles the crash where mService has been killed or not initialized at all and the stop() method is called on a null value.
Examples: