-
-
Notifications
You must be signed in to change notification settings - Fork 24
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
App Crash with IReviewManagerInvoker.RequestReviewFlow () Exception (Android) #20
Comments
@darrabam Whats the Android version on those devices? The error says Also, do you have a proguard file in your project? Whats the build configuration for it? |
@saamerm No, I don't use proguard for my project. These are my build settings: |
Are you sure that's the release project configuration? I don't believe you can publish an app with Shared Mono Runtime enabled |
@saamerm sorry, you are right, this is the one: |
If you use proguard or r8, you need to have a proguard file for now so that the shrinker you are using to reduce the size of the APK file doesn't delete those classes. Please follow the instructions in the readme to add a proguard file and publish a build with that. I highly recommend that you test the In-App Review using "Android Internal App Sharing" before you publish |
@saamerm thanks for the hint, I'll try that. |
Any success @darrabam |
@saamerm yep, it worked! at least I got the rating dialog and managed to submit a review without a crash :) |
@darrabam you mean without a crash? |
Hi there,
I'm noticing many crash reports logged in my App Center Issues for Android:
Details:
Bug
Version Number of Plugin: 3.0.0-beta
Device Tested On: Galaxy S8+, OnePlus 6 , Device, Y9 Prime 2019, and others
XF: 4.8.0.1560
Steps to reproduce the Behavior
I show the dialog by calling the request review
await Plugin.StoreReview.CrossStoreReview.Current.RequestReview(false);
Note that the application language is Arabic.
I don't have a physical device in order try to reproduce it, but I wonder if you could get a hint from the log on what could be the issue.
Thanks,
The text was updated successfully, but these errors were encountered: