I'm having issues submitting an app to iTunes Connect using Organizer.
I build and archive my application successfully then go to Organizer. I successfully validate the application. I then click to submit the application to iTunes Connect. I get the dialog to choose signing certificate and the app that I am uploading. I submit that and after a short time it comes back with the following error:
I know that I am entering my apple id and password correctly. As far as I can tell the bundle identifier and the rest of the app metadata are correct.
Has anyone seen this before or have any advice?
(I have tried using the App Uploader and get similar results).
10.6.4.
And latest version of SDK and xcode.
FWIW There doesn't seem to be an answer to this. I did however, uninstall Application Loader completely and reinstall it and the upload has worked.
Related
I uploaded an app as version 1.4 on iTunes Connect but on iTunes it is displaying "Invalid Binary". I tried more times but it is not fixed. I checked icons, appid, build settings etc. I revoked the certificate and generate again and provisioning profile also, i am using same app id which previous version have. Any guess what may be wrong here?
My app in an universal application.
This is the message from apple
Dear developer,
We have discovered one or more issues with your recent binary submission for "MyApp". Before your app can be reviewed, the following issues must be corrected:
Corrupt PNG File - The PNG icon file icon-72.png appears to be corrupt.
Once these issues have been corrected , go to the Version Details page and click Ready to Upload Binary. Continue through the submission process until the app status is Waiting for Upload and then use Application Loader to upload the corrected binary.
Regards,
The App Store team'
I got my answer,
Project > target > Build Settings > Show All > first item under the Packaging header
I searched for "pack"
Toggle Compress PNG Files to NO
And everything is ok
I signed up for TestFlight.
Then I followed all steps in this tutorial:
But Xcode throws this warning:
Application failed codesign verification. The signature was invalid,
contains disallowed entitlements, or it was not signed with an iPhone
Distribution Certificate. (-19011)
It smells like there is a lot more work to do than what they wrote in the tutorial.
Is there a complete tutorial which walks through every step without stepping over anything?
And do I need to add the SDK even for simple beta tests?
(Edit: No, SDK is not needed!)
Start with logging into the Provisioning Portal, and adding a test device or two, under Devices. Then go to Provisioning and create a new one for the appID you are working on and add those devices.
Back to Xcode and use the Organizer:Devices:Provisioning Profiles to download (refresh) the Provisioning Profile. Set your project's Debug scheme's signing to use that developer profile. You should then be able to build and then archive. Once archived, do an ad hoc distribution and save off that file to the desktop.
Go to your account on TestFlightApp.com and press the Upload Build button. Drop the file you saved on your desktop, into the Build upload area. TestFlightApp will give you errors if the app wasn't bundled for adhoc or signed properly.
Now, here is where TestFlightApp.com will save you work. Send out invites to friends from within TestFlightApp.com. TestFlightApp.com will manage notifying them and as they create an account, it will also help them find their UDIDs. These UDID's can be batched up and later downloaded by you and re-uploaded to the Apple Provisioning Center, into your devices section.
You then use Xcode to refresh your profiles, and rebuild the app, archive, and upload to testflightapp. Then you can select which one of your testers will get to see this build and what message they should be sent. Your testers will not have to figure out how to download the files and install them using iTunes or other app, they merely press the install button.
Believe me, while it is still a bit of work, it is so much better than not using TestFlightApp.com, especially if your users are not very savvy about app installation. In the future, you can use the TestFLight SDK to gather crash reports and usage information for your debug builds.
See the following for some more info: TestFlight beta-testing iOS app
I changed the version number to a higher version in my iPhone app. When I run the application from XCode, it runs successfully. But When I try putting it on my device from iTunes, installation failed.
Any ideas?
I have gotten this error before. It happened because I signed the build and the IPA with different keys by mistake. You need to be sure the one in your build settings matches the one you use to sign the IPA when you make it from the archive. Also of course they both need to be adhoc certificates,
You need to delete the Profile that is present In settings>General>profiles there delete the profile that belongs to your app also delete the app from the iPhone and download a profile form developer.apple yourAccount then drag and drop on the desktop and double click it and then drag and drop both ipa nad that profile in to the iTunes then sync the app will install now
Yesterday have I uploaded 2 builds to iOS beta testing platform - TestFlightApp. Unfortunately none of the testers, including me, can access those builds. It was working for us fine before.
I receive following message:
This device cannot install this build
TestFlight couldn't find the build you are looking for - perhaps it was removed
enter code here or you were sent an incorrect url. Check out your dashboard to see all your installable builds
Anyone received similar message ? Is it internal testflight problem, or something is wrong with my build ? How to fix that ?
It's happened to me as well, I got the message This device cannot install this build and the green button said Contact Developer.
After making sure that the user had register his device with test flight and that the device is also on the provisioning profile, I've removed the profile from the Settings app (by going to Settings>General>Profiles) and removed the Safari browsing data (by going to Settings>Safari>Advanced>Testflightapp.com)
Then I went back to the email and clicked on the link to install the app and that worked.
It may seem counter-intuitive (it was to me anyway) - even if you provision someone's device, you still have to check off each user on the permissions page and click "just update" before they can install an app, EVEN IF you already provisioned their device in the iOS provisioning portal.
I get warning: Application failed codesign verification. The signature was invalid, or it was
not signed with an Apple submission certificate. (-19011) can anyone help me ...ive been stuck
for a month ...also the app goes on my device for testing and i get a file to zip in my build
iphoneos file but when i use the app loader it says: Directory Services reported the following
error: Your Apple ID or password was entered incorrectly. (-20101)...i don't know how this happens when i log in correctly.. please help someone thank you.
When you receive "Directory Services reported the following error: Your Apple ID or password was entered incorrectly. (-20101)" from Application Loader, this means that your username and/or password has changed or it's in correct.
Solution:
1)Open Application Loader.
2)Click Window->Run Setup Wizard (Shift-Command-S).
3)Read the information on below the "Welcome to Application Loader." text
4)Click "Next".
5)Enter your iTunes Connect information (Apple ID and Password). If there are multiple developers on the account, use the Team Lead/Agent account information.
6) Click "Next".
7) If the information is correct you will get "Your iTunes login information has been verified." and if not you will get the same error as before and you will can always go back to re-enter the correct iTunes Connect information (Apple ID and Password).
I hope this helps.
Before doing a build for submitting (Release) to the app store, in Xcode under project properties ensure you have the settings for Release/Distribution selected. Then in the certificate row check you have your distribution certificate selected.
In Organizer check that your certificate is still valid. If not use your web browser and update the distribution certificate under developer.apple.com. THe update certificate takes a few minutes to become available. Back in Xcode use the update in Organizer to load your new certificates. If you get an error logging in then Xcode probably remembers an old or wrong password.
When you have your certificated sorted out, and want to do a build for the store use "Build and Archive" to upload your binary to Apple. The app loader still exists but since Xcode 3.2.something this functionality is included in Xcode
The best solution would be to develop for the Android. However, failing that are you using the Application Loader, not the xCode one which no longer works.
Also have you created your own Provisioning profiles for release and using them when you archive your code into its zip file from within Xcode?