The output of 'CheckAppReviewPlugin.IsAvailable' is false, and hence I am unable to use this plugin.I am using an APK file and testing it in the android device and not in browser. This post is related to O11, not ODC.
Hi @Bala Subramanian
As I mentioned in the new documentation, in order to demo this, the app identifier that you generated must be from an app in the Play/App Store. Otherwise, you can only test this in your production in-store app.
Steps to achieve the InAppReview dialog for demo purposes:
If you have any other questions, please let me know.
Best regards,Paulo Solipa
Dear,
I checked that plugin support commends , its not working long before
but can you make sure the GitHub path was correct in your application/plugin
https://github.com/chemerisuk/cordova-plugin-app-review.git
or please share the OML i will test from my end
The app review plugin is still using the mentioned URL.
Hello there.
The Possible Causes & Fixes:
1. Ensure You Are Testing on a Real Device (Not Emulator or Browser)
• The App Review Plugin does not work in a browser or emulator.
• Install the APK on a physical Android device and test again.
2. Check If Google Play Services Are Installed & Updated
• The plugin relies on Google Play Services to function.
• Go to Settings → Apps → Google Play Services and update if needed.
3. Confirm That the Plugin Is Installed Correctly
• Open OutSystems Service Studio.
• Go to Forge → Installed Plugins and ensure App Review Plugin (O11) is added.
• If not installed, install or update it from Forge.
4. Verify Permissions in AndroidManifest.xml
• The plugin might require specific permissions in AndroidManifest.xml.
• Ensure the following is present:
<uses-permission android:name="com.google.android.gms.permission.ACTIVITY_RECOGNITION"/>
• If permissions are missing, manually add them in OutSystems Mobile settings.
5. Check for Any Console Errors (ADB Logs)
• Connect the device via USB debugging and use Android Logcat to check errors.
adb logcat | grep "AppReviewPlugin"
• Look for errors related to missing dependencies.
6. Test with a New APK Build
• Sometimes, OutSystems may not bundle plugins properly.
• Try:
1. Deleting the old APK from the device.
2. Rebuilding the APK in OutSystems.
3. Reinstalling the APK on the device.
7. Verify Minimum Android Version
• The Google In-App Review API requires Android 5.0+ (API level 21).
• Check your device’s OS version and update if necessary.
8. Try a Different OutSystems Version
• If using OutSystems O11, ensure you have the latest service updates.
• Check the Forge page of the plugin to see if it supports O11.
Final Fix
• If none of the above works, try removing the plugin, reinstalling it, and rebuilding the APK.
Happy coding
I attached my OML file @Vignesh Sekar
A new version of the plugin will be uploaded to the forge today.
I will let you know once it's there.
Best regards,
Paulo Solipa
hi @Pankaj pant ,
This what I have used in the Extensibility config. I am still getting error only. Can you help on what might be the issue?
{
"plugin" : {
"url":"https://github.com/chemerisuk/cordova-plugin-app-review.git" },
"preferences": {
"AndroidPermissions":
[
"android.permission.WRITE_EXTERNAL_STORAGE",
"android.permission.READ_EXTERNAL_STORAGE",
"android.permission.ACTIVITY_RECOGNITION"
] }}Error:
Hi @Bala Subramanian,
I've identified the issue and the new version of the plugin will be deployed to forge in 1 hour.
A new version of the App Review Plugin is now available on forge, with demo, documentation and with the correct implementation.
If you experience any problems, please let me know.
Thanks Paulo.
Hi team,
@Paulo Solipathanks for the quick solution. I am using the newly created component from Forge and created a new application to try this. When i tried to use the
InAppRequest action with the Instagram package name, I got the below error.
Note: I did not add anything in the extensibility configuration.
Error:
Logic:
Let me check real quick.
I will get back to you in a few minutes.
Thank you for the help in correcting this issue.
One small issue was identified and new version 1.0.1 was released to forge.
I also added some documentation on how the InAppRequestReview action can be triggered without being in a App/Play Store app.
If you experience any more problems, please let me know and I happily help.
Hi,
I tried to open the gmail, youtube, whatsapp app's by passing the package name, but none opened the In App review. I also tried the package name of the app which I am trying as a demo app. Still that did not open too. There is not an error also.I'm not sure what went wrong this time. If anybody could help, I appreciate it.
Thanks in advance!
Thanks a lot team!This works now after i tried using Instagram's id (I realized we can not open TikTok in our region).I have added one more step to Open the Store screen on failure of InAppReview. Hope it might be useful to others.
Just adding one more point.
I tried the first time and it opened the popup as expected.
But I tried after a while, and I'm unable to view this InApp popup after the first time. Is there any condition or limitations on how many times the popup displays?
If so, how can we find out whether the In-App popup is not displayed or not (since the Review action gives Success)?
No worries at all.
So what happened there is that the InAppReview for Android has a time bound quota defined by Google which ensures that the InAppReview dialog is not shown everytime to the user. Additionally, the same thing happens for iOS where the review prompt is limited to three times a year. The data of the implementation by Google and Apple is not available to the public, can be changed at any time by them and it cannot be adjusted by developers.
TLDR; once its shown for the first time, there will be a sort of cooldown period until it shows again.
Thanks, Paulo.
I understand that we have no way of knowing whether the popup was displayed or if the user actually submitted a rating when it appeared.
Is that correct?
Yes, that's correct. Whether you are in a native app or hybrid Cordova app like OutSystems, the behaviour is that one.