Appirater - A utility that reminds your iPhone app's users to review the app.

Hi,

the app works without problem, however when sending to App Store, I get this error.

I am using Apppirater as part of my project workspace using cocoapods. Any hints?

Thanks!

Jindrich

Though the link still works on iOS 6, iOS [REDACTED] redirects to a blank page. Do you think this is temporary, or is Apple removing the direct link to the review page?

Hi,

Starting from iOS 6, it's possible to show an iTunes controller within the app with the SKITunesProductViewController class.

I believe this could be used to rate the app. This means the user wouldn't need to abandon the app being rated in order to rate it.

Implementing this wouldn't be trivial, since we need to push the view controller. I believe we would need to make some changes to the delegate protocol:

1. We need to get the view controller that will be used to push and dismiss the modal controller. If the user doesn't implement this delegate method, we may fall back to jumping to the iTunes URL.

2. We need to let the delegate know when we're pushing a view controller (e.g. so a game can pause) and when we're dismissing it (e.g. so a game can unpause).

3. We may need to ask the delegate if we should push with animations enabled or not, as pushing with animations can be troublesome in some (rare) cases.

Thoughts?

Regards,

Issues

When using Appirater via CocoaPods, the lproj directories are copied to the root of the main bundle. This causes two issues:

1. They conflict with any localization in the main app.
2. The App Store detects these localized bundles and assumes the app is fully localized into all 25+ languages Appirater supports. These Google results suggest this affects more than 1000 apps.

Solution

CocoaPods recommends setting spec.resource_bundles instead of spec.resources to avoid the collision from issue 1. To support this use case, the code checks if Appirater.bundle exists. If it does, it uses the string table from that bundle. If it doesn’t exist, which will be the case if the developer is using Appirater via a submodule or other method, then the main bundle will be used, as it is today.

Caveat

This is not backwards-compatible for users who have provided custom strings via their own AppiraterLocalizable.strings. These users must call the new method [Appirater setAlwaysUseMainBundle:YES]. To maintain semantic versioning, Appirater’s major version number should be incremented (e.g., it should become 2.0) after this is merged.

Note for those wishing to work around the second issue before this is merged.

You can use the Podspec from this pull request locally:

pod 'Appirater', :podspec => 'Vendor/Appirater.podspec'

You’ll need to manually create/copy AppiraterLocalizable.strings to any localized bundle(s) you have.

If the UIAlertView is present and the user moves the app to the background, Appirater gets stuck in a vicious circle of briefly presenting the alert and then dismissing it.

As a brute force measure, I am simply cycling through subviews from applicationDidEnterBackground: and calling dismissWithClickedButtonIndex: on the UIAlertView. This works for my particular implementation, but is obviously not safe for everyone.

My app is swift based 9.0, installed Appirater via cocoapods. Have this code in my AppDelegate:

    Appirater.setAppId("106037XXXX") //replace X's with last 4 digits just for here
    Appirater.setDaysUntilPrompt(2)
    Appirater.setUsesUntilPrompt(10)
    Appirater.setSignificantEventsUntilPrompt(-1)
    Appirater.setTimeBeforeReminding(2)
    Appirater.setDebug(true)

Code is definitely executed, but no popup appears. Tried both on simulator and actual device. Any ideas?

Thanks

This is great opportunity for Appirater to show new native dialog instead of sending to AppStore devices driven by iOS 10.3 or higher.

https://developer.apple.com/library/prerelease/content/releasenotes/General/WhatsNewIniOS/Articles/iOS10_3.html

it goes to details page rather than review page, below one works for me.

@"itms-apps://itunes.apple.com/WebObjects/MZStore.woa/wa/viewContentsUserReviews?id=APP_ID&onlyLatestVersion=true&pageNumber=0&sortOrdering=1&type=Purple+Software"

Hi, I just integrated Appirater with Cocoapods but the localized version of the dialog box does not appear when I have my device's language set to Chinese or Italian (that is what I tested).

Is there something we need to do to make sure the localized versions are used?

I see the localizations being copied into the Appirater.bundle in the build log.

When we integrated this before Cocoapods, my coworker had to modify the .h file to use his own version of NSLocalizedString.

Hello,

I installed appirater with cocoapods (pod 'Appirater', '~> 1.0.1') but the localizable files are not present. Am I missing something?

Thanks

This commit adds support for installing this library via Carthage by adding this line (once merged & new release published):

github "arashpayan/appirater" ~> 2.1

Until it's merged you can use my fork with this line instead:

github "Dschee/appirater" "master"

I am investigating on a crash happening in appirater. Firebase lists it as: -[Appirater incrementUseCount] + 434. If we assume that the stacktrace is accurate, it shows this line:

if (_debug)
     NSLog(@"APPIRATER Use count: %@", @(useCount));

Before we call Appirater.appLaunched(true) we are setting Appirater.setDebug(false) on a main thread. Looking at the code, I can see that static variable _debug is used without any thread safety around it.

BTW, this only happens to 0.03% of our users so chances of reproducing that are fairly low :)

When turning debug mode on with [Appirater setDebug:YES] then [Appirater appLaunched:NO] always shows the rating dialog; ignoring the canPromptForRating parameter that is set to NO here. I expect the dialog to be NOT shown in this case.

Currently, if setOpenInAppStore is set to true, if the user is on iOS 10.3 or above, it still uses the StoreKit's alert. This PR will change that and show the Appirater alert if the user has chosen setOpenInAppStore to be true.

Also, this PR adds two more delegate methods to AppiraterDelegate.

• -(void)appiraterDidDisplayAppiraterAlert:(Appirater *)appirater; Will tell if the AppiraterAlert was shown.
• -(void)appiraterDidDisplayStoreKitAlert:(Appirater *)appirater; Will tell if the StoreKit alert was shown.