appcenter-cli: Release upload Failed

Looks like Microsoft is going to be re-enabling the disabled endpoints until Feb 1st, 2021 to help with the transition. They also mentioned that they’ll create documentation for these new endpoints for those unable to use appcenter-cli:

https://status.appcenter.ms/incidents/7930rkfgtg1y

To best assist the App Center team, I’ve created a mockup for them for https://openapi.appcenter.ms, which they may use freely:

Also, here’s a link to a bash script that someone concucted that implements the new API: https://gist.github.com/ouchadam/c74fa26c639a50d68bc35ee5749f868c

This is now reflected on the status page as a Major Outage for Distribute. https://status.appcenter.ms

Same here. Old REST API stopped working today and the recommended CLI replacement fails, so any CI automation is pretty much blocked 🤷‍♂️

@joakimkemeny lol. Well that sure is helpful 20 hours after the fact.

For us who don’t use the appcenter tool, what’s network commands to push a distribution?

POST here-and-there PATCH another-url-and-params

that would be awesome.

Help, @pcohensc?

Going on to AppCenter, the build in question appears to have been uploaded, but has not been distributed. So it looks like the upload is succeeding, but a subsequent step in the distribute process is failing.

I am sorry to reopen the thread, but Uploading to AppCenter is not working. I am getting The remote server returned an error: (429) Too Many Requests. Status page is all green

Posting this because our error is slightly different than the OP. We are seeing “502 - Bad Gateway” versus “504 - Gateway Time-out”

This is the full text of the failure we’re seeing after running the following CLI command:

appcenter distribute release --app xxx/xxx --file ./xxx.ipa --group “Collab” --token xxxxxxxxxxxxxxxxxxxxxxxxxxxx

The upload appears to succeed, but then fails after a long wait during “Checking the uploaded file…”. Using CLI version 2.7.3.

Release upload failed
| Aborting release upload...(node:20421) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'release_distinct_id' of undefined
    at ReleaseBinaryCommand.<anonymous> (/Users/xxx/.nvm/versions/node/v12.14.1/lib/node_modules/appcenter-cli/dist/commands/distribute/release.js:360:48)
    at Generator.throw (<anonymous>)
    at rejected (/Users/xxx/.nvm/versions/node/v12.14.1/lib/node_modules/appcenter-cli/dist/commands/distribute/release.js:12:65)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:94:5)
(node:20421) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:20421) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Release upload was aborted
Error: Loading release id failed with error: failed to get release id for upload id: a5f15b7d-1fee-4fe5-8edf-***************, error: {"succeeded":false,"errorCode":3,"errorMessage":"failed to get release id with HTTP status: 502 - Bad Gateway"}

Hello guys. I’m getting the same issue for several hours already. It happens like 1/3 of all uploads Cannot read property 'release_distinct_id' of undefined

@rpendleton Part of the confusion is the lack of consistency … for example: the status mentions Swagger API, but has not been consistent today. Ex: aforementioned 500, half way through today it moved to 410, and yet it still lists as available despite others which are officially deprecated are struck-out with mention of being deprecated. Fwiw , I know it’s not “you”, just posting as road-marker if others hitting similar confusion.

Sorry for the inconvenience, we will update the status page once the issue is resolved.

Have a look at https://status.appcenter.ms and you shall see they are experiencing problems

I’m experience this issue at the moment.

Release upload failed Error: Command 'distribute release -f Runner.ipa --group Testers --app <redacted>' failed with exception "undefined"

appcenter cli version 2.10.6

Here are the updated API steps: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#upload-new-release

Ok, if anyone is interested to using a simple mechanism to publish an asset to appcenter, instead of deploying nodejs (duhh) to all nodes, here’s a 1, 2, 3 steps to do it:

https://github.com/microsoft/appcenter/issues/2069#issuecomment-740654621

Microsoft: when you make a change that affects thousands, will you WRITE IT IN BIG LETTERS and well ahead of time, please? Thank you.

@donnib What node version are you running? This issue and this one indicate you need node 10.

Not running node 10 gives a ‘command xxx is invalid’ error it seems.

it’s appcenter distribute release --help

I just wanted to chip in for Azure DevOps users. Here’s what I am seeing in the App Center distribute task logs with system.debug enabled:

[debug]-- Getting release id.
[debug]---- url: https://api.appcenter.ms/v0.1/apps/FOO_BAR/BIZ_BUZZ/uploads/releases/SOME_ID
[debug]---- "{\"id\":\"SOME_ID\",\"upload_status\":\"uploadFinished\"}"
[debug]---- http call status code: 200

It will simply loop over these logs over and over for 15+ minutes.

Eventually, the task will succeed but the release will not appear in App Center.

Same for us. All CI is borked by this and we’re at a standstill. We need an urgent resolution.