Publishing 1.3.0 to Web App hangs after logging in

Describe the bug

I’m trying to publish as an Azure web app. I created just a basic echo bot template. I then started the process to add a new publish profile and select the web app option. It asked me to login to Azure which I did successfully. It then hung on the “Configure resources” page. It says “Loading” with the spinning wheel but nothing ever actually loads.

Version

1.3.0

Browser

Not really meaningful for this point since I’m just trying to publish.

• Electron distribution
• Chrome
• Safari
• Firefox
• Edge

OS

• macOS
• Windows
• Ubuntu

To Reproduce

Steps to reproduce the behavior:

Create a new publish profile Give it a name and select the publish to Azure Web App option Login It hangs on the next screen trying to load resources

I belong to a lot of different directories so is it possible it’s related to that?

Expected behavior

I expect it to show the create resources UI as documented in the publish documentation: https://docs.microsoft.com/en-us/composer/how-to-publish-bot

Screenshots

It’s stuck on the below screen:

Additional context

I have previously been using 1.2.1 and was able to use the provision script there to publish bots. I was also able to publish bots to the provisioned resources from Composer for older versions. I tried opening one of those bots with 1.3.0 and publishing and I receive an error message saying, “Error - Required field accessToken is missing from publishing profile.”. The accessToken field is definitely in there, though, in the same place it was in 1.2.1. I ran an “az account get-access-token” and pasted the new token in to make sure it had a valid one.

That may be a separate issue with 1.2.1 publish profiles not working with 1.3.0, though. Which isn’t as big of a deal right now since I could ideally create a new profile if needed. The interesting thing, though, is that 1.2.1 bots can be published but it runs into an issue with 1.3.0. So, my Azure account is setup with everything it needs to publish bots and it just seems to be an issue with the UI retrieving Azure information for some reason.

[tonyanziano]

Note to fixer:

1. Check accountType property on received account object after sign-in
2. If accountType is non-federated, use acquireTokenInteractively instead of acquireTokenSilently a. I think we might already do this, but we need to look for it in the catch block instead of checking the result for result.error

[bdezeeuw]

Yes, I’m able to work on v1.2.1 currently. I’m looking forward to using some of the new features once they figure out the issue.

Thanks for the help, @luhan2017!