So my first official application got rejected as it was crashing on iOS 4.0 for which my application was not even made for (I didn't even check the option for iOS 4 tested). Now after resolving the bug I need to upload my application to the store. Should I create a new APP ID and a new distribution profile or just a new distribution provisioning profile for it?
You use the same ID, the same profile. Nothing to change at all. Just fix the bug and upload again.
Related
I recently have distributed an app for testing, and the test team are having a problem installing the app, more specifically the provisioning profile associated with the app.
They are using an iPhone 4 (iOS 5.1.1) and are getting "Could not install the provisioning profile due to an unknown error"
I am used to seeing this when a UDID is not registered against the profile which is trying to be installed, but they are adamant that they have supplied the correct UDID. In terms of the profile, both looking at provisioning on the iOS Dev account, and opening in a text editor confirms that the UDID that has been supplied is definitely present.
My question is, are there any known issues (other than wrong UDID supplied) which could cause this to occur on a device, even if that device is authorised to install that particular provisioning profile?
Thanks
This won't answer your question because your problematic device is iOS-5.1, but it may help lots of other people:
Another possible issue since iOS7 is where did you find UDID. As Apple says:
In iOS 7, apps that are already on the store or on users’ devices that call this removed API will no longer be returned the UDID. Instead, -[UIDevice uniqueIdentifier] will return a 40-character string starting with FFFFFFFF, followed by the hex value of -[UIDevice identifierForVendor].
Consequetly, check the UDID your client/collaborator sends to you: if it begins with FFFFFFFF, thats a wrong one.
The only & unique method to get UDID under iOS7 is to plug your device to a computer, launch iTunes (or Xcode) and copy the displayed UDID.
Looks like the UDID which is generated programmatically gives a random alphanumeric code from iOS 7. So to make sure you are using the right one, connect it to iTunes and then copy the UDID.
There may be few reasons behind that because information is not enough so i can just guess -
If you're getting any boot strap error in console then delete app from device then switched OFF your device then ON and try again.
May be in your device there is already an app having same profile so your app would overwrite on previous one and new app would not be install.
Last It might be provisioning profile issue. Make it again.
I submitted my app in the App Store. First I validated it, and turns out successful. Then I submitted it and succesfully uploaded to iTunes Connect. After a minute, it says that the file is Invalid binary. I am uploading an update of an existing app which is already published in the App Store. (previous version uploaded by other developer). I tried every solution that I found in google search but no luck.
Just for information.
Today I faced the same problem of Invalid Binary while uploading new version of existing application.
I got following email from apple
iPhone 5 Optimization Requirement - Your binary is not optimized for
iPhone 5. As of May 1, all new iPhone apps and app updates
submitted must support the 4-inch display on iPhone 5. All apps must
include a launch image with the -568h size modifier immediately
following the portion of the launch image's filename.
Launch images must be PNG files and located at the top-level of your
bundle, or provided within each .lproj folder if you localize your
launch images. Learn more about iPhone 5 support and app launch images
by reviewing the iOS Human Interface Guidelines and iOS App
Programming Guide.
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." You can then
deliver the corrected binary.
Solution:
Added 4inch app screen shots in iTunesconnect meta data
Added Default-568h#2x.png image in my application for iPhone 5
After these changes application successfully submitted.
Need to add arm64
I faced the same problem of Invalid Binary while uploading new version of existing application.
The reason are from February 2015 itself we need to Add arm64 to our app. i added this then my app successfully upload to app store.
Try to check the provisioning you made for the itunes store are correct with your application.
Remove the old binary which has been rejected then add the new one.
If you can do try to make fresh provisioning and also check in the xcode as well.
And do check the mode,is that debug or distribution as you need to make the build for distribution.
Hope it man help you.
Cheers
Sanjay
You cannot submit an app that uses the same bundle ID or the same app name of any app (even the "same" one) submitted by another developer account.
Make sure you have choosen "App Store" as distribution method in distribution provisioning profile, not "Ad Hoc".
I have faced this issue many times.My app got passed validation and submitted
successfully to iTunes Connect.But It shows invalid binary in prerelease
options.I saw one awesome post in Apple discussions and finally solved my
issue.App bundle id was changed in config file of my web app.I have changed
old bundle id in config.xml and app uploaded for review.
Try using the Application Loader under /Developer/Applications/Utilities. Make sure you have created a New App in iTunesConnect...under Manage Applications, select the application you are going to create an update for... when that loads on the right you will see Add a New Update.
I was trying to implement in-app purchase. I am using ios 5.0 beta and xcode 4.2. Now I am remaining with only error. Also when I add my binary to iTunes Connect through Application Loader I get this error:
Please help me with it!
At the moment it is not possible to submit binaries that were created with Xcode4.2 and link against iOS5. This restriction will be lifter when iOS5 and Xcode4.2 come out of beta. At the moment you will need to use Xcode 4.1 to submit a binary to Apple (which won't work if you need iOS5 features or ARC).
Is it necessary to make a build of project through app store distribution provisioning profile?
When you want to test you iPhone App with In-App Purchase you will need a development provisioning profile setup with your app's id.
To do this:
Go to iOS Provisioning Portal ( http://developer.apple.com/ios/manage/overview/index.action )
Create a new App ID e.g. com.test.my_app
Go to Provisioning and Create a new iOS Development Provisioning Profile with the App ID from before
Go to XCode set your app up with the correct App ID and new Provisioning Profile you just made.
Edit
I just re-read your question, and it's probably my fault for not paying more attention the first time, but you can probably ignore my previous answer..
What I believe is the problem is that you're using the 5.0 beta SDK to write and submit your app. This can't be done. Apple will not accept apps written with beta software.
You must compile and submit your app with the 4.3 SDK.
A lot of those errors can't be made any more clear than they already are...
Firstly, your app needs an armv6 binary, so make sure you're not building only the current active architecture.
You need to provide an icon that is 57 x 57 in size and specify it in the info plist with the CFBundleIconFile key.
Your code signing is invalid. Ensure you are using the correct distribution certificate and that you have a valid provisioning profile.
I created a distribution profile of my application, installed and tested it on my iPhone and uploaded the binary to App Store. Due to some usual reasons Apple rejected it and asked me to make a few changes.
Meanwhile I deleted the application from my iPhone. Now when I reinstall it says valid provisioning profile is not present, so will I have to repeat the whole process of making a distribution profile and then upload it to the store. The provisional profile cannot change, so should I create the new distribution profile with the same one and delete the old distribution profile I made?
Try out How to Fix Code Signing Errors.
I'm currently stuck in the distribution-profile-jungle and I can't find my way out.
I have launched an app to the App Store using my Distribution Profile, for various reasons I needed to wipe my keychain. When this was done I successfully updated the Development Profile by adding my newly created certificate. All is fine up until now.
The problem starts when I want to update the Distribution Profile to incorporate my new certificate. According to my experience this can not be done without removing it and creating a new one.
Question:
If I do this what will happen to the app in the App Store? (Will users still be able to download it?)
Can I still build the same app using the new Distribution Profile?
I am grateful for any knowledge/links which can clarify this issue.
Info:
I'm using Snow Leopard 64-bit, XCode 3.2.2 and SDK 3.0.
Best regards //Abeansits
I can't find documentation anywhere, but I've created new distribution certificates for Apps that are in the store without encountering any problems.
I believe that the distribution certificate is only used to verify your identity when transmitting the binary.
According to this website:
An application that has placed items
into the Key Chain can’t retrieve
those items if a follow-on version is
signed with a different distribution
profile.