App Crashes When Restoring Purchases in PaywallFooterView

[enoiu]

• I have updated Purchases SDK to the latest version
• I have read the Contribution Guidelines
• I have searched the Community
• I have read docs.revenuecat.com
• I have searched for existing Github issues

Environment

• Output of flutter doctor

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.22.2, on macOS 14.5 23F79
    darwin-arm64, locale ja-JP)
[✓] Android toolchain - develop for Android devices
    (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.4)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2023.3)
[✓] VS Code (version 1.90.0)
[✓] Connected device (5 available)
[✓] Network resources

• No issues found!

• Version of purchases-flutter

  purchases_flutter: ^6.29.3
  purchases_ui_flutter: ^6.29.3

• Testing device version e.g.: iOS 15.5, Android API 30, etc.
  Android 12 (API 31)
• How often the issue occurs- every one of your customers is impacted? Only in dev?
  one customer
• Debug logs that reproduce the issue
  This crash log was not found in the Google Play Console
• Steps to reproduce, with a description of expected vs. actual behavior
  Other information (e.g. stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc.)

Describe the bug

A customer using my app reported that the app crashes when they press "Restore Purchases." They also sent a video of the incident.

Upon reviewing the video, I noticed that despite the app's language being set to English, the purchase button (call to action) was in German.

(Additionally, the customer uses Korean as the device language, but my app does not support Korean, so it defaults to English. Similarly, in the RevenueCat Paywall editor, I have set up localizations for languages like English and German, but not Korean.)

In my environment, pressing the restore button does not cause any issues on either the emulator or my devices (Android 14, Fire 7 12th generation), regardless of whether there is purchase information or not.

Therefore, I suspect that the app crash might be related to a discrepancy in the purchase information. Unfortunately, there are no crash logs related to this in the Google Play Console, and I am unsure how to reproduce this issue in my environment.

Additional context

• My app uses PaywallFooterView.
• My app offers non-consumable in-app purchases.
• The customer had already purchased the non-consumable item on their smartphone and encountered this issue when trying to restore the purchase on their tablet.
• I had the customer reinstall the app, but the issue was not resolved.
• I tried setting the device language to Korean on the emulator and tested "Restore Purchases," but the issue did not occur (the Google Play region is Japan).

[RCGitBot]

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

[vegaro]

That's very strange indeed, we haven't had any reports of anything like this happening before. Do you have by any chance the stacktrace so we can take a look? You may be able to find that in the Play Console Quality > Android Vitals section.

This is the official guide on crashes on Google Play.

Thank you!

[enoiu]

Thank you for your response.

I checked the Play Console's Quality > Android Vitals again, but I did not find any logs related to this issue.

Moving forward, I plan to integrate firebase_crashlytics into the app and ask the customer to reproduce the issue again.

[enoiu]

After integrating firebase_crashlytics and asking the customer to press "Restore Purchases" again, I received a report that the restore function was working.

However, it seems there was a mistranslation by Google Translate, and I received a correction stating that the issue has not been resolved.
Additionally, even though firebase_crashlytics was integrated, I could not find any crash logs related to this issue in Firebase and Play Console.

The user is using a device called TAB910, which might be causing the problem.

Without the crash logs, resolving this issue will be difficult.
Therefore, I will close this issue and refund the customer.

If there is any prospect of resolving this issue, please reopen.

Thank you.

[vegaro]

Thank you @enoiu for understanding that it would be hard to solve without a stacktrace. If you ever get an stacktrace please don't hesitate to open an issue so we can take a look. We'll keep an eye out to see if we see this happening to anyone else.

Thank you