(In reply to Chris Peterson [:cpeterson] from comment #3) > > please check your proguard rules. > If your rules are in order, but some users still see the crash, it's likely to be an Android-specific issue and it's worth reporting to Google issue tracker > > Do we use ProGuard, Redex, or any other dex optimizers that cause symbol-renaming issues like this? Yes, we should look into ensuring that we are using the appropriate keep rules to avoid this crash. This happening in the same release and API version 21 as bug 1844964 is suspect that we are suffering from another root cause that is masked by these two different crash reports.
Bug 1851704 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Chris Peterson [:cpeterson] from comment #3) > > please check your proguard rules. > If your rules are in order, but some users still see the crash, it's likely to be an Android-specific issue and it's worth reporting to Google issue tracker > > Do we use ProGuard, Redex, or any other dex optimizers that cause symbol-renaming issues like this? Yes, we should look into ensuring that we are using the appropriate keep rules to avoid this crash if possible, however, this happening in the same release and API version 21 as bug 1844964 is suspect that we are suffering from another root cause that is masked by these two different crash reports.