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.
Related
This could be related to the problem here, but since this is happening in my iOS build (not Android), and I have cleaned the project and restarted Appcelerator, I don't know why this would occur.
Note - I did not change my dev environment, update appcelerator, or change any certs on my MBA where I'm developing my app. The only thing that I've changed is app code. I thought that I might see bugs or errors, but I'm not trying to debut either, as I'm building and installing via iTunes sync to my ipod Touch w/9.2. The build process and settings have not changed, so I don't even know where to start.
Work around more than an answer, but for some reason, my device, registered at apple was not being recognized by appcelerator (see note in my comment for related issue). After logging into apple dev center, and going back to appcelerator, the issue appeared to go away. I don't know if this is solved, but the workaround got me in business again.
I am getting a warning icon while trying to submit the app to App Store. I am using XCode 6.4 to submit the app directly to the app store from Organizer itself, I usually do like that only.
On clicking the warning icon, I am unable to see any reasons described. I tried with all the browsers for this.
I saw the below links also where they talk about beta-reports-active = 1 entitlement and I have made sure that it is present and also I am not using watch kit. Below is the snapshot of entitlements
Build warning
Build upload warning
So not sure what is the issue, the only thing that I did recently is that, since our certificate was expiring soon, I did a reset of the certificate using Xcode 7 (since it was easy to do it with Xcode 7). This ended up in having a profile automatically created by Xcode, now when I archive and try to submit, Xcode is picking this XC: profile.
Just wanted to know, if it is okay to submit even with this warning. Need to push a patch fix soon. Thanks in advance for the help.
After a couple of refresh of the screen the Warning went off, then in the next refresh, warning came back.Also I started seeing radio button names eg:"Manually release this version" as ITC.Manuall...... just crazy!!
Looked like something weird with the iTunes Connect site. In the next refresh where I got with no warning, I went ahead and submitted uh!!!...I couldn't run around with no clue :)
UPDATE: THE APP GOT APPROVED...HOOF!!!
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
My application got stuck on installation due to wrong configuration on my iPhone with iOS 7. Provisioning profiles, certificates, devices everything seems ok.
I found an example of how to prepare a web page to provide a download link for your iOS application. I completed the necessary steps with one small mistake. The mistake was my appName.ipa and appName.plist was different.
As a result, the link was look like working but was installing 2 apps because of this difference. Real app finished installing but other clone that comes from the wrong .plis file never finished installing.
I'm able to install/remove application but this second clone cannot be removed even there is an (X) symbol in edit mode. When I press the (X) symbol for deleting it shows the Alert View but not deleting the clone even I press Delete or Cancel.
I tried to delete it but couldn't find a way. I currently don't have any issues installing/removing my application but it just stuck there. Is there anyone has the same problem before or any ideas?
Did you try with iPhone Configuration utility (Win) / iPhone Configuration Utility (Mac) ?
I realised the problem, it's about the Bundle Identifier difference. I created a new app with the ghost icon's bundle identifier and run it from XCode, so XCode overrode it and successfully installed the test app.
We've built an MDM server using a mac mini.
We have 2 applications to push out to a number of users. One app will push and download on the remote devices with out a problem. The other displays an error "The app could not be installed at this time"
This second application is an older application.. however we are building it for 6.0. In the console we see this.
ipad SpringBoard[65] <Warning>: could not save thumbnail for downloading icon: image=(null) path='/var/mobile/Library/SpringBoard/DownloadingIconImageCache/
This app can be built an installed when a device is connected to the build computer. We have all of the signing the same as the first application. We can also archive the app without any errors. What would cause this app to not install, or what should we start with?
Several notes/ideas:
a) Take a look at this (they mention the same problem)
Trouble installing AD-HOC distribution through safari
iOs application crash on install
Ad-hoc distribution fail
http://community.phonegap.com/nitobi/topics/not_installing_my_application_in_ipod
b) Can you please post your manifest (if you are installing inhouse apps)?
Please double check that that if you pointing to icons in this manifest, the links are correct.
Ok this took days to figure this out... In my situation at some point another icon was added into the build settings. We did change the name of the bundle so I'm assuming that xcode automatically populates the icon information?
In the info tab check to make sure you only have one property for 'icon files' (to be clear you should have the ability to open the drop down menu and expose sub menus... What I had was 2 'icon file' sections.) After I deleted the second set of icon files it pushed fine.
Hope that helps others figure out a very frustrating situation