i am developing an native ios application on mac os mavericks image on vmware, i am doing a training in a company. this application contain PushNotification service. i have download a video tutorial and i complete all the tasks as the video show. but in the end when i install the provisioning profile it show this warning message : "valid signing identity not found" . i have work on this issue many days.
i am new in ios developing, so day by day i read questions of developers that have this issue also and i've read the answers and try to fix it but no result.
can anyone help me and guide what to do. down i will notice what i've see and i feel that this could be the problem and i can't do anything:
- when i create the provisioning profile , they gave me numbers of certificates to chose, none of these certificates is the one that i create.
There are probably many reasons for this message and many more potential solutions.
I often see this error message display when building. Quitting and restarting Xcode usually resolves the issue for me.
Have you tried downloading the provisioning direct from apple site? Sometimes I have problems when I try to update directly from xcode.
Related
I am getting message "TestFlight is Currently is Currently Unavailable. Try again later" when trying to install from TestFlight app. My outside testers get a message "[App Name] beta has expired" when trying to run the app. When trying to renew from TestFlight they get "TestFlight is currently unavailable. Try again later." I've been trying again later all day and just wanted to see if anyone else is experiencing this.
I had this same error.
Discovered that the company certificate was expired, and therefor all provisioning profiles as well.
1. Renew the company certificate (download, install on your computer)
2. Renew the provisioning profiles (edit, select new valid certificate, generate, download and install in xcode)
3. Repost the app to iTunes connect
problem solved :)
If you're new to Xcode, be sure to note the difference between a CERTIFICATE (first large red arrow below) and then a PROVISIONING-PROFILE (second large red arrow below). Basically provisioning-profiles are made using a certificate. So first make a new certificate, and then set a provisioning profile to use that certificate.
First, certificate...
Then, provisioning profile...
In the second image, click on the "Distribution" provisioning profile (the one with the purple arrow.) Then click to edit it, and you will then see the third image below. Note that somewhat annoyingly, the DATE is the only way really to distinguish your corporate certificates, when, you have more than one. (Ultimately you can, generally, just throw away the OLDER one, but it's clearer if you leave it so that you can clearly see how you select one or the other, as in this third image.)
Editing a provisioning profile...
A minor point is that you'll have to make a new build (so, increase the build number in Xcode, then archive, and then send up that new one) because you'll get a "redundant build" warning if you fix the cert/profile (i.e., as described in this answer) and re-submit.
Another possible reason for this message:
You accidentally removed the affected user from the TestFlight external testers group.
Adding him again would fix the issue.
Problems with certificates have been identified in several answers as the cause to this message. However, there's another possible (yet stupid) cause that leads to this situation.
You may see this error if your device's date/time is not set correctly. So make sure you set the correct date or "Set Automatically" is enabled under Settings > Date & Time.
I spent 2 days "trying again later" until I realized this.
I was ultimately able to fix this message by uninstalling and reinstalling the TestFlight app from scratch. Worth a try if the other answers don't fix your problem.
Make sure TestFlight can use Mobile Data if working without Wi-Fi. Otherwise it fails with this generic error.
Had to disable 'Use cellular data' option in Settings for Testflight. I did not have cellular data internet and was connected via wifi. Looks like testflight tried to use cellular data with that option being on.
Did a factory reset and that fixed it for me.
Actually just waiting solved the problem.
I had to wait around 16 hours and then it worked normally, without doing anything particular.
Sometimes the error message is just what it is, no need to panic !
Ahh devs ;)
Currently, Testflight is experiencing issues. It's always worth checking Apple's status page
Another possible reason , if your mobile app build is in processing state for a long time.
Just wait for the build to complete apple processing solved our issue of Testflight currently unavailable.
I had this same issue when using my personal email for beta testing my app, then using my apple ID email for internal testing.
I solved this issue by removing my personal email from all testing tracks, then deleting the TestFlight app and downloading it again. I now only use the one email (my Apple ID) for all testing.
I had to go to https://developer.apple.com and accept a new version of Apple's Developer Agreement
I am a PC person, and not much of a coder, so I have a developer building an app for distribution to the Apple App Store.
It's done, working great, but he tells me there is problems during the submission. He got an error ITMS-90034
Not having a Mac or the ability to run Xcode or the Application Loader, I'm in the dark here.
What does that error indicate, and why would it take multiple days to solve this problem?
Thanks for your insights.
ITMS 90034 means there is problem while getting the certificate(.p12) which you can see in Keychain Access, please check the certificate with valid provisioning profile.
I have faced this Issue after cleaning my Keychain Access where I installed certificate multiple times then it's linked with xcode6.0 where I am able to upload the build using Apploader.
you can prefer below link for more details.
ITMS 90034 Resolution
Thanks !!!
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!
I have made a game using game maker and successfully got it exported to xcode 5 on my mac. I have also successfully played the game on my iphone, so the game does work quite well.
I do have the provisional profile, the certificates needed (developer and distribution). I only have my certificate once in my keychain.
I also created my app on the developer website where it is now ready for upload.
Whenever I try to upload I can select my app and it starts uploading, only after a short time I get the error:
ERROR ITMS-9000 The bundle "com.grown-apps.whopays" at bundle path payload/whopays.app is not signed using an apple submission certificate at softwareassets/softwareasset (MZITMSPsoftwareassetpackage)
But I have signed everything in xcode 5. I selected the distribution profile to sign with.
It doesn't matter how I try to upload, using application loader or xcode 5, I get the same error.
I have now tried for a WHOLE WEEK searching the internet, and I just now got to the end where I simply cannot stand this anymore. I have followed every video or text guide I could possibly find. I have found many people with the same issues both here and everywhere else, none of the solutions people came up with and worked for many just didn't work for me.
I am now sitting here at 3 in the morning almost bald from ripping off my hair in desperation in hoping that someone somewhere has ANY idea what I can try next, this really is my last cry for help. I have used more than 100 hours just researching on this problem and it has turned up nothing for me.
Please help me so I don't have to take the final step and throw my expensive mac out the window!
I had this exact same problem and just resolved it today. In order for me to get anything from Windows to the Mac via Game Maker Studio, I had set the certificates "Trust" setting in the Keychain Access to "Always Trust" for both the provision and the distribution.
HOWEVER, for the app store submission, I had to change the "Trust" setting back to "Use System Default" for both the certificates. Also the keys attached to the Certificates are always put on "Allow all applications to access this item" in the "Access Control" tab of the respective key, regardless of the Certificate "Trust" parameter. I hope this helps people in the same bind.
I am trying to install an app on my iPhone from my computer using Flash cs6. I had it working before but my p12 expired. My friend on a mac made me a new one. From developer.apple.com I created a new provisioning file. I run the app install and I get this error.
Error Creating Files.
Installation Error: PackageExtractionFailed.
Device Error: please check if there is enough space on the device.
I have enough space. I think this is an issue with the two files and a combination of many other things. There are just so many options when making the provisioning file that I don't know what ones to choose for DEVELOPMENT.
I am putting all the errors in length in hopes that, when we find the answer, someone will find this in a search and it will help them too. It's very hard to find info on this error. Any help would be greatly appreciated. Thanks
http://www.instructables.com/id/How-to-use-Adobes-iPhone-Packager-without-an-Appl/step2/Exporting-the-App/
try with this one, if it work make another provisioning profile