-
Notifications
You must be signed in to change notification settings - Fork 234
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
Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[NSNull length]: unrecognized selector sent to instance 0x1fbabb5b0 #495
Comments
I'm running into the same issue within my app and have traced the problem to the following (I believe only impacting users on iOS 18.2): obfuscatedAccountId is null, but placing a string here will prevent the crash. Does anybody know if putting a random string here will impact restore purchase later on?
|
I'm facing the same issue. Has anyone found a solution? |
this issue happen only on IOS 18.2 ( it doesn't appear on previous version like IOS 18.1 ) , is there any up coming fix ? |
We are currently facing this issue as well only on 18.2. Any planned fix ?? |
This issue occurs on devices running iOS 18.2 when calling You can safely assign a unique value, a placeholder, or simply an empty string ( Fix:To resolve the issue, pass an empty FlutterInappPurchase.instance.requestPurchase(productId, obfuscatedAccountId: ""); |
Version of flutter_inapp_purchase
flutter_inapp_purchase: ^5.6.1
Platforms you faced the error (IOS or Android or both?)
IOS
Expected behavior
Ran this code:
Actual behavior
The app crashes, I couldn't catch
Error information:
App info:
Process Data:
Memory:
Duration:
Device:
Device Information:
Battery:
Memory:
Timestamp:
Tested environment (Emulator? Real Device?)
Only in production, is in just one user. That happened after he open the app and try to buy a subscription after download. And the user tried another 4 times and had the same error
Steps to reproduce the behavior
I couldn't, do you know where could be the error here? Thank you
The text was updated successfully, but these errors were encountered: