👁 Image
Oscore.Maui.InAppReviews 1.3.0

Maui.InAppReviews

👁 Nuget package
👁 CI/CD
👁 License: MIT

NuGet package that implementing native In-App Reviews for MAUI with debugging capabilities.

You also can use AppStoreInfo to open review page in the store.

Supported Platforms

Usage

• Add NuGet package to your project:

<PackageReference Include="Oscore.Maui.InAppReviews" Version="1.2.0" />

• Add the following to your MauiProgram.cs CreateMauiApp method:

builder
 .UseMauiApp<App>()
+ .UseInAppReviews()
 .ConfigureFonts(fonts =>
 {
 fonts.AddFont("OpenSans-Regular.ttf", "OpenSansRegular");
 fonts.AddFont("OpenSans-Semibold.ttf", "OpenSansSemibold");
 });

ReviewStatus status = await InAppReview.Current.RequestAsync();

Links

• https://developer.android.com/guide/playcore/in-app-review
• https://github.com/jamesmontemagno/StoreReviewPlugin
• Requesting Reviews with iOS 10.3’s SKStoreReviewController
• In-app reviews for your Android apps

Testing & Debugging issues

iOS

• You cannot submit a review on iOS while developing, but the review popup dialog displays in your simulator/device.
• However, when you download the app from Testflight, the popup dialog does not display at all, as mentioned here:

When you call this method while your app is still in development mode, a rating/review request view is always displayed so that you can test the user interface and experience. However, this method has no effect when you call it in an app that you distribute using TestFlight."

Android

• Unlike iOS, you cannot see the review popup dialog while developing or if you distribute it manually. As you can see here, you have to download the app from the Play Store to see the popup. I recommend using Android Play Store's “Internal App Sharing” feature to test.
• Occasionally, some devices may not show the popup at all as seen here. One way to test whether your device is affected by it, is by downloading this game that uses v3.1 of this nuget, target SDK version 30, target framework v11.0 and win the game once to see the popup. Additionally, you can debug the error using adb locat, as you can see here
• The most common issue/crash type is that developers release the app in the release configuration but they only test in the debug configuration. They do not realize that they have set Linker behavior to Link SDK assemblies only/Link all, and did not follow the proguard steps mentioned above