Giter Site home page Giter Site logo

Comments (5)

gabcvit avatar gabcvit commented on July 17, 2024 2

Hi @rorlf, I believe that this is not really a bug, it's rather a misunderstanding. Please have a look on the official in-app reviews documentation: https://developer.android.com/guide/playcore/in-app-review/test#troubleshooting

In this particular topic I linked it's stated that when:
The user has already reviewed the app., the in-app review won't show up. It would also not make much sense for the user experience to keep requesting for ratings to users that already rated your app.

EDIT:
For iOS, the dialogs will not keep showing up in a real scenario after the user rated the app, only when you're running it in a test environment. But that's the difference between Google and Apple and how they approach in-app ratings natively, not much related to the library.

from react-native-rate.

juliar avatar juliar commented on July 17, 2024 1

Hi @gabcvit , thanks for the response! I'm having this issue as well.

I agree it's better not to request a rating from a user that has already reviewed, however it seems there is no way to tell whether a user has already reviewed or not. So if we request a rating from a user that coincidentally has already reviewed, nothing happens, which is an unexpected user experience. It would be better to open the Play Store page instead, so the user could edit their existing review.

It would be helpful to at least know whether the in-app review prompt has appeared, although I'm not sure whether there's a reliable way to do that. Or if you know of a way to tell whether the user has already reviewed, that would work too. Thank you!

from react-native-rate.

KjellConnelly avatar KjellConnelly commented on July 17, 2024

Adding a bit of info to the README on this topic. Closing now.

from react-native-rate.

weraaaaz avatar weraaaaz commented on July 17, 2024

Is there any way to determine if the user has already reviewed?

from react-native-rate.

huntzinger92 avatar huntzinger92 commented on July 17, 2024

According to the current readme on the preferInApp option:

If true and user is on iOS, tries to use SKStoreReviewController. If true and user is on Android, it will try to use the native UI. If fails for whatever reason, or user is on another platform, opens the App Store externally.

And for openAppStoreIfInAppFails:

If preferInApp = true but the native iOS and Android UI failed, opens the store externally. Default true

I currently have the preferInApp and openAppStoreIfInAppFails options both set to true and neither the in app or play/app store navigation is happening, in precisely the manner described by @rorlf above. That seems to contradict the behavior described in the readme, which implies if the rate-in-app workflow fails, it will open the play/app store.

If that's correct, it would be great to update the readme to reflect this.

from react-native-rate.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.