When accessing Crashlytics via the "Beta" webclip I can sometimes see the list of builds, but when I cannot, or if I do see them, and tap on a build, I see a message at the bottom of the screen stating
Server Error
Something went wrong. Please try again.
[OK]
I did check the Profile for crashlytics, and found the signing certificate for *.crashlytics.com had expired on April 7th 2017.
I removed the profile, rebooted my device, and reinstalled the profile via accessing the check me out option in one of the builds. I checked the expiry date for *.crashlytics.com and it was newer (April 6th 2020)
For the first attempt afterwards, I was able to install a build, but occasionally on subsequent attempts I saw the aforementioned server error, or the screen indicating the device is not set up for beta testing.
Can someone explain exactly what is happening and how to properly resolve this, as it is impacting the ability to complete work due to being unable to install builds reliably. Having to remove and reinstall the profile - which works for a while - isn't an acceptable method to resolve things.
You're missing a final step.
You need to install the Certificate manually, it would be waiting for you to install it once you get into the Settings native App.
1. After this, go to Home > Settings (no need to close the Safari web)
2. Then install the certificate on Settings / Check top.
3. Go back to the browser and install the App.
If you are having trouble with this error on iPad, check that you are viewing the mobile website (tap the AA button in the search bar and then Request Mobile Website).
Each subsequent page load may revert back to desktop, so check that setting each time it fails.
Unless I enable debugging (Esc > Cmd+D > Debug JS Remotely) then I see this error:
Module AppRegistry is not a registered callable module
This also means that I'm unable to view the bundled app on device. If I try to view the app on device, but still use the dev server (remembering to use an IP address in AppDelegate.m instead of localhost) then I instead get this error:
WebSocket connection failed with error Error Domain=NSPOSIXErrorDomain Code=61 "Connection refused"
even though I've verified that I can open the dev server URL in a browser on the device.
I'm not an iOS developer, so maybe this is really obvious, but how do I go about debugging why these errors are happening, or just not having these errors in the first place?
One reason could be App Transport Security that was added in iOS 9. Please see https://facebook.github.io/react-native/docs/running-on-device-ios.html#app-transport-security for reference. You have to add the NSAllowsArbitraryLoads entry to your Info.plist yourself if you didn't use the React Native CLI to generate your project.
Although this doesn't really answer the 'How do I debug these kinds of generic errors' question, I've found out that in my case the problem was that I created my app using an older version of RN (maybe 0.26?) that had a bug in the scaffolding code it creates (which I stupidly ignored at the time when I found i could work around it by enabling debugging) and updating to newer versions of the app hasn't fixed the issue because that doesn't cause the scaffolding to be updated. By creating a fresh app under RN 0.29, and copying my code into it, everything is now working as expected.
It seems that most of Appcelerator's subdomains are having SSL issues, causing an issue in Titanium's iOS build process.
Does anyone also have this issue?
If so, is there a workaround to get the build process working.
I tried cleaning the project, explicitly trusting their invalid certificate, and disconnecting from the internet during build (produced different results but still failed).
Ex. https://security.appcelerator.com
https://www.ssllabs.com/ssltest/analyze.html?d=security.appcelerator.com
you are not alone, I am also seeing it and so are others...I also do nto think there is a workaround at this point
Appcelerator's response:
https://twitter.com/appcelerator/status/735908332054151170
I regenerate all of the certificates, update the version number of the application, but the problem persists.
Follow the below steps.
Go to My Apps Page.
Remove the Build. Then Save It.
Re Add your Build. then Save It.
Now try to Submit It must work.
I do not know what the reasons are, how to do?Thanks!
In Prerelease section the status of your build should not be "Processing". Just wait some time (10-20 min) after build upload, and it will be ready to use.
I got this problem in Chrome browser. Switching to Safari worked like a charm for me.
I had the same issue. To solve it, the unique thing I had to do was "Clear History and Website Data..." within Safari (version 8.0.3 in my case).
Please, keep in mind that I speak from my experience and that worked for me. I cannot guarantee this as a general rule to fix the problem. Nevertheless I can assure that I tried several alternatives explained here and the one I just described was the solution for me.
It seems to happen if you are too quick between the build finishing "processing" and it being attached to a version and the version being submitted. I just published two apps in quick succession and the second submission had this problem while the first was fine. The only difference - speed of clicking the submit button.
Logging out and back in made no difference - the "problem" is with the submission.
I removed the just uploaded build from the version and then re-attached it, proceeding as normal to submit the release to Apple with exactly the same build and submission artifacts as before, except this one "saved" and went into the review queue.
I got the strange but working solution.
I had tried submitting the app using Safari browser but it didn't work and showed same error. Submitting the App using Chrome worked for me in the first go...
I'm stuck on this too; and have had to work around several other iTunes Connect bugs just to get to this point. What were Apple thinking by releasing this iTunes Connect version? It's completely ridden with bugs!
Sorry, I've tried everything I can: Filing a support case with Apple appears to be the only 'solution' at this point.
Make sure the Version you have on iTunes Connect and the version you gave in the Info settings in xCode are exactly the same.
I had 1.0.0 in iTunes Connect and 1.0 in xCode and it kept giving me this error message. I changed it to 1.0.0 in xCode and it worked perfectly.
I had the same problem. just sign out and sign in again. it should work.
I had the following issue when submitting a build which was uploaded couple of days ago for test flight testing. Then figured out that the provisioning profile of the application has expired so I renewed the prov profile and downloaded and re-archived the application (by increasing only the build number ) and uploaded and submitted it. And it worked like a charm.
I guess apple need to be specific of these error scenarios
In my case we contacted apple and they said the issue is that it seems that we don’t have a correct certificate generated on developer.apple.com. We use Xcode automatic signing management. I refreshed correct profiles, rebuilt and I could submit successfully.
I had the same problem. Tried from different system and it got saved
I'm trying to upload an iOS app for review using Xcode's Organizer and I've encountered two problems:
Case 1
Binary uploads but when I press Submit for Review iTunes Connect gives the error:
Your app information could not be saved. Try again. If the problem
persists, contact us.
Case 2
After getting the first error message, I tried uploading a new binary, but got the following error message in Organizer:
ERROR ITMS-9000: "Redundant Binary Upload. There already exists a
binary upload with build version '1.1' for train '1.1'"
I tried uploading other binaries changing the version number but still I can't get my app to go in the review state. I also can't see any way to delete old binaries that were uploaded.
Another observation: My app should be around 30MB but when I look at the uploaded binary it is only 1.46MB. I guess there might be something wrong from the binary but I've built it using the same technique several times before and never had any issues.
Any ideas?
For me, I was filling out the form in Safari and getting the error. I logged out, then switched to Chrome and signed in. This fixed the error, and I was able to submit.
Sign out and Sign In again should work as it worked for me!
I solved this by increasing the number in Build (Select the Target, then Xcode -> General -> Build, see picture) by adding .1 so the build was 3.75 -> 3.75.1.
But only for the Build, the Version is still 3.75 and also appears like that in iTunesConnect.
Then the new binary uploaded and I could select it for review. In the picture below you may see the old and the new binary listed in iTunesConnect. Then I finally just had to select the new binary and submit for review.
Open web inspector, you will find that Apple said: We've got a server error ... 500
That's the real reason. :)
Update:
Inspired by #phantom, I try to use dotjs to run a javascript script to auto click submit button per 15 seconds, but still get the 500 error all the time.
#Geaka's answer is working for me. Because my product name is Chinese，I change my product name to english(DO NOT include whitespace! It maybe causes another error on building path error.)
I debug the apple website and find a js script named submit_for_review_cntrl.js which controls the whole submit progress. From line 123 to line 129(formatted by {} button in chrome) that setting the http headers, there is a field named X-Original-Filename, the value is given by $scope.addCcatFileToJson method in line 138, the param of this method is given by ajax callback, i guess there's a bug for encoding the product name field of the back-end code.
WTF Apple!
We just solved our version of the problem (generic error message)...
After hitting submit for review I was trying to upload a file for the ERN since my app uses encryption. It finally worked when I used a zip file that contains an image of the ERN response and a txt file describing what encryption is being used.
The problem unfortunately still occurs. My solution when this happens is removing the binary, clicking on the save button then adding the binary again. Then save and follow the standart procedure. That solves the problem for me without changing the build version or doing anything extra.
Finally find the solution:
Steps:
If your app version and build version is 1.0, keep version 1.0 and change build version as 1.1(bigger than last build version), then upload it.
If your app name is English, choose this build and submit to review, it would be change to review.
If your app name is not English, Chinese for example, you need to name it in Bundle display name,
Do not name it in TARGETS directly.
Maybe is also works for Japanese and Korean.
I solved this by switching over to Chrome instead of using Safari. Presto, worked right away!
I have met this problem this morning and have solved it. I change my product name from Chinese to English, and write the Chinese name in the Bundle display name, which solve this problem.
You can change the Bundle display name in the info.plist, and change the product name in the General tab in the project.
that's an erratic error. Probably some apple infrastructure problems You may have done something and then it worked - switching your browser, increasing build numbers and the like. But you could've hit several times submit as well. At least, after a while, my submission has been successful.
I opened the iTunes connect on my iPhone , and was able to submit sucessfully via iOS safari. I don't know why.
You will need to change the Build version. Create 1.2 build for version 1.1 of your app. Then upload your binary. After few minutes (on processing) you'll find new build to submit for rewiew.
I spent 2 hours !!!
Finally, i found the solutions. The main culprits is your PRODUCT NAME, it must be in English!
Go to build setting --> packaging --> change your product name into English
Change your "BUndle Display Name" to your desire localized name
Increase your build version and re-upload
This time you're fine!!!
I was plagued with these errors over and over when adding new screenshots.
Nothing seemed to help.
Then I visited iTunes connect in Safari (I normally use Chrome) and somehow all errors went away.
Maybe related to a Chrome browser extension like AdBlock?
TLDR; use Safari for iTunes Connect
I experienced this submitting an update today to my app. For about 30 minutes I retried and received the same error. I tried, removing the binary, signing out, I also rebuilt the binary with an incremented "Bundle Version String".
None of these steps made any difference, but I continued to retry, continued to get the same error, and eventually it accepted the submission.
I don't believe any of these solutions I tried made any difference. I believe there was some internal error on itunesconnect. As the message suggests, I think all you should do is try again later...
I only need to clear all my cookies, instead of switching browser.
Switch the browser you are using & then remove the build, save that once & then again add the build to it & then again save it. After that click on submit for review & it will work perfectly.
After 3 day, Itunes accept my first binary. I have tried to change my Bundle Display Name to English then tried to change to keep version 1.0 and change build versiyon to 1.2. Tried a lot of think and after 3 days surprise!!! Apple accept
I also got this error. Solution I found was to change contents in "Name" section of app description in iTunes Connect.
There was no need to change app name to English language (as some suggest), I just removed ":" character from app name - and then I could submit it to review! My localized versions of application still contained non-English names.
Had the same problem since my application name contains ":". The iTunes connect server returns 500 error because of it. I've just temporary removed ":" from English app title, submitted app and returned ":" back.
I think it ended up being a combination of several factors, but one thing that was definitely wrong was that I hadn't clicked the box about posting info to the Korean store. This was off by default and needed to be clicked. After doing this and several version changes (ended up submitting 1.2 instead of 1.0!) my app finally went into "waiting for review...".
Tried all possible solutions Chrome and Safari; none of them worked.
Then I switched to Firefox and magically it went through.
I found the simple solution. Just go to detail of the version, remove the current build then save.
Then click on the blue add button and add the current build again, save again. Then submit again.
It work for my case. Hope it helps
Log out from the iTunes from the current browser. and Login to iTunes from the another browser and try to submit the app.
Hope it works!
And Make sure that there should not be the Redundant binary (in other words the build number of the binary should not same).
I've just had the same problem.
Switching browsers to Chrome fixed it for me straight away, so will try clearing out Safari, and re-booting in order to get back to submitting with Safari.
#rayg - and for the sake of others - the Korean checkbox doesn't have to be checked in order to succeed in getting the app up for review. Maybe under certain circumstance it does have to be selected, so I'm not saying your solution to your scenario is wrong, but the post gave the impression that it's a requirement for every submitted app, which it isn't.
I have tried above all recommended solutions but none of them worked for me .
Then I select build version from my mac system and logged itunes connect using firefox from window system and it worked for me.
Or you can try itunes connect login from another Window/Mac system.