If I create an ad hoc distribution profile and successfully sent out an app in an ad-hoc fashion to a number of users, does deleting that profile then remove the app from that user's device or stop it from being used?
Thanks
Once the .mobileprovision is installed on the device, that version of the app will continue to work on the device until the provisioning profile expires. If you delete the profile from the device the app will no longer function, but will remain on the device. They will get a warning saying they don't have valid provisioning to run the app if they try and launch it.
No, it does not.
There is no way to remove the app from the users device, other then either asking them or wait until the profile will expire.
Related
I'm not in the developer program. I can run the app fine on my iPhone, and on my friends iPhone. But when I unplug his iPhone and try to run the app is says "MYAPP beta has expired".
Anyone know how to fix this without paying apple?
Try this: Create a new user account on your Mac for your friend. Copy the Xcode project from your account to his account. Delete your Apple ID from that project copy. Have him log into his new account on your Mac, and configure it using his Apple ID. Then build the app using Xcode with his Apple ID for the personal provisioning profile, and install the app on his iPhone from his account.
Note that personal provisioning profiles might only be valid for something around one week. For longer profile expiration times on stock iOS devices, you will need to enroll in Apple's Developer Program.
I am attempting to create an Ad Hoc Distribution Provision Profile from Apple's iOS Provisioning Portal with no success. I've selected Distribution Method: Ad Hoc, entered a Profile name, my Distribution Certificate doesn't expire until 6/28/2012, selected an APP ID and DID NOT select any Devices(Optional) click submit and I get no profile.
If I perform the same steps but select a Device I works.
I ran the process about a month ago to test the deployment of an app and it worked fine
Why does the process not provide a profile if I do not select a device? Has Apple made a change to the process that I might not be aware of?
Thanks
I don't know if there Apple changed anything, but why would you want an ad Hoc Profile without a device? There is no way to use the resulting build on any device then, or am I mistaking?
If you are a member of an Enterprise developer team, you can only create the distribution certificate if you are the team agent.
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'm developing a iPhone app and need to send it to my client. In turn, my client will distribute it to many other people for end-user testing.
What kind of Provisioning Profile, Certificate, or Code Signing will accomplish this task? I've heard something about Ad Hoc certificates; is an Ad Hoc certificate relevant for this task?
Yes, ad hoc is exactly what you need for massive end user beta testings.
There is a very thorough and comprehensive tutorial about this, right from Apple. Log into your iOS dev center account ==>> iOS Provisioning Portal ==>> Distribution ==>> Prepare App
Yes, at this point the Ad-Hoc distribution certificate is what you are looking for. The Ad-Hoc certificate allows you to build your app to run on a predetermined list of devices. There are a couple big caveats though:
You need the UDID of every device you want the app to run on.
The user needs to install the provisioning profile for the app as well as the device manually. It's a simple case of dragging and dropping to iTunes - but we're dealing with normal people here... Not programmers.
To Create One: You add all the UDIDs for testing to iTunes Connect and then create a new ad-hoc distrubution profile and certificate. Build your app with the new certificate and the users should be good to go.
What I recommend: TestFlight
Testflight allows you to simplify this process immensely. You just build a normal debug IPA and then put it on TestFlight. They have their own global provisioning profile the users install and run the app with. It's as seamless as mass testing on iPhone can be (Granted, that's not a high bar).
Good luck :)
Note that Ad Hoc certificates are no longer used in the new Apple TestFlight. Testers are no longer added via UUID.
Test Flight builds now require an App Store Distribution Provisioning Profile. The portal does not allow UUIDs to be added to this type of provisioning profile.
Instead, add "Internal Testers" via iTunes Connect:
Internal testers are iTunes Connect users with the Admin or Technical role. They can be added in Users and Roles.
After adding a user, be sure to click on their name and flip the "Internal Tester" switch.
Then, go to App > Prerelease > Internal Testers and invite them to the build.
You can create ad-hoc testing certificates. Your client won't be able to distribute it to "many other people" though. You'll have to know all their device UDIDs and you'll have to add them to your provisioning profile. Remember you can only add upto 100 devices to your account.
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.