tns appstore upload: Unable to connect to iTunes Connect (1268) - nativescript

Unable to upload .ipa file using NativeScript cmd
I'm running the following command:
tns appstore upload my-appstore-id my-appstore-pass --ipa /var/www/app.ipa
See the following error message:
Unable to connect to iTunes Connect
An error occurred while processing the json request. (1268)
no other messages or logs are provided.
Have no idea where to search for solution.

This was a known issue on the nativescript end. https://github.com/NativeScript/nativescript-cli/issues/2874
I had ran into this a few weeks ago and after upgrading to nativescript#next the issue went away.
To answer #BrianDilley you need to supply your itunes password, it's not app specific.

Related

Trying to log in on parse server gives "internal server error"

My iOS app has suddenly started giving this error message when logging in or creating a new user in the app:
[Error]: {"code":1,"message":"Internal server error."} (Code: 1, Version: 1.15.4)
Here is the pickle. The app works fine on an earlier version (version 4.4.0) that I have on my iPad. Here I can log in and create a user, and I can add items and delete items while in sync with the server. In the new version of the app (4.4.1) nothing has changed with regards to the code on my login page. I can still fetch data from the server in the app as well, but logging in and creating a user gives the internal server error.
I got my server on Heroku and the database on MongoDB. The database is available and running. However, the server Heroku got several failed throughputs (5xx code) during a day. This says to me that something is going on with the server side of things.
Does anyone know where to turn to next? I can't seem to get my head around where the issue is rising from. I have already sent a mail to Heroku, so I'll make an update when I receive an answer.
But basically, I need help to know what would be my next step to figure out what is causing the error?

Unable to deploy business network using local Composer Playground

I am unable to deploy the business network using the local playground. It hangs at "Please Wait: Installing Business Network"...and the browser console log shows the following error -
WebSocket is already in CLOSING or CLOSED state.
I am able to deploy the network using CLI.
I am at 0.13.0 version.
Please advise.
Thanks,
Naveen

parse.com: parse deploy not working

I have running project on parse.
Suddenly it stops deploying files on server.
When I run parse deploy command then it throws error as
Unable to authenticate app. Please make sure your applicationId and masterKey in "config/global.json" is correct
I have tried to do same with new account from my desktop but same error.
I am using windows 7 and Js Sdk v2.1.0(parse).
Please help to get sort out this issue.
I done with google no resolution found.

Could not create a bot on Server 4.0.3

I try to create a Bot for mac Server 4.0.3 on OS X 10.10.2. I update checkout repository with existing SSH key, but always get the same error : "Bot creation failed with error: Internal Error Creating Bot".
Could anyone help how to resolve this issue or give any explanation why it happened?
I had the same issue but I was not able to solve the root cause.
The only workaround I have found was to create the bot directly on the CI server.
The issue I think is due to something related to the certificates but I was not able to find out what.
HTH

Failure instantiating web-service client on xcode app upload

I'm using XCode 4.0.2 to upload my iPhone app to the iTunes app store but get the following error messages:
Failure instantiating web-service client
An exception has occurred: Unable to open url: https://contentdelivery.itunes.apple.com/WebObjects/MZLabelService.woa/ws/MZITunesProducerService?wsdl
Could not connect to Apple's web service
Unable to authenticate the package: 450416349.itmsp
I've got the latest Java version (1.6) and have double checked the network settings in the Java preferences.
Any ideas?
Got to the bottom of it. Running a TCP dump on our firewall discovered that some (but not all) of the requests that XCode made were using the configured proxy, and others were not.
We allowed the proxy to be bypassed completely to test and it all worked fine.
Have you tried using Application Loader? Try that and see if it works. Hope this helps.

Resources