This is causing an exception on many devices after A2DP volume targets API26. I need to figure out a solution for this when I get time.
The new background execution limits are also likely the cause of the app being stopped, not capturing location, not responding to connect/disconnect, etc. Investigation is needed to understand how to propelry handle the new execution limits and changes in this app.
Android made changes for API 26 that makes the starting of a service different. https://developer.android.com/about/versions/oreo/android-8.0-changes#back-all
Here is another app dealing with the same issue: https://github.com/mapbox/mapbox-events-android/pull/157
This is causing an exception on many devices after A2DP volume targets API26. I need to figure out a solution for this when I get time.
The new background execution limits are also likely the cause of the app being stopped, not capturing location, not responding to connect/disconnect, etc. Investigation is needed to understand how to propelry handle the new execution limits and changes in this app.