react-native-in-app-review: Its not working

Hi i am using and invoke this in react hook

 useEffect(() => {
   // _referalid();
	 InAppReview.RequestInAppReview();
	
  }, []);

But its not working at all.

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 27 (11 by maintainers)

Most upvoted comments

I thought it was broken too at first on Android but after reviewing the troubleshooting docs (https://developer.android.com/guide/playcore/in-app-review/test) I realized that I was not using the primary Google account set on my device. To fix, go to Settings => Google => at the top hit the dropdown => select an account to be your primary, then ensure that you download the app with your set primary account. After doing that it popped up on my first try.

lol i already have done these above points. but your module is not working.

Read this carefully 👍 for testing => Test using an internal test track: Upload your app to the internal test track and install it on a device with a user account that has access to the internal test track. When using an internal test track, the following conditions must be met:

1 - The user account in the Play Store has downloaded the app from the Play Store. When this is the case, the app is listed in the user’s Google Play library. 2- The user does not currently have a review for the app. 3- The quota has not been reached.

After the account on the device has downloaded the app at least once from the internal test track and is part of the testers list, you can deploy new versions of the app locally to that device (for example, using Android Studio).

RECOMMENDED: Test using internal app sharing: Alternatively, for rapid iteration you can use internal app sharing to test your integration. This method lets you quickly test changes by skipping some of the verification that happens with other test tracks.

Important: When using an app installed with internal app sharing, reviews can’t be submitted. To emphasize this difference, the button is disabled in the UI.


  • OR Publish your new release to production after integration, to trigger UI

without one of 3 options above, UI will not triggered.