Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 9 years ago.
Improve this question
After creating Profile the status is still PENDING. How long it takes?
Its spend about 2 hour but status is still pending.
I am getting this problem first time.
Had the same issue but now it works. I tried out many things but nothing helped and I haven't seen any message about a maintenance by apple.
Apple were apparently performing maintenance for over 24 hours yesterday. There was a message:
"We are performing maintenance on the provisioning service"
Now they have removed this message and the provisioning service is still not working. It used to be immediate and as soon as your sent a request it would be done a few seconds later after your refresh the page.
I'm outraged as I actually signed up to the program again yesterday to start building an app. The iPhone simulator doesn't work for video editing for some reason and I can't deploy to to the iPhone without provisioning so I have no way to test my code.
The lack of information from Apple is ridiculous seeing as they are well aware there is a problem but have not even bothered to notify the users and have even taken down the old notice. This must be very confusing for any novice developers who are provisioning for the first time and is also severely delaying the development of my app.
I'm getting this too, It appears to be an issue with Apple. Mine has been pending for 30 minutes.
EDIT: It's fixed
Yes for me also this happened. See apple message in same page.
"We are performing maintenance on the provisioning service"
Also someone reported same issue in apple forums here.
Related
Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 7 years ago.
Improve this question
I was in the middle of woking on a App in XCode 7 and was pushing it to my phone after making changes. All of a sudden, i was getting a general "security" error.
The app had already been verified and the developer trusted. The XCode console outsputs:
error: failed to launch '/private/var/mobile/Containers/Bundle/Application/C684E25D-F370-4DFC-B39F-C4508B653EA1/myapp.app' -- process launch failed: Security
If I go to System Preferences > Profile in my phone and try to verify it, it doesn't do anything and doesn't report any feedback.
I've tried deleting the app, restarting xcode, restarting my phone, etc..
And now, none of my apps will install on my phone for development -- note, I'm only talking about directly launching an app from Xcode to my phone. I'm not using the App Store.
It seems the server Apple uses to verify apps is down again. This has happened before: iOS 9 enterprise app verify failed
All we can do for now is wait until they resolve the issue.
Having the same issue as you, hitting VERIFY does nothing except briefly change my email at the top to 'Verifying", and then changes back. No feedback or notification.
My first thought would be as Dominic said is that the server on Apples side is down. Not sure if that server is listed here:
https://developer.apple.com/system-status/
But they all seem to be operational, so I guess all we have to do is wait.
Edit: As per Dominic's post, this is the proper site: ppq.apple.com, which is currently down.
http://www.isitdownrightnow.com/ppq.apple.com.html
For any future people with this error:
If you are having trouble verifying apps on your device, check the above site, if it is down that is almost certainly the cause.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 5 years ago.
Improve this question
We're building an iOS app in iOS 8 using Apple's version of TestFlight (integrated with iTunes Connect, of course). However, the system regularly refuses to send the "new build" notification e-mails to internal testers. In order to get build notification e-mails, I have to remove users from the internal testers group and re-invite them. Even when I have done this, the build notification e-mail (although it lists the desired version of the app) doesn't actually trigger an update in my TestFlight iOS app.
Points to note:
I have the Connect and TestFlight apps installed on my phone.
This has worked in the past with earlier versions of the app.
I have found other similar questions on Stack Overflow such as this and this one, but none of them seem to deal with the "this happens to me repeatedly" problem. Besides, most of them seem to suggest "remove all internal testers, disable beta testing on the app, then re-add them all" which is not a sustainable solution when we'd like to release multiple new builds per day through our continuous integration system.
Does anyone have any ideas?
ETA: I found an Apple Developer Forums thread on the subject. Not much help but it might be in future.
I had the same issue, Making changes to the "What to Test" field in the Build page and saving caused notifications to go out instantly for me.
When you upload a new build wait for a bit (I wait an hour) for all the processing to finish, then add the What to Test info and hit save. This seems to work for me quite well.
Using Edit, I removed the testers and saved. It says you can't test without testers. I added existing testers to the new build and saved. When I refreshed the page, it said they were notified with the current date.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
We have problems releasing our Newstand App to the App Store.
It always gets rejected, because the validation of the receipts coming from the subscription In-App-Purchase seem to fail in the live (non-sandbox) environment.
The thing is, we tested everything against the sandbox environment and everything works fine. For the release version, we made sure that we use
our validation webservice that validates against the apple live-service, NOT the sandbox validation service.
So everything should work, but in the review process it always fails.
Does anyone have experience with similar problems?
Apple does test against the live-environment, right? Because we have to submit the live-Version of our App, validating against sandbox does not make sense.
We submitted the IAP items together with the App, but that should not be a problem, as the Apple testers seem to be able to purchase the subscription,
just the validation does not work.
Ok, I found sth in the Apple documentation:
https://developer.apple.com/library/ios/#technotes/tn2259/_index.html
(way down under Frequently Asked Questions 16.)
"How do I verify my receipt (iOS)?
Always verify your receipt first with the production URL; proceed to verify with the sandbox URL if you receive a 21007 status code. Following this approach ensures that you do not have to switch between URLs while your application is being tested or reviewed in the sandbox or is live in the App Store."
We misread the line above "Use the production URL http://buy.itunes.apple.com/verifyReceipt once your application is live in the App Store.", thinking Apple would use real server validation iin review process, but they also use sandbox environment.
Difficult to find this little line, they should make that fact more prominent in my opinion!
So hopefully this will resolve the issue.
Thanks for your comments though!
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 7 years ago.
Improve this question
I'm trying to submit an app tonight and I can validate the app find but when I go to submit, get the following errors:
Apple's web service operation was not successful
Unable to Authenticate the package
exception occurred when creating MZContentProviderUpload
Has anyone else seen this error?
Just had this happen on Xcode 7. Quit Xcode, opened it back up, resubmitted and it worked fine.
EDIT: I agree with #arlomedia in the comments, this is a problem on Apple's side. Just had it happen again and restarting did not fix it. Maybe I just got lucky the first time :)
That seems like a temporary issue from Apple's side. It should have been fixed by now. Try uploading again.
I saw a slightly different error message, six times in a row:
Exception occurred when creating MZContentProviderUpload for provider. (1004)
Restarted my mac, resubmitted and boom - worked.
Can't say for sure if it was the restart, could have just been something on Apple's servers as the other answers point out.
I kept getting it for several days until I changed Deployment Target from 3.1.3 to 4.3.
My error also said "The bundle does not contain icon for iPad exactly '72x72' pixels". I checked the icon and updated it like 5 times :)
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 5 years ago.
Improve this question
I have just tried to uploaded an app through the Application Loader, but it froze in the middle of the upload (the percentage were in the middle and the window was not responding).
However, on iTunes Connects I now see that the status is "Waiting for Review".
Is it possible that the status changed even though the binary didn't upload completely?
Or the upload did complete and just my view was stuck?
Finally the question is if I should reject the binary and upload again, or safely continue with the review.
While "Waiting for Review", When you resubmit your binary by rejecting your old, you lose your line in the queue.
If you reject your binary, the status of your app will change to
Developer Rejected. When you resubmit your binary, the review process
starts over from the beginning.
From p. 83 in http://itunesconnect.apple.com/docs/iTunesConnect_DeveloperGuide.pdf
Demz answer is not correct (I don't have the privilege to comment it).
While it's in "Waiting for Review" you can change the binary at any time, without losing your line in the app review queue, so, if you want to be sure, you can change it without any problems.
I would definitely reject your application, and re-upload it. If it turns out that nothings wrong, then no problem but if something is wrong, you may end up getting rejected by Apple.
In addition to this, you may want to consider using the new application loader built into Xcode, I've found using it to be a much more streamlined process.