-
Notifications
You must be signed in to change notification settings - Fork 734
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
iOS 11 problem with opening app page in the App Store #302
Comments
Is this using the latest version of iRate? The URL changed recently. |
I tried it an hour ago, updated to the version 1.12.1 via Cocoapods |
I use version 1.12.1 via Cocoapods and confirm. |
The URL seems not to work anymore with the |
I confirm this is an issue. Even using the https-based URL (e.g. https://itunes.apple.com/app/blabla/idXXXXXX?action=write-review) fails to load. The documentation is still suggesting to use In the meantime, apps should not open the “write review” URL on iOS 11, just the basic App Store link. |
I confirm I have the same issue on the iOS 11 GM seed. How can we fix this? |
|
Update: First, sorry my bad, I had locked iRate below version 12 in my podfile. Fixing that, I think I know what was going on. I probably locked iRate below 12 in order to avoid the iOS 10.3+ way of opening the in-app rate alert (I don't remember the reason for this, but hey). In my app I had two cases where I used iRate.
Now, the So at this point, I assume that for me, 1 should work if I use the latest iRate, and 2 will work if use |
Okay, I guess even that's not the end of the story. I thought twice and thrice and I guess case 2 above is a no-go since iOS 11.0 (or probably also since 10.3, in a way). First, it doesn't make sense to prompt the user in the same way in 2 as I do in 1, I'd want to open the review page below 10.3 and open the in-app SKStoreReviewController from 10.3 and up. However with the current iRate there is no way to do that, unless possibly if we fix it so we can call But the discussion doesn't end there because on iOS 10.3+ that would ultimately call https://developer.apple.com/documentation/storekit/skstorereviewcontroller/2851536-requestreview which, as is stated in the docs, might or might not open the review UI. Which is in terms with how Apple wants the review experience to work... I guess I will have to advocate to my director to remove case 2 and only use case 1 above - rate upon some rare user interaction. Also in the long run I guess Apple is specifically wanting to shoot down iRate and similar libraries that show review popups. |
A workaround is to include a two-letter country code and app name in the URL, such as this:
The full URL for your app can be obtained from https://linkmaker.itunes.apple.com/ This successfully opens the "write a review" interface in the iOS 11 App Store. This workaround is not ideal however as changing the app title would also change its URL, thus breaking the workaround. Hopefully Apple will fix this soon for the shorter URL. See rdar://34498138 |
The country code and app name must be present in the URL but are ignored - only the ID needs to change. Also
Tested on iOS 11.0 (15A372). |
^ That one really works... so for a fast fix, I guess I could go with it if iRate was updated with this. Will iRate be updated or will I have to fork this? 🙄 |
Maybe you can fork, and offer a pull request 😉 |
@zapjonny you can override the URL without forking iRate by adding this to your setup code:
|
@nicklockwood Good one! It works ✌️ |
Can confirm workaround to be working, thanks |
Confirmed. Thanks |
Thanks @neave. This works! |
OK. And this also works on iOS 10 I just tested. |
@dpa99c |
Hi guys,
when using this code:
[[iRate sharedInstance] openRatingsPageInAppStore];
The app opens the app store but the message stands "Verbindung zum App Store nicht möglich" (I think the english translation is Can't connect to App Store)
The app already exists on the app store, and this code worked for the previous iOS versions.
P.S. I assume this is expected since Apple changed the whole App Store in iOS 11.
The text was updated successfully, but these errors were encountered: