I am getting the following error when trying to upload a new APK file to my distribution group. I don't understand what "changing distribution group is not supported" meant.
appcenter distribute release -f C:\Source\myapp.apk -g XXXXXXXXX -r "First Test App Release" -a
Error: changing distribution group is not supported
@xplatform Can you please share the exact command you are running? You can hide the token, the rest is not a secret.
Also you can run it with --debug it might give you some hints as for why it happens. The error 'Error: changing distribution group is not supported' is obviously misleading and doesn't represent the root cause for that error.
Hey @xplatform Gary, we haven't heard back from you in some time, and I'll be closing this ticket for now. Please reach back again if you have questions anytime, and we'll reopen this ticket again.
Thank you for your support!
Amanda
For people from future: encountered this error today. My cause was specifying a non-existent distribution group name.
@jokester thanks for letting us know - and that happens :) Did you manage to get it working now?
hi Amanda, mine worked wo problem. just thought the cause might be helpful
to others :)
On Wed, May 23, 2018 at 1:51 Amanda Chew notifications@github.com wrote:
@jokester https://github.com/jokester thanks for letting us know - and
that happens :) Did you manage to get it working now?—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/appcenter-cli/issues/413#issuecomment-391062659,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAw9UkTDt2qE6xq7g-ZhCM1cxOU9eO8Rks5t1EIbgaJpZM4S31Hv
.
@jokester - cool! It sounded like it was working but just checking. And yes, note to all: use the right distribution group name. You can find a list of distribution group names of your app by running the command ‘appcenter distribute groups list’
Hi, I experienced the same issue as the original poster. In my case the command was something like this (sensitive data masked out):
/usr/local/bin/appcenter distribute release --group Collaborators --release-notes-file CHANGELOGS/CHANGELOG_2018.44.10.md --file AppName.iOS.ipa --app atzimler/AppName --token xxxtokenxxx
I was not manually executing the command, but through an automated build process, so I know it should work. For about 10 minutes, the build process was regularly failing on the upload, but then went back to working. It seems that this might be on the server side. Lately, I'm experiencing a huge amount of HTTP 504 GAETWAY_TIMEOUT messages from the server.
Hey @atzimler thanks for contributing to the community!
App Center Distribute was experiencing a temporary delay in our distribution services including uploads and distributing stores at around Nov 1, 20:12 UTC today - about the time you posted this comment. It was resolved at 20:45 UTC, and our systems are operational now. You can see the status of App Center here.
Thank you for bearing with us!
May be we should add a documentation which say that spaces in group name are replaced with "-" for example our distribution group was "TestApp Dev" and it was displayed in the same way on app center. However when i ran the command appcenter distribute groups list i got to know all the group names come back without any spaces like TestApp-Dev. Hope this helps someone in future.
Also:
Updating release details...Response status code: 400
Body: {"code":"bad_request","message":"Error: The release notes exceeds the limit of 5000 characters."}
Error: changing distribution group is not supported
I started getting this error message today, turns out the issue was that I had not included release notes
I get this error when distributing an iOS app to an existing group it's associated with but noticed I have spaces in its name which I use quotes when specifying. Weirdly enough the Android version of the app distributing to a similarly named group doesn't fail :(
just noticed in my case when adding the --debug flag to identify any errors I do have a completely unrelated issue which seems fixable but the error message you get doesn't provide you the correct insights:
{"code":"two_factor_authentication_error","message":"Error in fetching the Apple service connection details for managing devices. apple connection is not valid for connectionId: 39bed04f-bce6-4128-bb85-9ccf00c23cdf"}
In my case the reason for this error was that I was using the wrong file extension when uploading.
##[error]{"code":"bad_request","message":"Error: The release notes exceeds the limit of 5000 characters."}
In my case it was the confirm merge/squash message. For some reason Github generate all. my commit messages although I tried to squash it.
Anyway, Just replace the long merge message with something shorter than 5000 characters. Maybe just your Jira tickets links etc..
Error: failed to create release upload for apk
Can someone help me with the above error ?
Appreciate your help
@praveen6577
had the same issue today. try running:
npm i -g appcenter-cli
updated the npm binary and it fixed
ps. I also had to add Set-ExecutionPolicy RemoteSigned on powershell. it seems the tool uses a .ps1 file now
@praveen6577
had the same issue today. try running:
npm i -g appcenter-cli
updated the npm binary and it fixed
ps. I also had to add Set-ExecutionPolicy RemoteSigned on powershell. it seems the tool uses a .ps1 file now
Thanks Much for your reply
will try the same
Most helpful comment
I started getting this error message today, turns out the issue was that I had not included release notes