I have installed an app on
my iPod touch. Will this app expire when the provisioning certificate does?
EDIT:
I am the developer in this case. I installed it using XCode. I used a development provisioning profile not a distribution one. Does this change anything?
How did you install it? I assume it was sent to you by the developer along with the distribution certificate and you installed it via iTunes?
If so, then yes you will need to reinstall with an updated provisioning profile after your current one expires.
If you're talking about adhoc distribution, yes : you won't be able to launch "adhoc distributed applications" anymore once the adhoc provisioning profile installed on the iphone has expired. You will need to request a new "fresh" generated adhoc version.
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.
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?
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.
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.
The iPhone is attached to a Mac runnning the latest iTunes version and I am 100% sure that her UDID is in the provisioning file. Her iPhone has not been jailbroken and we even restored it to factory settings.
I am having trouble installing our development build on this one iPhone. The error is:
the application "[Application Name]" was not
installed on the iPhone "iPhone"
because the signer is not valid
I am 100% sure that the UDID is accurately entered in the provisioning file and that they correctly copied the right provision file/build combo. This same combo has been successfully installed on over a dozen iphones.
We have been able to install this on some devices with no problems.
Edit:
From comments to an answer:
We can install it on 100 iphone with
our account. We have about 40 iphones
in this provisioning profile and it
works on 38 of them.
I had a fix that seemed to work for one user who was having troubles:
remove all offending profiles and apps
restart
add back provisioning profile FIRST
sync device
now add app resource
sync again to get app on device
the offending machine was a windows box... dunno if that makes a difference.
If someone else gets this issue - try this and let us know if this is the actual fix or workaround! This goblin has rarely been seen and solved with the same steps.
this was my reference for the fix idea:
http://iphone.forums.wordpress.org/topic/installing-beta#post-1194
Does the answer to this question help you at all?
Signer not valid error
Put the signing at the Target level, not the Project level
I'm personally not sure what that means but it worked in that case
We can install it on 100 iphone with our account. We have about 40 iphones in this provisioning profile and it works on 38 of them. Any other ideas?
I'll tell Buzz that you say hi and if you can help us we'll get you a moon rock!
(Ignore: I misread the question and didn't notice he had dozens of installs already so my advice does not apply)
If you have just the standard developers account, you can only install on up to five phones before the certificate becomes invalid for further installs. If you've already installed it on five phones that is most likely the problem.
Tell Buzz some random guy on the internet said, "Hi!"
A couple of things to try:
Renew the profile at the Developer's portal. It may have expired or become corrupt.
Create a new provisioning profile
Does the mobileprovision file show up on the device after sync? You should see it in
Settings->General->Profiles
If it doesn't then that would be the problem. Check once again that the UDID is correct - same UDID on iTunes and in the developer portal. Try syncing iTunes with the mobileprovision without trying to install the app. If it still doesn't get installed then CHECK THE UDID. If it is getting installed on all other devices, UDID is most likely the issue.
If the distribution signing certificate was revoked in the meantime and recreated, you need to remove the old provisioning profile from the device first. This is on an iOS 3.1.3 device.
This happened to me recently and I resolved it. Situation was that I had an ad hoc provisioning profile I was using successfully for around 40 devices with several different apps. When a new device was required I would add it to the profile, download, then use 'share' from XCode with the same archived app but the new profile.
Recently my distribution certificate expired, so I created a new one and recreated the provisioning profiles. Subsequently, I could still install on the existing devices but would get an error trying to install on new devices, even though I had added them to the profile and installed the profile on the device.
The secret was that although I had created the new distribution cert and added it to my KeyChain, there was still a copy of the old cert in the KeyChain, and that was being used to sign the app. It turns out that if you do not delete the old provisioning profiles from XCode, when you start up XCode it will recreate the old cert in the KeyChain, and that will be used to sign the app, which means that the new profile with the new device (created with the new cert) will not match.
Solution: when you renew your cert, delete all the old profiles signed with that cert, delete the old cert, then recreate, download and install the new profiles.
hth