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.
Related
I am facing an issue related to apple developer portal. I had added a new UDID (with all alphabets as capitals )to the dev account. But somehow now the device shows UDID with all lowercase letters. This may be the reason i am unable to deploy an adhoc build to this device.
If i disable this device and try to add again with a different name and same UDID(pasted as Capitalized alphabets), the device previously disabled becomes active again and the new device is not added.
I am not sure if this question fits around here in stackoverflow, in which case it will be closed very soon :-). But if it does, it would be very helpful if someone could let me know a workaround through this issue.
OK, here's the problem:
In iOS7 UDIDs are no longer available via the "send me my UDID apps.
UDIDs are ONLY available via Xcode or connecting to itunes.
The ones sent by the apps are incorrect and will fail - they all have FFFFF as the start...
To find the correct UDID, connect to itunes.
click on:
My Device->serial number (it will switch to the UDID)
grrrrr..............
Very nice woman at Apple walked me through it.
S
I am working on a project for which i bought a couple of iPad minis. I added both of the iPads to the provisioning portal as devices. I then try to modify my provisioning profile and click on both of the devices to add them to the certificate. When i hit save/submit to add the devices to the certificate i receive the following error, "The selected device(s) are not unique. Please select unique device(s)."
Both of the devices have different names in the portal and different UDID. I fear that The issue could be related to adding the devices through Xcode 4.5, thanks.
I solved the problem on my end. When I was adding the devices through Xcode, one of the devices was somehow added twice in some odd glitch but with two different names. Deleting the extra device which I guess did have a duplicate udid took care of the issue. This was also preventing other devices although those devices did not have duplicate udid in the system. Hope this helps anyone that might encounter this issue.
I had a similar issue before. The workaround is to just create a new provisioning profile.
might be the udid: (for IOS7, requires new method to get udid).
Issue with developer portal added device
How to disable an iPhone app running on a testing device without deleting it, for which the ipa file has been generated using a provisioning profile for the testing device. Assume I have access to the paid member account.
If I make the profile invalid, Does the app still works on the device ?
I am naive to the iPhone development. I am sorry If my question is improper one.
I guess that when you make a IPA with a profile from the provisioning center, it comes embeded within the IPA. So, theoretically, if you remove a device from the provisioning center, the change will not reflect on previously installed devices.
Just a guess.
If that's right, the only way I see to do it dynamically, is if you make by yourself an auth system for the app testers, requiring a password or whatever that will be validated online for the app be able to run.
in apple developer provisioning center, when you make a profile, it asks you to select devices for that profile from your list. app will run on listed devices only, you can remove/add the devices by modifying that profile and then downloading profile and making a IPA with that profile.
I think what you are asking is is it possible to remotely disable / wipe an app that you have previously sent to a tester.
I believe that is impossible, because assuming the tester managed to make it run at least one, he/she already has the provisioning profile and the app to match that provisioning profile. Therefore unless the tester changes that setup, there is nothing you can do to revoke the access.
On the other hand, I believe remote wipe is possible under the enterprise developer programme though.
I am trying to set an Ad Hoc distribution in order to test an iPhone app with some remote users. And I haven't found any good and clear tutorial up to now. By reading bits and pieces on Apple documentation and others I am now able to put the app on my iPod device doing as much as I can "as if I was remote user"; meaning I can put my app on the device without going through XCode. But when I send the xxx.mobileprovision an the app file to a remote user, things go wrong. The user gets a message saying that there is no proper signing authority.
As far as I know I included myself and the other users in the list of device UDIDs.
One thing unclear to me related to this issue is :
In the iOS Provisioning Portal section Certificates I can see one tab "Development" and another one "Distribution", I am not sure of what the difference is. I have one item in each tab, but I see no "Add" button to add more items and try something different. Is one of those two tabs important for my problem above?
Thanks.
The tabs are very important.
With certificates, Development is the Key Chain cert that grants you permission to build in Xcode directly to an iOS device connected by cable. Distribution is the Key Chain cert that grants you permission to build in Xcode app that may be installed onto an iOS device remotely.
Development is the mobile provisioning profile that has the list of registered an iOS devices you may directly build an app onto connected by cable.
Distribution is the mobile provisioning profile that has the list of registered an iOS devices you may send an app to someone else and have them install it on a registered iOS device remotely without using Xcode.
You want to do an Archive which will require a Distribution mobile provisioning profile. I might add that if you are sending an mobile provisioning profile in an email, you will likely want to Zip it with the .ipa since the profile can often get corrupted with in certain email clients.
Here's a link to another question that has very thorough step-by-step instructions for creating ad-hoc distribution profiles: how do you beta test an iPhone app. The instructions have changed slightly with newer Xcode versions, but this is still the best walkthrough I could find.
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.