iOS9 - Can't Verify Any Apps [closed] - ios

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.

Related

iOS Crash Report Service [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
Improve this question
My concern is to improve my app by collecting crash reports via the crash report service in iOS. For internal testing I uploaded a beta version of it using Xcode, containing a built-in error throwing NSRangeException. After archiving and uploading the app to the store it was installed on an iPhone 5s running iOS 9.3.3 using TestFlight. In my opinion I followed all the steps described here, but with no success.
In the diagnostic settings of the device, automatic crash reporting is enabled and I can see various crash logs (>10) caused by my app. On the iTunes Connect website I see only three overall crashes and just one is shown in the Xcode Organizer. Even after syncing the device through iTunes nothing changed.
Contacting Apple-Support didn´t help either. because they had "very little information available".
For stability improvement I need to make the crash reports available, so I have a couple questions:
Which steps are done internally by the crash reporting service and how long does it take to see some results? (As mentioned in iOS developer library documentation it can take up to three days, which are long overdue by now).
Are the reports caused by the same error gathered and reported as a single entry? If not what is the procedure?
I already searched for some similar questions and came up with the following information:
Users say that the iOS app crashes without any further explanation
Not able to get crash reports in iTunes connect for a live application in AppStore
I can not get a crash report in iTunes Connect
submit crash logs to Apple via iTunes Connect
How do you view TestFlight crash logs?
I hope somebody has deeper insight or already gained more experience using Apple`s Crash Report Service and could share this information. Thanks a lot in advance.
Fabric may be a good choice.
It can collect you crash report, and give a crash description.

Unable to Process the authenticateForTransportDiscovery \ validateMetadata request [closed]

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'm trying to submit an application to the App Store from Xcode, "Submit to App Store..."
and I get this error message(s):
Unable to process the authenticateForTransportDiscovery request at this time due to a general error. (1240)
and
Unable to process validateMetadata request at this time due to a general error (1019)
is it a (another...) problem with Apple?
yeah same problem with me (using Application Loader). Here are my steps to resolve it.
- Sign out and close Application Loader
- Sign in and upload the build again. No need to re-archive app, just on
Keep trying until it works. No need to rebuild. Just reupload.
For me it worked on the second time
Few hours ago this happened to me while using application loader. Just hit previous and re- try the operation. Worked for me.
I had the same issue, I was using a VPN connection, I exited it and everything worked fine
I also tried switching WiFi (maybe previous one was on VPN) and it was able to go through.
Try with Application Loader it works fine.
I think this problem occurs because you have to agree the latest ios Program License Agreement.
You can do it here https://developer.apple.com/membercenter/

unable to process application info.plist validation due to a general error? [duplicate]

This question already has answers here:
Unable to process application info.plist validation at this time due to a general error (1095)
(10 answers)
Closed 9 years ago.
I know this question has been asked multiple times before and i looked into all answers.
I just want to confirm , anybody facing this issue today ?
Has someone submitted to app store today or yesterday without facing this issue . Just to make sure if others are facing this issue(seems to me due to apple servers).
This is clearly an Apple server issue, not an Xcode/iOS/OSX issue. Just wait patiently and Apple's servers will catch up to the traffic, or solve whatever issues they're having at their end.
If you're anxious, feel free to just sit there and restart Xcode until it works - but it's not restarting Xcode, only the time you waste that's solving the issue.
While you're waiting, run your apps in Instruments and solve some performance issues
Unable to process application info.plist validation at this time due to a general error (1095)

Provisioning profile status is Pending [closed]

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.

Error submitting app via XCode [closed]

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 :)

Resources