You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are getting EXC_BAD_ACCESS crash, though it's not in sharedRunLoop and the stack trace doesn't have any detail.
It seems to only happen where we have Location permissions set to "Always" (set and used with a different LocationManager outside of MapBox) which is only a subset of our users. It happens sporadically, we haven't been able to nail down exact circumstances, other than when Location permissions are set to Always, and the app is backgrounded. The exception looks like:
Environment
Observed behavior and steps to reproduce
We are getting EXC_BAD_ACCESS crash, though it's not in sharedRunLoop and the stack trace doesn't have any detail.
It seems to only happen where we have Location permissions set to "Always" (set and used with a different LocationManager outside of MapBox) which is only a subset of our users. It happens sporadically, we haven't been able to nail down exact circumstances, other than when Location permissions are set to Always, and the app is backgrounded. The exception looks like:
com.mapbox.common.Unspecified Worker 1 (37): EXC_BAD_ACCESS (code=10, address=0x123ef4000)
The stack trace for the crashed thread is just:
#0 0x00000001047b3f2c in ___lldb_unnamed_symbol2102 ()
#12 0x0000000224c500ec in _pthread_start ()
I made a comment on #2236 but because the crash type seemed similar, but since it's on a different thread, I'm adding a new ticket as well.
The text was updated successfully, but these errors were encountered: