itunesconnect

As I understand, promo-codes expire 4 weeks after generated. You are also given 50 codes per version uploaded. But, what would happen if you generate a promo-code, e.g. for app version 1.0, then upload a new binary/version, e.g. app version 1.1, to iTunesConnect and give out more promo-codes? Would the other promocodes expire immediately when the new version is ready or would they still be active until their 4-weeks are past? Also, would they then be able to download version 1.1 instead of 1.0 (on which they were generated) ? You would get 50 new promo codes for your new version. All promo

I've included screenshots of the full error messages I'm getting. This happens when I try and submit my app to iTunes Connect. I don't get any errors when running the app. I had the exact same error for my application, and I was not able to find any reason from the information. The difference was, though, that I got it for all my .dll files. After some time, I saw that under IOS Bundle Signing - Custom entitlements it tried to point to a file that did not exist. I just removed that, and it stopped giving errors. Not sure if it helps you too, but it worked for me. This issue for me was caused

I'm having the same issue as this guy , this guy , and this guy (nota bene, I'm actually not sure if they're all guys, per se). They all ended up finding their own solutions, but none of them apply to my issue. I'm using Xcode 6.1 in my iOS 8 app with an included extension. The app and the extension both rely on an included framework. When I try to submit the app to the Store, the validation warning I get is "ERROR ITMS-9000: Invalid bundle. The bundle at 'xxxxx.appex' contains disallowed file 'Frameworks'". I can't even find a file called Frameworks. The shared framework is supposed to be

I regenerate all of the certificates, update the version number of the application, but the problem persists. Follow the below steps. Go to My Apps Page. Remove the Build. Then Save It. Re Add your Build. then Save It. Now try to Submit It must work. I do not know what the reasons are, how to do?Thanks! In Prerelease section the status of your build should not be "Processing". Just wait some time (10-20 min) after build upload, and it will be ready to use. I got this problem in Chrome browser. Switching to Safari worked like a charm for me. It seems to happen if you are too quick between the