I had already published a working bot to Azure. However I had to update it and I am now trying to publish it again to the same resource group in which it already exists. As expected, my access token had expired, so I generated a new one, pasted it on the bot's profile (after clicking on "Edit") and tried to publish the bot again.
I tried following this documentation: https://docs.microsoft.com/en-us/composer/how-to-publish-bot
I also tried using the JSON structure that appears on the "README" of the bot files, and tried just modifying the values of the previous JSON that I used when I first uploaded this file. But I keep getting the same error 400.
I made sure to use a valid access token on each attempt.
Any help would be greatly appreciated.
I'm using the Composer v1.1.1
Steps to reproduce the behavior:
I expected the bot to be published normally, as it had worked before, with the new updates.

This is the JSON that I followed from the Readmefile

And this is the one that I used following the structure in the "Edit" of the profile:

It should be fixed in main per @lei9444 , @luhan2017 will help verify this
@juanpmendoza , I suspect the az cli subscription does not match with your subscription in publish profile, could you please double check? could you try to run this command "az account show", it will show your current subscription info and check whether the services you used in the publish profile belongs to this subscription.
@luhan2017 I checked and you're right! I should set the right one using "az account set" right? Which Json schema should I use to edit the bot? Thanks!
@luhan2017 I used az login and then the JSON from the Readme file and it worked! Thanks for the help!
Awesome, thanks for reporting back that @luhan2017's solution worked. I'm closing this issue as it sounds like it has been resolved, if there are any questions related to this please reply here and @mention a team member or open a new issue.
@luhan2017 I tried with Json in the Readme file. But still, I'm facing the same error.