• State Not Answered
  • Replies 4 replies
  • Subscribers 20 subscribers
  • Views 431 views
  • Users 0 members are here
Options
Related

REVIEW_REQUEST_STATUS_DENIED

janjanousek
over 1 year ago

I am trying to implement WatchUi.makeReviewTokenRequest(). Everything seems to be working, but after I rejected the review once on the watch, I am no longer able to request review. I always get ReviewRequestStatus "REVIEW_REQUEST_STATUS_DENIED". And even after possibly updating the application to a newer version. When I uninstall the app and install it again it is the same (always get REVIEW_REQUEST_STATUS_DENIED).

Is there any way to request a review again? Is there a more detailed description of how it works? I think that at least after some time the request should show again even if the user canceled it before.

  • 0 over 1 year ago

    I see your point and it makes sense but if I look at the side of the user: If I deny a review, do I want to be bothered with this request again? If the user really wants he can still do a review via the connect iq app if he really would want to do this, no?

    The documentation mentions that also a time frame is taken into consideration. "The app store validates a number of factors, including if you have recently requested a review from a user"  

    It does not menion how long this timeframe is, so the question is have you waited long enough before you do the request again.

    (I haven't tried this api myself as I'm not a fan of requesting reviews/ forcing reviews. i also think this api will only allow to do a review without textual feedback. Getting reviews without textual feedback provides no benefit to improving the quality of the app) 

  • 0 over 1 year ago in reply to peterdedecker

    The problem is that you don't know why the user declined. Did he hit the wrong button by mistake (happened to me), doesn't have time right now, etc.?

    The fact that there is another option for the user to create a review is nice. But the problem is that a user who is satisfied has no reason to spend his time looking for a way to create the review. On the contrary, users who are dissatisfied have an incredible need to express their dissatisfaction. I have several applications (not only for Garmin) and it's always the same, users who are satisfied almost never write a review. Dissatisfied yes, so at first glance it looks like the application is completely unusable.

    I agree that it is good to limit the number of rating requests so that the user is not outright forced/annoyed.

    But as I mentioned, the rating request is not showing again even after uninstalling and reinstalling the app. It is also not displayed after updating to a new version of the application. And I couldn't even get it to show again after 2 days (as you mentioned, the documentation doesn't mention any time).

    In my opinion, the request should appear again (if requested by the programmer):

    • After reinstalling the app.
    • After updating to a new version.
    • If it hasn't already been shown x times ("x" should be at least 2, but that's up for debate).
    • At least once a week.
  • 0 6 months ago in reply to janjanousek

    Does anyone have any tuning recommendations on when to request a token? 

    On my own device during testing with fully deployed non-beta apps (and having never seen the prompt before), I'm getting "REVIEW_REQUEST_STATUS_DENIED".  So I'm wondering if my app is requesting the review token too soon after launch or install or some other issue.

  • 0 6 months ago in reply to janjanousek

    Asking for a review once is obnoxious enough.

    (“Once a week” is a request to uninstall it.)