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.
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.
Problematic Workflow:
Start Xcode,
New ->Project,
Pick Single View Application ->next,
Enter app name etc ->next,
"Choose Options for your project:" page opens which does not let me
do anything.
It just stalls there. There is "Add to" combo box in this page which is not responsive. SinceI can`t do any changes on this page I cannot click on "next" either, i.e., it is disabled.I can click on "previous" which turns back to project name etc page.
This started to happen all of a sudden yesterday. There is no crash or anything, just unresponsive screen. But I cannot do any development at all since I cannot create a project in the first place.
Finally the problem was solved. Steps were below:
1 - Update the system to Yosemite,
2 - Completely clean the system off of the Xcode (I did it using AppCleaner, freely available on the internet),
3 - Make sure no trace of Xcode exist in the system,
4 - Go to App Store and install Xcode from scratch.
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
We are seeing a strange behavior in our iOS part of the App:
We are using a Jenkins Build Server with an XCode plugin to compile the app on the command line
At first we had an SVN ignore on the iPhone "native" folder in our SVN. So all was taken from common and the whole native project was generated by the worklight Ant scripts on the Jenkins server. This was then compiled by the xcode on jenkins and the App worked fine with Direct Update - the Dialog had a "UPDATE" and a "EXIT" button, both buttons worked as intended.
Then we added a CustomWebView to our project and had to include the native folder into the SVN. We tried to SVN.ignore all generated files and the build processes in Worklight Studio and on the Jenkins xcode server work both fine.
We did not change any of the generated code except we added two classes:
WebViewOverlayPlugin.h
WebViewOverlayPlugin.m
and added the plugin to the config.xml:
<plugin name="WebViewOverlayPlugin" value="WebViewOverlayPlugin"/>
BUT:
when we compile the same SVN code in the Worklight Studio, we have an iPhone app that has a Direct Update dialog with only the "UPDATE" button across the whole dialog. There is no "EXIT" button anymore at all.
when we compile the same SVN on the Jenkins Xcode server, we have an iPhone app that has a Direct Update dialog with an "UPDATE" and an "EXIT" button but the "EXIT" button does not work as intended - when pressing it, the app stays open and the dialog closes, so the user can continue to use the old version of the app without updating. The "UPDATE" button works and updates the App.
So my question is, what build setting, generated files or configuration etc. could have any influence on the behavior of the Direct Update dialog. Since we use the exact same SVN source it has to have something to do with something generated, or with some configuration.
Is anything around such a strange behavior known?
Is it known that one can "configure" the Direct Update dialog to have only an "UPDATE" button with no "EXIT"?
Thank you all for any help or hint where we could look to further investigate.
You didn't mention your Worklight version, but starting with Worklight 5.0.6.x:
The Direct Update dialog will feature only 1 button - Update. The Exit button was removed.
This was done in order to be inline with Apple's App Store submission guidelines.
And more in general, the WL.App.close API method was rendered "non functional", because as per Apple's guidelines, it is the user that should be given the control on exiting the application and not the application to do so. Think of it as an "OK" button instead of "Exit".
That said, you are not supposed to see an Exit button to begin with. But again, I do not know what is your Worklight version and what exactly is your build setup to understand what is going on there that does this sort of mixing.
You are not supposed to be able to "configure" anything in Direct Update. It is non-configurable in this respect.
As for why you have 2 buttons when building with Worklight Studio, but 1 button after adding the WebOverlayPlugin, it is interesting. Is there a chance the app is of a lower Worklight version and you are now building it with a newer version of Worklight, containing the changes made, as described above?