I have an iPhone app that was handed to me. I deleted all of the existing certificates & provisioning profiles and created them from scratch. I believe I have set everything in the Provisioning Portal correctly:
Distribution Certificate created
Devices with correct UDID's added
Ad-Hoc Provisioning file created with associated devices
I was able to successfully build & Archive my application. When I save it as a *.ipa and drag that and the *.mobileprovision file into iTunes everything is good, until my phone is syncing.
At that point I get an iTunes Sync: Failed to Install error. Other testers get the error: The app was not installed because the signer is not valid
I am not sure how to resolve this?
I have received that error because I had created my .ipa file with the ad hoc provisioning profile BEFORE I added the devices. Are you sure that you are using the most recent provisioning profile when you create the ipa? You may need to check which scheme you are using and verify its right
Everything was correct, except for the final stage where I am given the save options. The profile matched my Distribution profile, but for the wrong app. It just defaulted to one of them. I had to manually change it to the Ad Hoc Distribution I was building for. Silly mistake.
This question was not resolved by the above suggestions, however we were able to fix it by removing the entitlements from the build.
This problem happened while working on an old app we were updating. No jailbreaking, just an ad hoc .ipa sent over email between team members. All provisions were correct.
We were able to figure out the issue was entitlements by trying to install using "iPhone Configuration Utility" instead of iTunes. That gave us the actual error message which was easy to fix.
Debugging this issue was easier than with iTunes. It also has better UI for installing ad hoc builds. I recommend you try it here:
http://www.macupdate.com/app/mac/27986/apple-iphone-configuration-utility
i already face this , finnaly i found,.
If Your Certificates, Provisoning Profiles then & the ipa is generated,,
so there is no problem in your ipa File,
But Problem in Specific Device in which you are try to insalled,,
If Your Device is JailBroken Then Easily iTunes cab Install ipa,,
But If Not Then You Have To Register/Add device to
https://developer.apple.com/devcenter/ios/index.action
->Procsoning Profile -> Devices
Then & Then Ipa File Is Installed
Related
Hy.
I have developed an IOS app in version 5.1 and xcode 4.5.1. After completing the app when I try to run it in the device using ad hoc distribution, the app is unable to install on device.
It shows popup "Unable to download application. ' could not be downloaded at this time'".
I have added distribution and developer certificate and it does not give any such alert when installing directly from the xcode but the problem occurs only when installing app from the testflight.
Could someone tell me where I m making a mistake.
You must Archive the application using your AdHoc Distribution Cert, then from the Archives tab of the Organizer click Distribute and again select your AdHoc cert. The .ipa that this produces is what must be uploaded to TestFlight and you must authorize your device through TestFlight. Here's some tutorials that will help:
Create and Upload an IPA to TestFlight
Setting up Permissions for Distribution on TestFlight
If your IPA and permissions are all correct then according to this article the error could be related to one of many other factors:
Device storage is full
The provisioning profile is a developer provisioning profile
The ad hoc distribution provisioning profile is corrupted and the device is having an issue with it.
The device was restored from a backup and is causing a conflict for over-the-air distribution
There was a network timeout
See the referenced article for details on how to get a console log on the device. If you still are unable to resolve the issue then edit your question and include the relevant parts of the console log from the device.
Go to Product -> Edit Schema -> Build Configuration
Change Debug to Release and try it.
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.
I have created an ad hoc archive and a .ipa file for the application I am trying to distribute. I have also created a distributing provisioning profile with the UDIDs of the devices that I plan on distributing my application to. When I drag the .ipa and .mobileprovision files into iTunes and try to sync the application to the device, an error message on the phone pops up reading "'myapp' failed to install". By the way, I have a standard iOS developer's license ($99 per year) and am using Xcode version 4.2.1. I am pretty new to the developer program, so please try to keep your answers as simple as possible. Let me know if you need any extra information. Thank you!
I had the exact same issue. My issue was simple to fix. Check your Code Signing Identities for Project & Target in your project Build Settings. Mine were pointing to my Development Profile.
The Code Signing Identities need to point to the Ad hoc Distribution Profile that you created.
Make this change and then recreate the Archive and .ipa file. I then deleted the old App in iTunes, and then dragged the .ipa file onto the iTunes icon (Windows). Then I was able to use iTunes to install the App successfully.
My problem seemed to be Xcode. I had multiple copies of the Ad_Hoc profile with different expirations (all valid) and a few with different names from the days. I deleted them all and the app still failed to install, but I noticed all the Ad_Hoc profiles had been resurrected by iTunes. Tried it several times and including deleting them from the Organizer, but they always resurrected (reappeared installed on the device). Finally I drug out a copy of the supposedly extinct iPhone Configuration utility and used it to delete the app and all Ad_Hoc profiles. Then tried to install just the profile. That got it down to 2. Finally got all deleted and got iTunes to install the right profile. Still took 2 more attempts for iTunes to finally install my archive file!
Check this .
Don't need to drag both .ipa and Provisioning Profile.
Just Drag the .IPA File Follow Further steps as you.
Set install owner param in Xcode project / Deployment to the name you specified in apple dev license. I set both install owner and alternative install owner and Install Group and Alternative Install Group to my name which the 100% exactly as in my apple development license.
And the error was gone.
I was having a similar issue where my project was stored on a secondary NTFS drive. After moving the project over to my desktop [aka MacOS Extended (Journaled) drive], I was able to load the ipa file via itunes.
Another point: If the store version of the app installed on your device (or a version deployed another provision), you have to remove it from your device before installing the ad-hoc version.
I solved the issue by not trying to sync with iTunes but instead to sync it within Xcode (from the window->devices menu)
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
I'm trying to do an ad hoc distribution of my iPhone app to some beta testers. I created the certs, device IDs, provisioning profiles, etc. and followed the instructions on Apple's site regarding how to incorporate them into the build/distribution. When I copy the provisioning profile and app to iTunes and try to sync, I get the following message:
The application "XYZ" was not installed on the iPhone "Eric's iPhone" because the entitlements are not valid.
It seems like everyone else that runs into this problem solves it by adding the Entitlements.plist file to the build configuration. The thing is, I've created (and edited) that file correctly. I see it and the provisioning profile in the built app.
Does anyone know what might be going on?
Regards,
Eric
Did you go into the build settings for the AdHoc configuration and make sure the Code Signing Entitlements setting is set to point to your Entitlements.plist file?