Fatal Exception: com.revenuecat.purchases.PurchasesException: [There was an unknown backend error]

[NickMelnykIronvest]

• [ ] I have updated Purchases SDK to the latest version (USED VERSION 8.16.0)
• [x] I have read the Contribution Guidelines
• [x] I have searched the Community
• [x] I have read docs.revenuecat.com
• [x] I have searched for existing Github issues

Describe the bug Crash for some users that comes from RevenueCat's SDK. Fatal Exception: com.revenuecat.purchases.PurchasesException: [There was an unknown backend error] See file for details

1. Environment

   1. Platform: Android
   2. SDK version:
   3. OS version: Android 9
   4. Android Studio version: Android Studio Meerkat Feature Drop | 2024.3.2
   5. How widespread is the issue. Percentage of devices affected. (~1%, 100% Samsung, 100% background)

2. Stacktrace: file

rc_issue_crash_stacktrace.txt

Additional context Issue reported at Jun 13, 2025, 2:03:07 AM Samsung Galaxy S10+, enough free RAM and disk space, non rooted

No reproduce steps and logs are limited, as not available in firebase crashlytics. Some users has also other crashed reported in firebase sharedInstance is accessed before initialisation, which according to my app logic should not happen in normal user flow, thus leads to conclusion that it could be result of some data tempering/fraud/hacking attempts.

[RCGitBot]

👀 We've just linked this issue to our internal tracker and notified the team. Thank you for reporting, we're checking this out!

[HaleyRevcat]

Hi, can you upgrade to our most recent 8.19.2 SDK and let me know if this fixes it for you?

If not then can you please share with me your code for configuring/logging in, firebase sharedInstance, and purchasing? And are you able to reproduce this on your end? If so RevenueCat debug logs would also be helpful, see our docs here for how to enable these.

[github-actions[bot]]

This issue has been automatically locked due to no recent activity after it was closed. Please open a new issue for related reports.