I have submitted iOS app to TestFlight and when my internal testers try to download app it says the provisioning profile is invalid. I have verified that the provisioning profile is not invalid. Is there something else that could be causing this.
I am using Xamarin on windows. I was able to successfully submit a different app to TestFlight using same certificate and app id.
Basically what i am looking for is a way to troubleshoot this other than just looking at the status of profile on the app store.
So problem here was needed to use App Store distribution instead of ad-hoc which to me is confusing considering i only wanted app on TestFlight so hopefully this clears things up for someone else.
Related
Big hand to Apple for screwing TestFlight. I can't seem to get anything to happen past this screen. I've
Created external testers
Upload a build with ad hoc profile (though application loader)
Turned on TestFlight Beta Testing (even tried turning it on and off to get invitation emails to send)
When adding external users they never receive and email either. Anyone have this problem?
I haven't seen this exact message, but one problem I see with your process is that you used an adhoc profile. According to Apple, you should be using an app store distribution profile:
Generate a new App Store Distribution profile containing the beta
entitlement to distribute builds via TestFlight.
As the message says, you also need to have the beta entitlement in your profile. If you created it in the last couple months - it should have it - but it's possible adhoc profiles don't. When you go to upload the binary, expand the entitlements and check to see that beta-reports-active is present and set to on.
Hopefully one of those two is your issue.
I have invited one TestFlight user from iTunes to test my app. The app is currently under review status. When that user tried to install the app, at the time of launching in iTunes, it throws the following error :
Could not install XXXX.
The app couldn't be installed because the developer's certificate is no longer valid. To resolve the issue, contact the developer.
Anyone can provide brief explanation what could be the reason for this and how it can be resolved.
I encountered this error because the build was signed using a provisioning profile whose certificate had been revoked.
When i checked in the developer center, the provisioning profile was marked as "Invalid".
I just clicked "Edit", selected the new developer certificate and regenerated the provisioning profile. When the new build was uploaded on testflight signed with the new provisioning profile, the error went away.
However, i do think Apple should be checking if the provisioning profile is still valid rather than developers finding it out after build is already approved by TestFlight and testers complain about this error.
It simply means that the developer account from which this app is uploaded is expired OR the development/distribution certificates of the app are expired or revoked. It can be resolved by activating the certificates of the app on apple's developer portal.
We have uploaded a version to apple-test flight and apple approved app for external testers. Now we're trying to download and is not working, got same message.
But if we run app from dev phone push notification works so P12 still valid. And distributed with old test flight process works.
We're trying to upload another version and see if works.
I try and try again until I read a comment on the apple forum:
This XC profile will be acceptable for upload, but is incompatible with Testflight
When you have to check provisioning profile, be sure any "XC" provisioning profile is selected (you can change it by clicking on the right arrow)
more details on the "goldstee" answer : https://forums.developer.apple.com/thread/18446
The error CLearly states what is wrong, your Certificate needs to be renewed, as your certificate may have expired or revoked, Try to create the Certificate again along with the provisioning profiles, and it will work fine
I had a slightly different issue which was a bit more puzzling as everything was 'valid'. I encountered the issue when I needed a production push certificate (which I already set 2-3 months before and tested!).
This is what I've done to resolve the issue:
Check xocde - both Code Signing and Provisioning Profile:
I had the correct settings (they matched what I was expecting and what I used for a previous build).
Check my apple developer account - it stated that my 'prod' profile was 'Active'
Check xcode -> prefrences -> provisioning profiles - I found the profile I could see in apple developer. It had the same expiry date too!
Wet back to my Apple Developer account, clicked on the profile, downloaded it and double clicked on it.
That fixed the problem for me.
If you encounter any issues, I suggest you check Parse guide (yes, I know they are shutting down but their doc is very good!). It covers more than just profiles but you can choose the step you are having an issue with.
In my case, I found everything is fine, both provisioning profile and certificates were valid.
What I did wrong is, I upload the build to TestFligth using Transporter app, which usually needs an .ipa for same but choose adHoc type instead of AppStore while exporting the binary in the organiser.
Which somehow allow the build to upload to TestFlight but didn't authorised to install on the user's device.
So make sure you're choosing the right option while exporting the build.
I am building my application using XCode 6 and App Store provisioning profile. After creating the application, I tried to upload it in Device Anywhere (Keynote), but it is giving me an error saying the app might be unsigned and that I need to sign it. I also tried it with AdHoc profile, but it is the same.
To verify, I installed the application on my test device, the one signed with AdHoc and it is working properly. I also verified the IPAs with security cms command and the IPA are getting generated properly.
Any help regarding this will be helpful.
Is the device in which you are trying to deploy the code, registered under the same provisioning profile you are trying ? Please check on this.
A provisioning profile binds
Certificate
App ID
Device UDID.
So basically only if your device is under this particular provisioning profile, you will be able to deploy.
The issue has been resolved. Build the application using AdHoc profile and during upload selection the option to re-sign it. Also using Device Anywhere version 7.0 or the latest one. That will resolve the issue.
For one of company we have created iPhone app as in-house. This app is not on app store. We provide them updated provision file everytime.
When client tries to installing app on one of iPhone, it keep on saying Installing... But installation never occurs.
Any idea why this is happening?
I have iOS 7 on client iPhone.
This could be for many reasons but the most common are:
Did not sign with the right provisioning profile.
The users device is not set up in an ad hoc distribution profile.
Is it signed using a proper enterprise provisioning profile?
The information in the plist if downloading from a site does not match the file being downloaded.
Poor internet connection.
I would go down the list and doubly check everything. Make sure that if you're building an adhoc profile from an app store account that it is actually being refreshed and not duplicated in Xcode when building with the provisioning profile that contains the proper UDID for the device they want to install it on.
I am a contractor, building an app that will be published by another company. I have been using a Development profile to test with my device, and an Ad-hoc Distribution profile to share the app with a group of testers via TestFlight. This all works fine.
I am having trouble submitting the app to Apple. I tried creating an IPA signed with their App Store profile, but they were unable to submit it with Application Loader (this is their usual work flow). They shared their iTunes Connect admin login with me so I could try submitting it from Xcode.
Both approaches give the same error: Application failed codesign verification. The signature was invalid, contains disallowed entitlements, or it was not signed with an iPhone Distribution Certificate.
What are my options here? I have tried deleting and remaking the App Store profile.
I figured it out with the help of Apple. I just had to revoke my certificate, issue a new certificate signing request, and recreate all my provisioning profiles. I changed my Apple ID's email address recently, so it was probably related to that.
More details on starting fresh here https://developer.apple.com/legacy/library/technotes/tn2250/_index.html#//apple_ref/doc/uid/DTS40009933-CH1-TNTAG6