My Provisioning Profiles for iPhone have just expired and I cannot download anything to my test device for testing anymore. Have tired "Automatic Device Provisioning (Refresh)", the Team Provisioning Profile seemed to have updated in the process. But my profile on a specific software in development cannot be extended similarly. Hope somebody who have experience on this could help ...
Check your device using the Xcode Organizer window. Delete any expired provisions from the device and install the same non-expired provision as specified in your Target build settings for whichever of your your Debug or Release builds you are trying to run.
Related
I am a beginner in iOS development. I have got some understanding on provisioning profiles in IOS. Please help me confirm my understanding.
Here is my scenario. iOS application developed on MAC1 with developer certificate1 and built using developer provisioning profile1 which includes UDID1 is deployed on device D1 with UDID1 successfully.
I add a new device D2 with UDID2 to my developer provisioning profile1 and built the app in MAC1 and generated an .ipa file.
I have a new MAC machine M2 where i try to connect device D2 and try to deploy the app on device D2. I copied the latest developer provisioning profile to the device.
Questions
1. Will the provisioning profile get installed successfully ?
2. Will i be able to deploy the .ipa file on device only with the developer provisioning profile and without developer certificate from a new MAC machine on to the device D2(UDID of this device is already added to developer provisioning profile)?
3. If i had used adhoc provisioning profile and followed the same above steps will i be able to use instruments in Xcode ?
Thanks.
UPDATE 1
3. Answer - If i use adhoc distribution profile, i could not use instruments in xcode.
No that's not how things work
!) certificates must exist on every computer and on every device you want to test
2) On ad-hoc you must add the devices and then sent them some profiles for the phones.
3) then you archive and codesign app and send it wherever you want to.
OR you can use something like that https://testflightapp.com/
Answer1 - YES, provisioning profile will be installed successfully.
Reason - Provisioning profile if included with the UDID of a device, it can be installed. No other dependancies. But in the Keychain access, you will get a warning telling that, valid identities are missing.
Answer2 - YES, we will be able to deploy the .ipa file on the Device D2. .ipa file internally has .app and the provisioning profile. We cannot deploy the app on device without developer certificate.
Answer3 - No, Distribution profile is for submitting apps in app store. Those apps cannot be debugged.
Adding to these answers, .dysm file helps developers to get more details while profiling. This .dysm file can be generated only with developer provisioning profile.
If anyone thinks my understanding is wrong in any aspect please add a comment. Thanks.
I followed the stepped to create a ad hoc carefully:
Added the testers team devices to the devices list in iOs Provisioning profile page
Created a new distribution profile for ad-hoc
In xcode I chose the project and clicked on product->archive.
I sent both the archive (ipa file) and mobile provision to the testers team.
The application failed to install.
I saw an answer of a developer to set in build settings the provisioning file to Code Signing Identities to the distribution profile here
In the list I can see only iOS Team Provisioning Profile that was created by xcode.
This is probably not the distribution profile.
What is missing? How can I set the build settings to the distribution ones?
In the IOS Provisioning Portal, in the Provisioning page, click the 'Download' button by your new distribution profile and it should get added to XCode.
To check you have it, go to XCode Organizer, Devices, then Library / Provisioning Profiles on the left.
You may also use https://testflightapp.com.
This is a free service and works very reliably - you can manage your testers and test ipa's easily.
First I also tried testing my app without such a service - but I ended up using this, since it's also very easy for the testers.
Create Distribution certificate and Provisioning profile.
You should have the Distribution certificate in key-chain.
Download Distribution Provisioning profile and double click on that profile.
Confirm you are having the profile in XCode -> Organizer.
In case the Add-Hoc deployment won't install on a testing device, and you have the device added to the profile, and the app signed correctly ...
Ok, what I did is to add an Entitlements.plist file and set the Can be debugged option to NO and set it on the target as the Code Signing Entitlements, but actually I don't know if this was the fix because I won't try again and again, now that it worked.
Then, actually I didn't archive the app and save the .ipa file from Organizer - Archives, but instead I've sent the .app file from the build/Release-iphoneos as it is, together with the profile downloaded from dev account. It will install in iTunes and it just worked, after couple of hours of frustration.
Following the instructions at MusicalGeometry.com, I've archived and created the .ipa file. However, whenever I try to install it to my iPhone through iTunes, it gets about 3/4ths of the way done before it stops and tells me the app failed to install. How can I go about finding out why it failed to install?
I'm using xCode 4.2
Thanks~
EDIT
I am trying to install an app that I currently have on the market. I do have a valid developer account, and the app is code signed.
The first thing to check is whether the device you are trying to install to is added to a list of development devices in the Provisioning Portal.
Then please check if your device is in a list of devices your provisioning profile supports (Review your Ad Hoc profile in Provisioning Portal).
Here's how you can do it:
Go to Provisioning Portal, navigate to Provisioning -> Distribution
Edit your Ad Hoc profile and make sure your target devices are selected:
Do you have a paid developer account and is the app codesigned?
I am trying to test my iPhone app in XCode 4 and it is telling me that i don't have a valid provisioning profile even though i do. What is wrong?
There are a lot of factors that could cause this. More information is needed. The primary things I would suggest are:
Is your device authorized in the provisioning profile (using the Developer Portal or team provisioning profile)
Have you downloaded the latest profile from the developer portal? And made sure its not expired?
Have you specified the correct provisioning profile in the build settings for your project? If you have had to make changes to the profile or renew it you will have to re-download it AND install it in Xcode AND change your build settings to point to the new one even though it has the same name.
I have an app that is loaded onto one of my development phones. The provisioning profile that was used for this app will expire in a couple of days. So, after the provisioning profile expires will the app will cease to function? or does the provisioning profile expiration only affect building and installing the app on the device?
Once the profile expires you will be unable to launch the app. You can go to the Provisioning Portal ( http://developer.apple.com/ ) on the apple site and renew the provisioning license - once an updated provisioning license is installed on the phone the app will function again (i.e you won't need to do a rebuild).
There are reports that if you delete all the expired provisioning profiles from the device, a previously running app installed using one of those expired profiles might still continue to launch on that device, but I haven't had a chance to test this on a recent OS release.
A non-expired profile with an appropriate Developer and app ID on the device (even if not the one used to install the app) may or may not be required.
The app will cease to function. It will launch then exit immediately.
As davbryn says you won't be able to launch the app, except you do not need to go to the provisioning portal as XCode should take care of things automatically these days.