I have a provisioning profile, registered my device, added the certificate, and created an app id for my application. I set the provisioning profile in the Code Signing section on XCode and the App ID is set. I had a problem where it said iPad-only applications should not use armv6 and the build failed so I followed some advice I read and set it to build active architecture only and now I don't receive any warnings, but the build still fails. The iPad is plugged in and I selected it from the drop down for running. Also I am using XCode 4 and I was trying to follow this tutorial http://mobile.tutsplus.com/tutorials/iphone/iphone-sdk-install-apps-on-iphone-devices-for-development/.
My professor created the provisioning profile and the app id, but I checked and everything looks fine except for one thing. When I look at the app ids on the developer page under "Apple Push Notification service" it says unavailable for the app I'm using, while some other app ids say "Configurable for Development". I'm not sure if that has to do with the problem but I thought it might be related.
I also tried doing a clean build because I saw that suggested somewhere, but it still failed so something must be wrong with how I set it up.
Does anyone have any ideas on what I might be doing wrong?
edit: just thought of something else, under the organizer page if I click on applications my app isn't there and if I try to add it I get an error message saying "No Code Signature Found"
Also, if I look at the provisioning profiles the app id section is blank. Do I need to link the provisioning profile up to the app id some how?
Take a look at this, It might be helpful https://developer.apple.com/legacy/library/technotes/tn2250/_index.html#//apple_ref/doc/uid/DTS40009933-CH1-TROUBLESHOOTING_GUIDE-CODE_SIGNING_ENTITLEMENTS
Related
I'm trying to run my app on a new device through Xcode 7 but everytime I click to run I received this error: "No matching provisioning profiles found: None of the valid provisioning profiles allowed the specified capabilities: Features: push and inApp purchase". I don't know what this means. I've never seen a message like this before when running apps on another device with Xcode 7. Does anyone how I can fix this issue so I can run my app?
If you haven't added your apple developer id to Xcode, I'd suggest doing this now. once you've done this and in the project navigator, if you highlight the project, then on the middle-most pane, go to the Capabilities Tab and make sure In App Purchase is enabled. If not, enable it. It should pop up asking which developer ID to use, or ask you to add one.
Choose the ID in question, then it'll add the entitlements to the app.
Whats going on here is that the provisioning profile which your app is using, hasn't been enabled in terms of IAP's.
There's more to read about that here:
https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/Introduction/Introduction.html
The app which i created worked well in all devices other than IPhone6 . I got the following error message in XCODE 'The application could not be verified.' . I deleted the app and then reinstalled it as per the suggestion given in the link:
iOS app 'The application could not be verified' only on one device
I want to know that what might be the actual cause of this error message. !!
I don't think, this is an xCode issue. This can happen under many conditions. Like-
Provisioning Profile mismatch:
Scenario 1:
When first time, you had built or installed the app in your device, you may have used a different certificate(paired with a different provisioning profile) than now. So, when you try to re-run the app, the device got confused. The ways to fix it-
Delete the existing app and re-build. That way, you don't have to figure out which certificate, you used the first time.
However, if you know which certificate and provisioning profile you used earlier, then just switch to those.
Scenario 2:
May be you are trying to use distribution profile where you supposed to use development profile.Fix-
Assign any valid development provisioning profile under the code signing.
Device not added:
May be the device is not added in your developer account under Devices or
May be the device is added under Devices, but when you created the provisioning profile, you forgot to select the device on which you are trying to run your app.
Please make sure that your are using the latest version of XCode i.e 6 for creating the build, and then tell us what is the exact error you are getting.
I am trying to create a widget on the Today extension but have been having some issues regarding entitlements with my provisioning profile.
In essence I'm just trying to output a greeting message on the Today extension. But I am not able to view this message because of what I believe is an entitlements/provisioning profile issue that is preventing the App Groups from being used. I am using XCode 6.1
The error I'm having is below (apologies for all the links; I don't have enough rep points to post inline images it seems)
http://imageshack.com/a/img540/6973/eYBQly.png
And on my Developer Account, you can see that I've enabled App Groups on this App ID
http://imageshack.com/a/img912/3636/jY84SI.png
But it still doesn't seem to work, i.e. I still get the errors pertaining to App Groups not being a part of the App ID which in turn is, I believe, preventing the Today widget from working.
Would someone be able to please explain how the provisioning profile works and what it is that I might be missing here?
Follow these steps
Find your App Id and make sure your App Group state is Enabled.
Use your App Id to create Provisioning Profiles and download to your computer then double click it
Check Xcode's Identity to make sure your team is the right one. If you have problems, click fix issue
Have a look at this link too
https://developer.apple.com/library/content/documentation/IDEs/Conceptual/AppDistributionGuide/AddingCapabilities/AddingCapabilities.html
This must be the worst question ever asked.
I'm almost ashamed to ask it but I can't wrap my head around this.
We are trying to push my app to itunes connect for beta testing.
Now there is no way to do this because XCode 6 gives all signing errors available.
We are able to run the app on the development device just as usual. We have the profiles.
But when we set the release sign identity to iOS Distribution, the hell breaks loose.
No matching identity was the first error. Fix issue releases another error:
No provisioning profiles with a valid signing identity were found.
It's useful to note that XCode knows this better than I do so it changes the code signing identity back to developer.
That's not me, I want to distribute.
Ok so at this time we're stuck at this error. We don't know where it came from, but we do know there was another error.
While pressing the submit button in the organizer the error was:
"You already have a valid provisioning profile"
According to the apple documentation I should press the revoke & request button but that isn't there.
So here we are, totally stuck and have no idea where to go now. The apple docs are incomplete, the signing gives errors but no logs. Errors messages change, but are consistent.
What the hell should we do now?
Reinstall OSX and remove all existing profiles? What will happen with current clients running apps on those profiles?
Have a look in yoru account and check that the provisioning profiles are active and not invalid. You might need to regenerate it.
You might also want to download them manually and install them yourself.
Sometimes I've had to archive the app then submit 'manually' using application loader.
I would recommend going back to basics:
check your development and distribution profiles on the developer site. if you have recently renewed your annual subscription, you might need to recreate them.
when you are archiving make sure you chose the real testing device, not a simulator.
if both doesn't work, create a new empty project and sign it with the profiles and archive. if that works, then check if you altered the bundle settings. if it doesn't work, delete your profiles and recreate them.
I hope that helps.
Hmm. I understand the plight of having to deal with the overly complex process of app submission which should have been rather simple.
Two things:
Make sure you delete all the provisioning profiles. Revoke and request a new one. Create a new certificate with distribution licence (you can make upto 3).
Once you've done that go to tour XCode > Preferences > Accounts and open up the apple id you find there. Refresh and that should download and fix redundancies.
For more I think you should also give this a read.
How do you beta test an iphone app?
About you second issue. What would happen to apps packed with previous profiles?
Well, your app is not bundled with a particular profile and so you can create a new one and use that without pain
I was already looking through some other threads here with the ITMS-Error 9000, but they didn't help me to get my App passing the submission to the App Store.
I have NO errors or warnings inside XCode.
The App is perfectly working on iOS Devices & Simulators.
EDIT: What I have already tried:
Changed Deployment Target from iOS 7.1 to 7.0
Checked the Bundle ID in iTunesConnect and inside Xcode
Checked for any errors and warnings --- removed / fixed them
Do you have any additional ideas what it could be? Without any errors or further information it is hard to find out what the reason is.
UPDATE2::
If I try "just" to "Validate" instead of "Distribute" in the organizer after Archiviing it i get the following Error
Its an Issue with Apple's Server I tried validating the app it said "Unable to process app at this time due to general error" a quick search about it on SO said its got nothing to do with our code or project but some process running at Apples server
Assuming that your binary icons does not meet as per apple's human interface guidelines.
It most probably seems to be the issue with the profile you are signing your app with. You got to make sure that your are signing the app rightly with proper distribution profile. Also check out for the bundle identifier and make sure that it is same as the one you have given in itunes connect.
Check this link!
You should be creating the binary with the simulator or some device connected.
Try it:
Unconnect iOS device from your Mac,
Dont select any simulator, just leave it as it is, iOS device option
Archive it
Publish it
Make sure you're using a provisioning profile for the App Store (not for Ad Hoc distribution)
Then select this profile when building your app.
I would guess this all has something to do with Apple making system changes to prepare for iOS 8 and in doing so somethings got broken.
The issues look to have just been resolved by Apple. I just successfully submitted an app that was previous showing the same problem you had. If you look at your Provisioning Profiles, you should notice that Apple has removed your app's previous Distribution Profiles.
To get your submission working again, all you have to do is recreate your App Store and Ad Hoc provisioning profile, but make sure to use a new name and you should be good to go. You were not alone on this one. A bunch of people experienced the same problem and there were a lot of posts about it on the official Apple Dev forums.
Please check the Distribution Profile that you are signing your app with at iTunes Connects. make sure that it is still valid. I had same issue couple days back and after a struggle , i found out that somehow my provisioning profile was not valid anymore. Creating a new profile and submitting app with it solved my issue.
Apple have deleted corrupted provisionning, you just have to regenerate it and make submission works again !
Connect to your iOS Developer
Certificates, Identifiers & Profiles
Provisioning Profiles / Distribution
Here you can see some certificates missing. You have to re-create (Distribution / AdHoc). Note, you have to change certificates name !
In Xcode, refresh your certificates, set the right one in Build Settings, and submit...
I called today the Apple Developer Support and i get one very very simple answear to this issue.
You have to create all your certificates, provisioning profiles etc with Apples SAFARI browser.
It is not working "always" proper with Mozilla Firefox or other Browsers. So if you get such an error, try to recreate it with Safari! It worked like a charm!