We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
On the latest beta version of flutter, dart errors are thrown when a purchase is requested.
I believe this may be due to this dart change with how Future<Null> is interpreted: dart-lang/sdk#37985
Future<Null>
E/flutter (13113): [ERROR:flutter/lib/ui/ui_dart_state.cc(148)] Unhandled Exception: type 'String' is not a subtype of type 'Null' E/flutter (13113): #0 MethodChannel.invokeMethod (package:flutter/src/services/platform_channel.dart:321:13) E/flutter (13113): <asynchronous suspension> E/flutter (13113): #1 FlutterInappPurchase.requestPurchase (package:flutter_inapp_purchase/flutter_inapp_purchase.dart:229:29) E/flutter (13113): <asynchronous suspension>
The text was updated successfully, but these errors were encountered:
Do you think you can help out giving any other PR?
PR
Sorry, something went wrong.
What was the motivation for some of the methods to return Future<Null> instead of Future? I believe this is the only change that is required.
Future
I have created pull request #117 which I believe fixes this issue.
Please test it however as I have only performed basic tests.
#116 changed Future<Null> to Future due to dart sdk change (#117)
7f00692
Amazon billing: Trigger purchaseUpdated callback when iap purchased (#…
51d4f6e
…165) * #116 changed Future<Null> to Future due to dart sdk change * Make amazon purchase trigger callback
No branches or pull requests
On the latest beta version of flutter, dart errors are thrown when a purchase is requested.
I believe this may be due to this dart change with how
Future<Null>
is interpreted:dart-lang/sdk#37985
The text was updated successfully, but these errors were encountered: