I am clicking on my project, then clicking export.After clicking export i choose blackberry -> release build.
After this step i click next again, until i reach last step. I select enable digital signing and click on finish.
It starts exporting release build , but i get an error Error: Server cannot handle your request at the moment, please try again later.
(Time of error: 18 August 2014 13:37:29 EES
what is this problem?
Signing server is down at the moment, just wait for some time
https://supportforums.blackberry.com/t5/Native-Development/Signing-Server-down-again/m-p/2960188#M66552
Yeah, I have checked :
- IP : not wrong
- Password : not wrong
- All Setting already right
But i just got that error..
Having go through BB Forum + This(StackOverflow) -> all people got this problem
Related
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.
I have successfully built and uploaded a new version of an app with Xcode 7.3.1 in OS X 10.11.5, but the build is not showing in iTunes Connect.
After the build process (launched through the "product->archive" menu) the Organizer opens.
There, I choose the build and click on "Upload to App Store..."
So far, everything works as expected.
After the upload, when I refresh the iTunes Connect web page (under the "Activity" tab), I briefly see the new build showing in the list.
If I refresh the page again, some seconds later, the build has disappeared. I can no longer find it anywhere in the iTunes Connect site.
When I try to repeat the process, XCode gives the following error message:
ERROR ITMS-4238: "Redundant Binary Upload. There already exists a
binary upload with build version '2.4' for train '1.5'" at
SoftwareAssets/PreReleaseSoftwareAsset
so I have to increase the version number to complete another upload.
I went through this process 3 times, the last one using Application Loader instead of XCode, but the same thing happened all the times.
Does anyone know why this is happening?
What could I do to troubleshoot this problem?
What other informations may be useful to further investigate?
UPDATE
More than 48 hours have passed since the first upload, still no signs of any builds in iTunes Connect.
The only thing I can tell you is that it's probably a matter of time. I faced the same issue weeks ago, and between 24 and 48 hours after submitting, my build was finally showing in iTunes Connect.
It's a shame for Apple to make developers wait without informations... But this kind of issue had been reported a lot.
It turned out to be a wrong icon included in the asset catalog.
After 5 days of troubleshooting and ping pong with the Apple support, I was finally pointed in the right direction. All I had to do was replacing an image that was the wrong size.
Done that, all worked as expected.
I was having problem with uploading a build of my app but I was successful uploading a build (0.0.7) of version (1.0.0) while the build (0.0.6) was still processing
But when I am trying to add internal testers to test this build, the uploaded version is not showing up instead it shows the version which is still in processing.
Does it have something to do with iTunes or I am doing something wrong?
A guy from Apple contacted me after 12 hours with this e-mail
"Thank you for providing that information. In reviewing the information and screenshots you provided, I can see that you have a build that is stuck in processing and you were able to upload subsequent builds successfully, however you are unable to test the new builds.
We’ve had some reports of this issue and it should now be resolved. In order to continue testing, you will need to submit a new build with a new version. Once you submit a new build with a new version, you will have the new builds available to select from when choosing a build to test."
So, I think uploading a new build with a new version will hopefully work
I was able to resolve the issue by logging into iTunes Connect and removing myself as an internal tester (which removed the app from my TestFlight App) and then accepting the invitation again.
Try this :
1) Launch Application Loader.
2) In the top menu bar, click Application Loader > Preferences.
3) Choose Advanced.
4) Under Transfer Protocol, deselect Aspera.
5) Close the Preferences window and proceed with the delivery.
I am also facing the same issue and i change the version of my app in Xcode and then it will be shown in the internal testing. Please just change the version of your app then it will show. Just change the version to 1.0.1 or 1.1 whatever you want. Hope this will help you.
Thanks
Regards
Mandeep Singh
I just move to upload my first app.I am using xcode 7,swift app.while validating i got any message like this:
I also google it about this problem.In this stack over flow also I saw some solution that its just a warning.but when I move to iTunes to wait for that + button to build my app and to submit. I am not able to see that + button in iTunes.
I also delete my archive and re-archives and wait for one hour.till now I din see that + button to add my build
Now what shall I do.Kindl give some soilution
Thanks in advance !
Updated:
here after validate one +button will shows to add.That only i din get
See the steps you followed or not :
first of all create a new ios app and fill all details.Then move on to the steps:
1. archive your app
2. validate it
3. submit to app store
4. then only you will see that + ( build) button over there.
If you already done these steps.Then also you not get means try to change build number or version and re do all steps.sure this will work.
Hope this help !
This error won't affect your ability to upload the app to iTunes Connect.
Once you have opened iTunes Connect - go to My Apps -> Plus Icon -> New App. The just follow the steps and you should be good.
Recently (as of around Nov 1), whenever I update a TriggerIO module to the most recent version (as prompted by a "your modules are out of date" message on the TriggerIO Toolkit), it tries to "download instructions to build the app" but then always fails after about 5 seconds with this message:
"Failed to download instructions to build and run your app, contact us if this error persists."
Thus preventing me from running the app or doing anything..
This did not used to be a problem..
UPDATE: it just started working again - I clicked the "Shutdown Toolkit" button on Trigger Toolkit and then it seemed to work? Closing the browser window earlier didn't seem to fix it but maybe clicking that button does? Or it was just coincidence..
The "Shutdown Toolkit" button on the top right of the header (NOT just closing the browser) and then restarting the toolkit seems to be a fix.