Provisioning profile issue, I just can't run my application on device - iphone

I'm getting this message when I try to run on my device:
A valid provisioning profile matching the application's Identifier 'my app bundle ' could not be found
I am able to run the app on iPhone Simulator without problem.
I was able to connect to the device before, I don't know what is going on...
I already deleted everything and tried again, even with a new App ID created on the portal but it didn't work either.
I just don't know what to do to run the app on my device?

A valid provisioning profile matching the application's Identifier 'my app bundle ' could not be found
Please ensure that the identifer is consistent with the App ID you created for the provisioning profiles on developer portal.
For example, if you created App ID "A1B2C3D4E5.com.yourdomain.*" and assigned it to your provisioning profile, your app must have a bundle identifer like "com.yourdomain.someapp" so that it can be correctly signed.
Also I don't think space character is allowed in the identifier. See Information Property List Key Reference:
The bundle ID string must be a uniform type identifier (UTI) that contains only alphanumeric (A-Z,a-z,0-9), hyphen (-), and period (.) characters.
You may refer to:
"Creating and Configuring App IDs" in iOS Team Administration Guide.
Bundle Identifier and Provisioning Profile

Running an app on simulator doesn't require code signing and hence no provisioning profile. As it was working earlier and you've tried deleting and reinstalling everything, see whether your code signing certificate has been revoked or expired.

Related

No value was provided for the parameter 'appIdName' when provisioning

I've just enrolled in Apple's iOS Developer Program (account type: Individual).
In my Xcode organizer on my iPhone 4 device I click "Add device to provisioning portal" => Xcode asks my credentials => I enter them => I see "No value was provided for the parameter 'appIdName'." dialog window.
What am I missing?
Part of the process in Xcode's automated submitting of certificate requests is that it looks for a "Wildcard" app ID. If you're missing this (for some reason, it's created on some accounts automatically and not created automatically on others?), this automated process will likely fail.
To fix it, try the following:
1) "Revoke" any existing certificates you might have from within the developer portal
2) Create a new "App Id"; title it "Wildcard"; and enter only " * " (without any spaces or quotes) as the suffix.
3) Try the automated certificate request from within Xcode again, and it should now work
Cheers!
I'm getting the same issue in Xcode. I think it's related to the wildcard app ID that Xcode creates for you. There seems to be an issue with that process that then cancels the device addition process that you're trying to complete.
You should still be able to add the device via the iOS Dev Center. Once logged in, go to the Provisioning Portal and you can add the device there.
Not perfect I know, but should allow you to start building apps and testing on your device until the Xcode issue is resolved.
You could avoid this problem by making App ID with wild-card id in iOS dev center.
I guess Organizer could not follow the updated policy related to App ID in iOS Dev Center/Provisioning Portal.
App ID with wild-card("*") is seems to be restricted in some function,
for example, Push Notification, Game Center.
and
developer also seems to be required to make sure the security option for the app related to the App ID.
Actually, my initial goal was to be able to test my app on iPhone device. Clicking "Add device to provisioning portal" still results into the subject error, but anyway my iPhone device have been added somehow to the Provisioning Portal and now I can see my app on iPhone (I haven't even tried to add it via iOS Dev Center). My guess is that this procedure takes multiple steps to be completed, and only the last of them still fails now, while the rest of them do succeed.
In my case the provisioning profile for that application was invalid, then I did the following steps:
Login on Developers Portal
Click on Certificates, Identifiers & Profiles section.
Go to Provisioning Profiles, in the list I realized my app profile
was invalid.
Click to edit it and selected the corresponding certificates (all)
and devices (all).
Download the profile and un Run. Issue solved.

Upload IPhone app to device instead of other app

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.

provisioning profile problem?

i am running my apps with different provisioning profiles.(I am creating one
provisioning profile for each application an running in device). but i want to
run all applications in my device(without overwritting previous apps) with only one provisioning profile.I hope , it is possible.when we set apple id only in plist file as "com.myappleid.identifer(123145^&)" identifier will come uniquely automatically.can any one give simple tutorial to create the provisioning profile?
can i use my previous development certificate for that provisioning profile?
I think you want a wildcard provisioning profile. If all your apps start with the same identifier, e.g. com.myappleid.App1, com.myappleid.App2... then you can create a provisioning profile with the identifier com.myappleid.* which would match all of the above.

How can I update my App in the App Store if the Distribution Provisioning Profile expired?

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.

Why must the bundle identifier be changed prior to submitting an iPhone app to the App Store?

I need to understand this piece better because when I reached that step in the app submission process, my comprehension went to hell.
While developing my app, my bundle identifier was com.yourcompany.${PRODUCT_NAME:rfc1034identifier}.
The instructions say
In the Properties Pane of the Target Info window, enter the Bundle Identifier portion of your App ID. If you have used an explicit App ID you must enter the Bundle Identifier portion of the App ID in the Identifier field. For example enter com.domainname.applicationname if your App ID is A1B2C3D4E5.com.domainname.applicationname. If you have used a wildcard asterisk character in your App ID, replace the asterisk with whatever string you choose.
Here are example App IDs and what
should be input into the Identifier
field in Xcode.
Example App ID:
A1B2C3D4E5.com.domainname.applicationname
Identifier to enter in Xcode:
com.domainname.applicationname
Example App ID:
A1B2C3D4E5.com.domainname.* Identifier
to enter in Xcode:
com.domainname.
Example App ID: A1B2C3D4E5.*
Identifier to enter in Xcode:
full_reverse_dns_company_and_application_or_suite_name
In the provisioning protocol, my App id is XXXXXX1111.*. So In the identifier I entered com.mysite.myAppName, which was absolutely arbitrary, but that seemed to be the point. I built the app submitted it, everything seemed to work alright. But then I tried to create the Ad Hoc distribution and upload it to my device and what happens is that the app loads, and then crashes after about 3 seconds. At first I couldnt figure out what was going wrong so I retraced all my steps until finally I got to changing the identifier in the target. I changed it back to com.yourcompany.${PRODUCT_NAME:rfc1034identifier} and my app then started to work perfectly on my device with the Ad Hoc distribution provision.
My question then, is what do I need to write as the value for the identifier in order to make sure that my app doesnt crash when the app store team is reviewing my app?
Thanks!
EDIT
The Ad Hoc Distribution, App Store distribution, and the Development profile i was using all have the SAME app id, which is a wildcard XXXXXXXXXX.. In the organizer, the only provisioning profiles i have for my ipod touch are my team provisioning profile and my development profile. Under the developer profiles category in the organizer, I have team, distribution, ad hoc, and development, all with '' app identifier. in the 'provisioning profiles' i have the same 4, with my ipod touch as an included device on the ad hoc profile.
In my info.plist my id is com.mysite.myappname. Everytime i try running the app on my ipod touch using my distribution ad hoc profile, i get the dialog box:
'cant run "myappname" on ipod "my ipod name"
The ipod 'my ipod name' doesnt have the provisioning profile with which the application was signed. click install and run to install the provisioning profile 'dev name Ad Hoc' on 'ipod name' and continue running 'app name.app'
when i click install and run, the app loads, and then crashes after 3 seconds, as i said before. it seems as though the provisioning profile is failing to install on the ipod touch.
The important thing is that the bundle identifier in your info.plist file, the bundle identifier in your provisioning profile, and the bundle identifier associated with your app ID should all match up.
If you were able to do a distribution build, it means that the bundle identifier in your provisioning profile is the same as the one in your info.plist file. And if Itunes connect accepted your submission, it means that the bundle identifier associated with your app id is also the same. So you are in good shape there.
Reading your description, it is possible that your add hoc distribution profile does not have the same bundle identifier as your app store distribution profile. If so, this would explain why you had to change the bundle identifier in your info.plist when switching from an app store submission to ad hoc distribution.