Crash after resume
- [x] I have updated Purchases SDK to the latest version
- [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
‼️ Required data ‼️
Do not remove any of the steps from the template below. If a step is not applicable to your issue, please leave that step empty.
There are a lot of things that can contribute to things not working. Having a very basic understanding of your environment will help us understand your issue faster!
Environment
- [ ] Output of
flutter doctor - [ ] Version of
purchases-flutter - [ ] Testing device version e.g.: iOS 15.5, Android API 30, etc.
- [ ] How often the issue occurs- every one of your customers is impacted? Only in dev?
- [ ] Debug logs that reproduce the issue
- [ ] 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
I've just use Paywall feature and got many crash report message like this
There is no singleton instance. Make sure you configure Purchases before trying to get the default instance. More info here: https://errors.rev.cat/configuring-sdk
I think the issue happen when the user open paywall and leave the app. And when they comeback, the activity resume and have this issue.
To reproduce the issue you can enable "Don't keep activities" on Developer options. And then ope paywall in the app, leave paywall open and change to other app. When comeback you can see the issue or you can't close the paywall.
Additional context
Add any other context about the problem here.
👀 We've just linked this issue to our internal tracker and notified the team. Thank you for reporting, we're checking this out!
Hey @sonbui00 ,
Can you please confirm that you have configured the SDK before showing the Paywall in this instance? You might be able to confirm that from debug logs or stack trace of the crash report that you get. Once you get that information, can you please share it here so we can look further into it?
@michaelAtRC Confirmed. I can open Paywal and make purchase normally. The issue happen when I leave the Paywall open and change to other app in long time and come back, not when I open paywall first time.
Hi @sonbui00, Is this still happening with the latest version?
@nyeu my version: purchases_flutter: 8.1.0 Not yet upgrade to the latest version. And this is the log: issue_89f38a626f952d2f99e9acd3f13edffe_crash_session_66F6A394007E000148BCF49565B0731B_DNE_0_v2_stacktrace.txt
Hi,
I have the same issue in my flutter app, In the last 7 days I received 29 crashes for 29 different users. My version is : purchases_flutter: 8.1.0
You will find attached screenshots from my play store console.
To be honest it is urgent issue, I feel like I am losing a lot of users in my app due to this crash in the payment workflow.
Thanks
Hi,
I am getting the exact same issue and it is repeatedly logged on the crashlytics.
Environment:
purchases_flutter: 8.1.1
I have initialised the RevenueCat SDK when app starts.
here is the crashlytics stacktrace:
Crashlytics insights:
Hi all, would you mind sharing a code snippet on where and how do you configure the RevenueCat SDK? Thank you!
Hi @nyeu
here is the code where i have configured the RC.
first in main.dart file line number 74:
then in revenue_cat_manager_impl.dart line number 25 init method.
Hi all, we've debugged it and found the issue and the root cause. We are currently working on making a fix for it. Thank you a lot for the debug logs and for your patience! I'll let you know as soon as the fix is out.
Hi guys, there is any update on this.
I am experimenting same issue, I make anything I could, but still can find any fixing.
Hey @nyeu any update on this?
I am experiencing the same issue, I already raised the bug in separate thread and no one is answering... so Any update on this issue ?
Hi all,
We've released a new SDK version 8.4.2 with a fix for this issue.
Please let me know if that works or if you still find the crash!
Thank you a lot and I appreciate your patience.
Hey @nyeu thank you, going to do a deployment this week and will get back to you with the results.
@hamza-imran75 does the new update solve the crash ?
Update We have deployed to our users(50%) and it seems promising, the deployment was done on 23 Jan, and up till now we haven't received any errors for the above issue. I will still monitor and get back to this until we do a 100% deployment.
cc @nyeu
Hi @hamza-imran75, Thank you for letting me know! We've got reports from users saying that they no longer see the crash. I hope it's also fixed for all your users. Let us know if it's safe to close the issue.
Hey @nyeu i think we can close this issue now, we haven't gotten any bugs anymore.
Thank you very much.