Publishing to the App Store and Troubleshooting


#1

Now that you’ve got your app to version 1.0 it’s time to share it with the world. With Thunkable you can now send your project directly to App Store Connect where you can add device art, a description (and set your pricing!) before submitting it to Apple for review.

Troubleshooting

1 Apple

When your app is being reviewed by Apple you may see one of the following warnings.

1.1 SDK Version Issue

SDK Version Issue - This app was built with the iOS 11.4 SDK. Starting March 2019, all iOS apps submitted to the App Store must be built with the iOS 12.1 SDK or later, included in Xcode 10.1 or later.

We’re working on an update for this and have an update out by January. This is just a notification that the SDK will be updated in March and you can still submit your app for publication.

1.2 Missing Push Notification Entitlement

Your app appears to register with the Apple Push Notification service, but the app signature’s entitlements do not include the “aps-environment” entitlement…

Again, this message is simply a warning rather than an error. If you see this message simply resubmit your app for review.

2 Thunkable

When sending your project from Thunkable to App Store Connect, it is imperative that you follow all of the steps. If you miss one of these steps you will get an email from us with a title like Oops! Your app did not publish. and a long error message containing something like this:

Command failed: cd
.
.
.
No such file or directory. Not unobfuscating. Error uploading ipa file, for more information see above

If you see a message like this you need to make sure you are doing the following:

  1. Using Thunkable’s .csr file
  2. Uploading a valid .cer file
  3. Uploading a valid .mobileprovision file
  4. Using the correct Bundle ID
  5. Using the correct Team ID

iOS app not publishing
Publish to IOS error
Help me fix publish app