i have a free account not a paid dev one
i have not updated my app recently and i was wondering if this is what could have caused it
i check my provisioning profile and it says the newest licence was created TODAY , i didn't run the app thought Xcode today, but if i do, i know it will be all ok, i just want to know why did my app stop working, is there a way i can check for memory leaks etc or could it simply be that the licence doesn't update online but only when running the app thought Xcode (so you get 7 days )
You can check the device console to see if the app is "crashing" due to an expired / invalid provisioning profile. For information around seeing that information in the console, you can get that information here.
If you want to build in provisioning profile checking into your app to see when the app provisioning profile is set to expire within the app itself (or the certificate used to sign the app), you can see that here. Accessing the profile information at runtime is challenging, but can be done.
However, if you just want to confirm that the app is crashing at launch due to the profile, simply check the device console.
Also, free account provisioning profiles will last only 7 days. So you have a week to run the app. But if you build the app when you provisioning profile is 3 days old, that only gives you 4 days from when you build the app to a device.
Also, the having a new provisioning profile in Xcode has no effect on the device. When you run on the device from Xcode (or install an .ipa from a web link), iOS installed the profile on the device. If you don't run from Xcode, your devices provisioning profile will be older than the one in Xcode and the app will not run.
Related
enter image description here
I am a new to app development .in current phase I am learning how to make them using some tutorials . after using for few days , suddenly my project is not able to build and run the app on simulator . it's showing that provisioning profiles could not be created. I have tried everything and stuck for a day but nothing coming out to be correct.
error : failed to create provisioning certificate
There are no devices registered in your account on the developer website. Plug in and select a device to have Xcode register it.
Xcode couldn't find any iOS App Development provisioning profiles matching 'tour.holi-celebration0000000'.
Try to check if there are extra certificates in Keychain -> My Certificates.
I had similar problem once and it was fixed after removing unnecessary certificates from Keychain.
I have finished developing a big and heavy app. It is universal (for iPhone and iPad), and now I am trying to publish it in App Store. I have done this other times, so I know how annoying it is.
I'm using Xcode 4.2 and devices with many iOS versions (4.2.1, 5.0, 5.1). My app is enabled to send Push Notifications, and it doesn't use iCloud.
I have tested it with development certificate, and it works OK. Now I've generated and downloaded Ad Hoc Distribution Provisioning Profile in order to test it in my iPhone and iPad. It seem like all is OK, but when I'm going to install the app (with the Ad Hoc Distribution Provisioning profile) with Xcode in any device, Xcode shows an error: "Error launching remote program: failed to get the task for process".
I've read this link it suggests two causes:
I am using Ad Hoc Distribution Provisioning profile when debugging the app in my device. This is not the problem, because I'm not debugging the app.
I specify a code signing entitlements property list in my build settings which does not include a "get-task-allow" or "Can be debugged" property. This is not the problem, because I'm not specifying any entitlements property list because I don't need it (or I think so).
Some people that have the same problem solve it adding the "get-task-allow" property to the entitlements property list. But I haven't that file. So the question is, Do I need to create it just for add the "get-task-allow" property?
If I don't , which is the problem? I'm not trying to debugging and I haven't entitlements p-list in my app.
Although my app doesn't need entitlements p-list, I tried to create it and add the "get-task-allow" property in OFF following this, but it didn't solve the problem.
I have also to say that althought Xcode shows the error during the installation in the device and the app shut off, when I start again the app, the installation is done and the app runs without problem.
I read the following similar thread, but they didn't solve my problem:
iPhone Debugging: How to resolve 'failed to get the task for process'?
Profile bug (Error launching remote program: failed to get the task for process XXX.)
iPhone Debugging Error launching remote program: failed to get the task for process 907
Error launching remote program: failed to get the task for process 699
Thank you so much.
I am using Ad Hoc Distribution Provisioning profile when debugging the app in my device. This is not the problem, because I'm not debugging the app.
This is exactly the problem.
You are trying to run an ad-hoc application from the XCode - it means to debug it.
You should archive your app and install it (an ipa file) together with the correct provisioning profile.
There are few ways to install the app:
Using iTunes - not trivial
Using an iPhone Configuration Utility - easier
Using some OTA (over the air) installation service (e.g. TestFlight site) - I use this all the time, after a couple of times it gets really easy and you can distribute your Beta version to remote devices (e.g. clients, friends etc.)
The problem look like you are running App from Xcode with Ad Hoc Distribution Provisioning profile.
After Archiving (Product menu > Archive ) the App from Xcode, you can get ipa.
You can install ipa via iTunes if you device already sync with your iTunes app.
https://testflightapp.com/ , I am using testflightapp for testing the app. It's easy to use and we can distribute to for test user.
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.
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