-
Notifications
You must be signed in to change notification settings - Fork 236
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
Crash SharedPrefKeysetReader #604
Comments
👋 Hello @DmitriiBroli - do you have steps to replicate? |
@scannillo Hi, no steps unfortunately, this is a Crashlytics crash. |
Hi @DmitriiBroli we have an issue with our 3rd party MPI provider Cardinal that prevents us from providing explicit support for API version 33. I'm guessing this issue may be related, although it is hard to tell without steps. We appreciate the stack trace though that is helpful. Is the crash frequent? Also you can follow along with #585 once this is resolved we'll release a new minor version update to include explicit support for Android 13. |
Hello @DmitriiBroli - We believe this has been fixed by our 3rd Party MPI Cardinal. The fix has been released in version 4.18.0. Are you able to test again as we were not able to reproduce this after updating and confirm if you are seeing this issue resolved? |
Hi, the crash still persists. Additionally, we also noticed StrictMode violations from braintree side:
|
@DmitriiBroli thank you for your patience. We have a PR up. After looking at this stack overflow post, it looks like we may benefit from explicitly providing an encryption key alias. Once we have it merged it, it may help us if you could verify that our SNAPSHOT build fixes the issue and if so, we can add it to the next release. |
Hey @DmitriiBroli can you try version |
@sshropshire Thank you for your time. We have updated to 4.19.0 and we will check out whether this helped after releasing to prod. |
@DmitriiBroli issue has been fixed in latest version 4.20.0. In order to avoid a crash, you need to catch |
General information
Issue description
Crashlytics crash
The text was updated successfully, but these errors were encountered: