BotFramework-Composer: App create failed when publishing from composer desktop 2.0 with new resources

Describe the bug

The customer is publishing bot with LUIS from Composer desktop 2.0 with the option “Create new resources”. The publish fails with the below error, which I describe in the repro steps.

Version

Browser

Electron distribution

To Reproduce

Steps to reproduce the behavior:

Customer signs into composer
Creates a new publishing profile
Chooses the tenant with multi factor auth enabled
Tries to publish and gets the below error

This error has been anonymized and formatted for readability. See the linked incident for the original error.

{
    "name": "CREATE_APP_REGISTRATION",
    "message": "App create failed! Please file an issue on Github.",
    "stack": "Error
        at new CustomizeError (C:\\Users\\John Doe\\AppData\\Local\\Programs\\Bot Framework Composer\\resources\\John.Doe.App\\extensions\\azurePublish\\dist\\extension.js:255547:25)
        at createCustomizeError2 (C:\\Users\\John Doe\\AppData\\Local\\Programs\\Bot Framework Composer\\resources\\John.Doe.App\\extensions\\azurePublish\\dist\\extension.js:255552:10)
        at BotProjectProvision.createApp (C:\\Users\\John Doe\\AppData\\Local\\Programs\\Bot Framework Composer\\resources\\John.Doe.App\\extensions\\azurePublish\\dist\\extension.js:256989:17)"
}

Expected behavior

LUIS Resource should be published successfully.

Additional context

For more information, please refer to this incident (authentication required).

About this issue

Original URL
State: open
Created 3 years ago
Comments: 22 (6 by maintainers)

Most upvoted comments

@lesniara I resolved the issue. The account with which you are logged in needs contributor access both for the subscription as well as the active directory. Once you get that sorted, the app should be published easily.

prajwal-ainapur on Mar 10, 2022

It seems only Application Developer will not suffice, maybe Application Administrator.

As a work around, create manually the application on Azure AD, save the App ID and Secret value, go to your bot resource group and create an Azure Bot (since Bot channels are deprecated) and use the App info. After that, import only the App information using composer publishing profile and save, edit the profile and choose create new resoures and the wizard will take care of the rest.

Thanks, @flavio-neves for the suggestion regarding permissions. I have been facing the same issue and I assigned every admin permission to the user and still getting the error log.

manan0701 on Mar 4, 2022

contributor access both for the subscription as well as the active directory

Thanks @prajwal-ainapur the issue was that my personal hotmail account, that has the azure subscription, was not added to my windows accounts like my company account was. Once I did that the publishing/provisioning happened.

lesniara on Mar 10, 2022

OK 😃 I’ll try again with the nightly build later today

victorlamana on Jul 8, 2021

@stevengum yes, the new build has additional logging

natalgar on Jul 8, 2021

@natalgar, should @victorlamana & @shameeritc try the v2.0.0-nightly.257298.f833d8e nightly build of Composer to gather more info during the debugging process?

https://github.com/microsoft/BotFramework-Composer-Nightlies/releases/tag/v2.0.0-nightly.257298.f833d8e

stevengum on Jul 8, 2021

@stevengum hello Steven! Yeah, seems to be a similar issue

victorlamana on Jul 7, 2021