EDIT : I recreated the build and checked, the CFBundleSupportedPlatforms is correct this time. So this is clearly not the reason. Wrong direction unfortunately.
d.
I am using Enterprise and I can confirm I do not have the simulator in the plist.
\<key\>CFBundleSupportedPlatforms\</key\> \<array\> \<string\>iPhoneOS\</string\> \</array\>Hey guyz i my APP has been finally accepted by Apple Store, after so many trial and error upload.
I use Phonegap/Cordova for my App.
The secrete was to delete my plugin folder and allow Phonegap Build populate the plugins for the APp on its own.
Um… Rob Miracle? Any ideas
The issue from my experience is plugin compatibility.
This is because i had to clear all plugins on my APP and use just the basic once i need
BELOW are the only plugins i called for my cordova App which worked for me
<plugin name=“org.apache.cordova.inappbrowser” />
<plugin name=“org.apache.cordova.network-information” />
<plugin name=“org.apache.cordova.splashscreen” />
<plugin name=“cordova-plugin-whitelist” />
The initial message is this:
Dear LobsterApps,
While processing your iOS app, errors occurred in the app thinning process, and your app couldn’t be thinned. If your app contains bitcode, bitcode processing may have failed. Because of these errors, this build of your app will not be able to be submitted for review or placed on the App Store. For information that may help resolve this issue, see Tech Note 2432.
Regards,
The App Store team
The rejection email from Apple includes a link. The link makes reference to many possible causes, one of which is the CFBundleExecutable key.
https://developer.apple.com/library/ios/technotes/tn2432/_index.html
omg… i have to submit my app today. the message is same above…
I really hope this problem will be fine as soon as possible…
Rob, do you have a timeline on when Corona Labs will release the SDK for Xcode 8?
With Corona Simulator 2016.2945 you can build using Xcode 8, but this is unrelated to the issue in question. You’ll still get app thinning processing error.
Also, you’ll have to add plist entries, something like
NSPhotoLibraryUsageDescription = ‘To select user profile picture’,
NSCameraUsageDescription = ‘To take a user profile picture’,
This issue started after 9/5/2016 and without ANY changes to my plugins or build settings.
The App Store has now released Xcode 8 as an update on the Mac App Store. Should we upgrade or should we wait to upgrade Xcode 8? I’m guessing as long as we are using 2016.2945 we should be fine, but I want to double check.
I am also getting the thinning error:
Build 2940
Plugins: Admob, GPGS, google IAP, Amazon IAP, notifications, toast, flurry
So I discovered I had two system updates between the last successful build Aug31 and the first failure on Sep 7th.
OSX X El Capitan Update v 10.11.6 on Sep 3 and Security update 2016-001 on Sep 4th. Possibly related?
Any solution for this?
Got the same problem with the Google Plus framework.
I also got the thinning error a few times - is Corona planning on fixing this, or are you trying to contact Apple to get them to fix it server-side? I doubt Apple will be fixing this anytime soon even with people contacting them … hope there is a fix for this soon as we have a lot of updates to push.
@JBean, we are working on trying to find something that works. Apple did this back in May and they fixed it a couple of days later. I don’t know why they are taking so long acknowledging the problem this time. But our engineering team is working hard to get this solved.
Rob
@Rob and other Corona staff, in case you are feeling a little beat up over this, please know that we do appreciate the work you are putting into fixing this.
Thanks @Rob we really appreciate it! It’s so frustrating when Apple updates and makes changes like this on a whim, and you are scrambling to get it resolved, I can’t imagine how stressful that must be. Thanks to the Corona team for looking into it!
Thanks @Rob, for looking on what the issue could be and fixing it.
In another update, i sent my signed IPA and screenshots and a really detailed description of how the issue was affecting us, the multiple attempts and different things i tried, and that not much had changed from the last successful accepted build, i also included a link to this forum. They responded with this, unfortunately:
Thank you for your prompt reply, and for providing the requested information. I greatly appreciate your assistance in this matter. Upon further investigation, we were unable to determine an issue with our systems preventing your build from uploading.
So even after they asked for all the information, an IPA, screenshots and all that stuff, they did not know what is causing the issue. 