IPhone: Application Installation Fails with Invalid Subscriber Error

Question

The iPhone is attached to a Mac running the latest version of iTunes, and I'm 100% sure that its UDID is in the initialization file. Her iPhone was not jailbroken, and we even returned it to factory settings.

I'm having trouble installing our development on this iPhone. Error:

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 exactly entered in the initialization file and that they correctly copied the correct file / assembly file. The same combination has been successfully installed on more than a dozen iphones.

We were able to install this on some devices without problems.

Edit:

From comments to the answer:

We can install it on 100 iphone with our account. We have about 40 iphones in this provisioning profile and works on 38 of them.

Answer 1

I had a fix that seemed to work for a single user who had problems:

• Remove all abusive profiles and applications.
• reboot
• add backup access profile FIRST
• sync device
• add application resource
• sync again to get the application on the device

the abusive machine was a window box ... dunno, if that matters.

If someone else gets this problem - try this and let us know if this is an actual fix or a workaround! This goblin was rarely seen and solved using the same steps.

This was my link to the fix idea:

http://iphone.forums.wordpress.org/topic/installing-beta#post-1194

Answer 2

Does the answer to this question help you?

Subscriber error not valid

Place the signature at the target level, not at the project level

I personally am not sure what this means, but it worked in this case

Answer 3

(Ignoring: I misunderstood the question and did not notice that he already had many installations, so my advice is not applicable)

If you have only a standard developer account, you can only install up to five phones before the certificate becomes invalid for further installations. If you have already installed it on five phones, this is most likely a problem.

Tell Buzz, some random guy on the Internet said, "Hello!"

Answer 4

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 will tell Buzz that you say hi, and if you help us, we will get you moon rock!

Answer 5

A few things to try:

• Update your profile on the developer portal. It may have expired or become corrupt.
• Create a new training profile

Answer 6

Does the mobileprovision file appear on the device after synchronization? You should see him in

Settings->General->Profiles 

If this is not the case, it will be a problem. Once again, check the correct UDID - the same UDID on iTunes and the developer portal. Try syncing iTunes with your mobile device without trying to install the application. If it is still not installed, then CHECK the UDID. If it is installed on all other devices, most likely a problem with the UDID.

Answer 7

If the distribution signature certificate was revoked in the meantime and recreated, you must first delete the old provisioning profile. This is an iOS 3.1.3 device.

Answer 8

This has happened to me recently, and I decided it. The situation was that I had an ad hoc Provision profile, which I successfully used for about 40 devices with several different applications. When a new device is required, I will add it to the profile, load it, and then use the "share" from Xcode with the same archived application, but with the new profile.

My distribution certificate has recently expired, so I created a new one and updated provisioning profiles. Subsequently, I could still install on existing devices, but I received an error when trying to install on new devices, although I added them to the profile and installed the profile on the device.

The secret was that although I created a new distribution certificate and added it to my KeyChain, there was still a copy of the old certificate in KeyChain, and this was used to sign the application. It turns out that if you do not delete the old provisioning profiles from Xcode, when you start Xcode, it recreates the old certificate in KeyChain and will be used to sign the application, which means that the new profile with the new device (created with the new certificate) will not match.

Solution: when updating the certificate, delete all old profiles signed with this certificate, delete the old certificate, then recreate, download and install new profiles.

Hth