I'm trying to add a user to a Testflight build. So I go to the Developer Portal and add their info (UDID and Device name) and add their device to the provisioning profile, redownload it, and apply it to the project. Then I archive to an .ipa file. However, when I upload the ipa to Testflight, I'm only seeing the users that were available before, I would exact the new ID to show up under "Anonymous" or something. I opened up the .ipa file (convert to zip, unzip, check Payload/embeddedprofile.mobileprovision) and the device's UDID that I added was there, so it's just Testflight refusing to add my device. Is there something up with the Testflight service, or am I missing something? I'm not getting any errors at any step, just not seeing the new UDID in the "Invite Testers" page (and the user can't access the build, Testflight turns them away).
-Esa
I'll bet you didn't apply it when you archived the project for distribution. I did the same thing, took me an hour or so to figure that out! You need to double check that your Ad Hoc profile is selected in this dialog.
I deleted my account completely and started over with a new email address and it works now.
Related
I have upload build in app store after archive the file it will goes to uploading builds on that time i got this error
1.Apples web services operation was not successful.
2.Unable to authenticate the package:727047181.itmsp
3.ERROR ITMS -9000:"The bundle identifier cannot be changed from the current val;ue,'com.redim.pokerastic'. If u want to change your bundle identifier,you will need to create a new application in itunes Connect."at softwareAssests/SoftwareAsset(MZItmspsoftwareAssetPackage)
Please any one help me out dis problem.
This has happened to me a lot of times. To fix it, you should first delete your previous provisioning profiles for your application, then go to developer.apple.com and create a new provisioning profile for App Store
Then, choose the correct bundle ID (try to not use a wildcard ID) and choose the certificate that you would like to include in your profile. Make sure that your provisioning profile is named your app name (pokerastic) instead of com.redim.pokerastic, then download it and open it.
If you do not have any certificates, go to developer.apple.com and click the plus sign to add a new certificate.
Choose App store and Ad hoc then do exactly what it says to do. Make your certificate, upload it to Apple, then open up the download that Apple gives you.
In iTunesConnect, make sure that the bundle IDs of your applications match. You can find this by clicking manage applications, then clicking on the app you would like to upload, and in the top left it should say the bundle ID.
Finally, in Xcode under your application manager, click the target app then click 'General' at the top. Make sure that the bundle ID is the same as the one on iTunes Connect, then make sure the versions are the same.
The error it gives you states that your bundle IDs do not match, so make sure that they do. If you want to change it, you're going to have to go to iTunesConnect and create a new application with the same bundle ID that you have in Xcode. Make sure the one on iTunesConnect has the bundle ID com.redim.pokerastic
I am going to send a demo of my project through TestFlight to someone.
To do so, I followed this answer: https://stackoverflow.com/a/11917884/555690, but I did something else as well: I asked for his device UDID and then added the device on my Apple Developer portal. After that, I created my distribution provisioning profile selecting such device...
... now someone else is probably going to test too. And other people as well.
I fear that I might have to add their devices to my Apple Developer portal, re-configure the provisioning profile, and then re-create the archive all over again.
Is this correct, or is it unnecessary to add their devices to my portal (and thus creating a new archive would also be unncessary)?
You dont have to update a build every time you want to add new tester. It is quite easy to add new tester for the existing build, all you have to do is add the device to your provisioning profile in ADC for your app. Then, download the profile to your computer. Now, comes the moment of truth. Go to the build, in testflight, to which you want to add tester. Then, in the left hand side you will see Permission tab,click there and then it will show you the profile and all the tester who currently have access to the build. Now, update the build with the one you downloaded earlier and then you will see the device in your list. Click on checkbox to turn the permission for the device and voila you're done. You could now distribute the same build to the tester.
Yes you have to add them to the profile in the dev portal each time, however testflight has a button, under Permissions, to update the profile for a build.
You can try uploading your new provisioning profile without having to archive and upload a new build.
You could follow any of the following steps whichever suits you but in my experience I would recommend Process 1 as I have found this more reliable.
Process 1:
You have the UDID of the tester.
Using ADP, add the UDID in the devices list and create a new provisioning profile.
Download the profile and update the same in you project.
Build and archive a new ipa.
Upload it to testflight.
Process 2:
Using ADP, create a new provisioning provile.
Download the profile and upload it in your testflight account in permissions tab.
refresh and you would receive an updated list of usrs on your provisoning profile.
Select the users and Voila you are ON.
What i have experienced while trying Process 2 is that sometimes when you try to download the app, it displays " you dont have permission to download" or "unable to download at this time" even though the user is present in the provsioning profile.
A work-around fix for this issue is that whenever you upload a new build or a provisioning profile, always clear the cahce or in exterme cases, logout and log back in.
Hope this helps.
sorry for my bad english but i'm italian.
I have to release an app that will work on only a few devices. What should I do when the provisioning profile expires? Will the app continue to work or should I release it again with the updated profile?
thx all
No the app will not work after the mobileprovision expiration date. You need to renew your mobile provision, build again and sign the app with new certificate and resent to users the new mobile provision file and the new app.
Edit:
You can submit for an enterprise account an you will not have this issue again.
Not sure what you're really asking, but here is a quick answer with some points that might help you.
Ad hoc provisioning profiles last for 1 year. After a year the certificate is invalid and the application won't work any more. At this point you will have to create a new certificate (usually just renew the certificate will work) and re-release built against the new certificate. This will mean that anyone using the application this way will have to remove the app from their device and install the new package you send them.
When you release an application on the app store the certificate is permanent, you don't have to renew anything and apple will deal with it itself.
If you archived it, all you need to do is create a new .ipa (by selecting "Share" in the organizer) and sign it using the new profile.
If you didn't archive it you need to build it again and you'll need to reselect the code signing identities in the project settings.
Either way you need to send a new build or a re-signed archive to your testers, the new profile alone won't work.
So I'm not that familiar with the process of Provisioning profiles and certificates.
Currently I have one app I'm developing that I can upload to my device.
Now, for testing reasons, I want to write a very simple app and to upload it to my device as well. The thing is, is that I don't want to configure another app in iTunes connect and provisioning profiles, so I thought maybe it's possible just to change the bundle identifier of the second app to be the same as the first.
However, in XCode I get the following error :
"Code Sign error: The identity 'iPhone Developer' doesn't match any identity in any profile"
Any way to make this happen?
If you set the bundle identifier of the 2nd app to be the same as the 1st, the 2nd app will replace the 1st one on your phone.
If you want the ability to have both apps installed at the same time, you need a new app id.
But you don't want to create a new app id for each test project.
The idea is to recreate the Team provisioning profile available for the Company developer program (I guess you subscribed to the individual developer program).
Create a new app id with bundle identifier set to *
Create the provisioning profile associated to this app id
Download and install this generic provisioning profile
With this wildcard profile, you will be able to install any test application.
Please request a certificate to apple through your paid developer account, generate a provisioning profile and install this in mac as well as in your device. then choose your provisioning profile and build and run your app through this provision.then it will install in device. There are details in developer.apple.com regarding to this. If you feels confusion please mail me sandeep.kniit#gmail.com. i will reply you asap.
I want to update an existing App in the App Store, but the profile I used expired (I'm not sure, if it has something to do with the corresponding certificate which also expired..). Since Apple tells me in the How-Tos:
Use the same Distribution Provisioning
Profile to build each new version of
your application
I don't know, what to do. Can anyone help?
The important part is keep the same bundle id.
If your provisioning profile has expired or you has to generate another certificate, it doesn't matter.
Get anew version of you provisioning profile, build your app and it should be fine.
If the profile is expired, simple renew it or generate a new one. I did it yesterday, my dist profile was expired and I simply deleted it and generated a new one.
Once a new one certificate is generated, download it, delete the old one from your keychain and add the new one.
After that, try to build your app. (Sometimes restarting Xcode is required)
Every profile and every certificate will expire. As long as the developer account is still the same, simply creating a new distribution cert should do the trick.
You need to keep exactly two things the same: the enrolled iOS Developer account you use, and the Target Identifier Property in Xcode (becomes the Bundle Identifier in the app). Do that, and the result will be an update to the same app in the App store.
Everything else you can renew, recreate in the portal, install on a new Mac, etc., including App IDs (wildcard on not) created in the portal, Developer or Distribution certificates, and provisioning profiles in the portal, installed in Xcode or on the iDevice. You can also change the Bundle display name (under the icon), the Product name, the Target name in Xcode, and maybe even the name of the app as it appears in the App store (if it's not misleadingly different).
Renew your certificate and provisioning profile at the iOS Developer Portal.