Tagged: music app
iTunes Connect error -22421 solved!
Submitting and app to iTunes Connect without errors is not as simple as it should be, although the review process is now so much faster than it used to be. Back in 2015 app reviews would take almost a week before you knew if the app had been rejected or not. These days (and I am talking November 2016) app reviews take only one day before they are live on the App Store.
Today I tried uploading a new version of Tessitura Pro 1.9.4 to iTunes Connect from within XCode 8.1 and I got an error with code -22421
Searching on the internet I couldn’t find any case that applied to mine. Apparently -22421 is returned as an error code for several different reasons.
Here’s the problem I had: On my previous (most recent) version of Tessitura, I selected 9.3 as the iOS version in Deployment Target. But for some reason after opening the project inĀ XCode 8.1 my deployment target had changed to 8.4
I am guessing you can’t downgrade the deployment target on an app (although I don’t this for a fact). I changed it back to 9.3 and the new Tessitura built uploaded without any problems
In this new version I am adding a google adwords conversion tracking snippet to track installs on the app and I thought that was the problem. I still don’t know whether the tracking code will be accepted in the review process, but I will write a new post with my findings once it’s worked.
Building an App on iOS 8 still compatible with iOS7
My new app 20 Saxophone Tricks of the Trade by Mario Cerra has been available on the App Store for over a week now.
We’ve had many downloads apparently with no issues. Yesterday a user wrote us an email saying the app was crashing right after launching. I knew right away it had something to do with the user’s device or IOS.
I downloaded the app from the App Store on an iPad running IOS 7.1.1 and the app crashed right away. I tried it in XCode with the iPad 2 simulator and the app run perfectly but, as soon I connected my iPad with IOS 7 and run it from XCode the app crashed again with an uncaught exemption error.
Long story short, after a few break points I found the issue was in a line where I’ve usedĀ containsString to find if a substring is contained in a string, which is an iOS 8 only method. Although the app was set to build for ios 7.1 and up the xcode compiler gave me no warning notice.
The solution is to use the rangeOfString method that is compatible with iOS 7:
[yourString rangeOfString:@”whatever-you-are-looking-for string”].location == NSNotFound
That solved the problem.
To submit a new version of the app to the App Store you must change the version number and build number of the app, archive it and submit it.
Now the app is back on waiting for review on the App Store.
I also added a note in the description for the current version of the app so users still running IOS 7 will wait for the update before buying it.
– (NSString*) archivoFullPath: (NSString *)archivo {
NSMutableString* result = [NSMutableString stringWithString: mDecksURLFolder];
if (!([archivo rangeOfString:@”http”].location == NSNotFound)) {
return archivo;
} else {
[result appendString: archivo];
return result;
}
}
You must be logged in to post a comment.