Status Update
Comments
ca...@google.com <ca...@google.com> #2
Thank you for posting.
We have logged this issue internally. Please note that we cannot give you any timelines, but you can star the issue to get notifications.
as...@google.com <as...@google.com> #3
#1: the stack trace file that you attached doesn't contain the string "com.google.android.libraries.navigation.internal.xf.at.l" or "java.lang.IllegalStateException - Trying to call onSurfaceCreated with no current context". Could you please double checK?
be...@goflink.com <be...@goflink.com> #4
you are correct though it does contain com.google.android.libraries.navigation.internal
with different variants as I have attached the title I copied from Crashlytics.
as...@google.com <as...@google.com> #5
Thank you. Looking at the stack traces in #4:
- Crash in variant #1: is it possible that this occurred on your app version that uses Nav SDK 5.5.1? If yes, then this is the same as variant #3.
- Crash in variant #2: we are investigating.
- Crash in variant #3: we have a fix coming in the next patch version.
be...@goflink.com <be...@goflink.com> #6
- yes, I believe it was version 5.5.0
- perfect thanks a lot
- when are the patch fixes usually merged with the main releases? sometimes I find some fixes in versions for example
5.5.1
but not in6.0.0
or isn't that true? Are they always updated with all the fixes?
as...@google.com <as...@google.com> #7
The issue in variant #1 and #3 is fixed in version 6.0.1 (and also 5.99.1):
Once you adopt this version, could you please monitor if crash variant #2 still occurs? If yes, please file a new issue.
About fixes: if a bug exists in version 5.x and 6.x, usually we will fix both versions. Our policy is at
Description
Hey guys after updating the
com.google.android.libraries.navigation:navigation
library to version6.0.0
, we started getting an increase in the crash rate of the app caused byI have attached the full stack trace