-
Notifications
You must be signed in to change notification settings - Fork 61
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
Compatibitlity Issue with iOS 8.1? #9
Comments
We found in the release notes |
As of iOS 8.1 / OSX 10.10, applications now longer create a resourcerules plist by default, meaning this code would be mostly invalid as a missing resourcerules.plist no longer indicates that the application has been tampered with. If you did want to add this in though, it can be done through going to Build Settings > Code Signing > 'Code Signing Resource Path' and adding '$(SDKROOT)/ResourceRules.plist' as the value. |
@Jordo96 That fix on debug. But is that going to work on production? |
Probably best to just remove the check from the code - after all, it is no longer really a definitive way to determine if the application has been compromised if it is no longer actually needed. If you still wanted to keep the check in the code, then I'm pretty confident it would work in production. |
@Jordo96 How confident you are? My app have been compromised straight after removing this check. Maybe I shall add an analytics event just to make sure before doing any serious action... |
This occurred after we migrated to iOS 8.1. However, I have not double checked whether this is really related to iOS 8.1
static NSString *str2 = @"ResourceRules.plist";
[manager fileExistsAtPath:([NSString stringWithFormat:@"%@/%@", bundlePath, str2])]
returns FALSE.
As a result the method isCracked returns true which causes a false alarm.
The text was updated successfully, but these errors were encountered: