I have two XCode projects the first is an iOS app the second a MacOS application. Whenever I build one the provisioning profile for the other is lost. So if I build the iOS app, when I then build the MacOS one I get an error because I use Map Kit. When I look at the provisioning profile in the build settings, the correct one is not even in the list in the menu. I have to double click on it in the Finder to reinstall it.
When I then go to build the iOS one the name of the provisioning profile I had selected has been replaced by a hex UUID and again the correct profile is missing from the list, I get a Code Signing Error and I have to reinstall them (development, ad hoc and App Store distribution ones) by double clicking on them in the finder.
As these two apps work in tandem and I alternate between building them on a daily basis this is becoming quite a pain..
I am using XCode 5.1.1, any suggestions gratefully received
Related
I'm trying to get my first app on the app-store and have been following the instruction of my teacher (creating certificate, app-id and provisioning profile.) When I double click my mobile provisioning file, xcode opens but it just doesn't show up.
When I click the provisioning profile-box in build settings it just shows me a blank space to type into (see screenshot)
After trying to uninstall and reinstall xcode, redo the certificate, app ID and mobileprovision-file and trying to load the mobile provisioning file via window-devices(rightclick my mac) add provisioning profile (It doesn't work. The mobileprovision-file is grayed out)
I don't know what to do.
Even my teacher said he had no idea what the problem is or how to fix it.
I'm running xcode ver 7.1.1
Editor -> Show values (the problem was not the keys but simply that I could not see them in xcode)
I want to submit a new application to the App Store. The application is build with IBM MobileFirst Platform 6.3 so the application itself is a Cordova application. When trying to validate before submitting it to the store, I get the following error message:
After searching for several hours. I can't find any solution which helps for me. The code signature seems to be OK, at least, I think so.
Does anyone know how to solve this problem? I tried to run the application on an iPad 2 with iOS 7.2 and this works great. When connecting my iPhone 5s with iOS 8.3, I can't run the application as Xcode throws an error, he doesn't recognize my iOS version or something while Xcode is completely updated. The archive creation was successful, but the validation not.
New Signing:
Your provisioning profile doesn't seem right.If there are so many "junk numbers" then we can say something's wrong.So I recommend you to check your steps or make everything from scratch:
Steps to make your app ready for App Store submit:
1-You create an App ID from member center
2-You create a Distribution Certificate
3-You create a Distribution Provisioning Profile with this App ID and Distribution Certificate included
4-Download this Provisioning Profile to your Mac
5-Double Click on this Provisioning Profile
6-in xCode make sure you selected the right team under Target -> General -> Team (This must be the team that includes App ID and Distribution Certificate that you just created)
7-Click xCode -> Preferences (or cmd,)
8-Under Accounts section, choose your team
9-Click "View Details" button
10-Click the "Refresh" button and wait for refreshing to finish
11-If you see the recently-created and downloaded provisioning profile, it is ok to click 'Done' button
12- Now, under Project and Targets, choose the recently-downloaded provisioning profile for "release" and "distribution" (also for the 'Any iOS SDK')
13- Then choose the right code signing identities that are derived from this provisioning profile (for release and distribution and also for 'Any iOS SDK')
14- Now it must be successsful
The problem had nothing to do with the incorrect settings of the project, but with IBM Mobile First Platform. This platform creates an buildtime.sh file which is not signed. Apple won't allow this anymore, so this is why the error message keeps appearing.
For future reference: https://mobilefirstplatform.ibmcloud.com/blog/2015/05/01/recent-changes-in-apples-app-submission-process/
I can't get Titanium to accept my provisioning profile.
I am using Titanium to build a development app to run on my iPhone and that of two others. I have created the certificates, app ids, and provisioning profiles but when I come to create a package for distributing via iTune I get the error:
"Specified Provisioning Profile is invalid or is the wrong type"
I have tried pretty much every option I can think with respect to ways to build the package and types of provisioning profiles but it consistently fails with this message.
Is there a solution to this problem?
I always get xCode to build correctly first. I set up a blank helloWorld application in xCode and follow the Apple guide there on their resources site. Once this is set up titanium will pick up on your valid certificate and provisioning profiles.
Check that when you are trying to run the project you have removed any invalid or old provisioning profiles. This can be done under xCode device manager > Selected device , click the settings wheel in the bottom left > Show provisioning profiles... You'll then see a list of profiles you re trying to build with, if you've created a couple that have the same name it could be selecting the wrong one.
I have created an iOS application, and wanted to submit it to the App Store.
I saw a tutorial on how to do that, and understood that I need to create a Distribution profile and replace it with the Development profile. So I did that but before sending it to the App Store. I want to check it last with that profile on it (the distribution profile).
Can I run Xcode project when I add a distribution profile?
because when I tried running it on a real device, an error popped up: "the provisioning profile "XXXXX" was not found".
So i went to the Devices tab and tried adding the file of the provisioning profile, and it didn't allow me to.
What should I do?
You can't use distribution profile to run the app on your device directly from your device.
Now Apple provides beta testing of apps using iTunes Connect. So you can opt for that option as an alternative.
Refer Beta Testing Your iOS App for more details
Yes, you can do by applying small tweak.
Open you Xcode project
click on your target.
choose edit scheme from list.
choose Run tab from left.
select info tab from top.
select Build Configuration and choose release from drop-down list.
Now delete your existing app, from device if exist.
And run the app from Xcode.
After completion of compiling for app, it would show some error dialog and will stop execution, ignore it.
Now app is installed on your device with distribution profile.
Re-run the app.
Cheers!
I have a really annoying issue, I have a xcode Project that I needed to copy and make some Changes to (only some text Changes), so I started of by copying the whole Project and Place it in a Another folder on my mac, I then created an new provisioning profile and a new App ID, selected all the exsisting devices and downloaded the profiles, doubleclicked on them and then compiled the Project. The app can be installed on my ipad, but when I try with Another ipad (that was selected in devices) it give me an error saying this device isn't allowed to install the app... What could be wrong...?
I hate the Member Center for reasons like this. Seriously, the best thing you can do is to delete everything (except for AppID) and start fresh.
UPDATE
For a clean start:
Delete all certificates and provisioning profiles
Re-create your certificates, provisioning profiles
Import them into your project/refresh code signing/refresh team
Build Settings > Code Signing: Set your Code Signing Identity & Provisioning Profile attributes
Select "iOS Devices", your schema, and then Archive
Last note pertinent to your specific issue: Make sure you are creating an Ad Hoc provisioning profile and archiving (& distributing) under that profile. I know how dee-d-dee this sounds, but it happens when you're not paying attention ;)