App create failed when publishing from composer desktop 2.0 with new resources #8283

stevengum · 2021-07-07T18:35:49Z

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).

stevengum · 2021-07-07T18:39:38Z

Adding @Shameeritc and @victorlamana as FYI

@victorlamana I believe the issue you originally referenced is #8249, correct?

victorlamana · 2021-07-07T18:59:16Z

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

stevengum · 2021-07-07T19:00:42Z

@victorlamana understood, thank you for the quick confirmation!

stevengum · 2021-07-08T17:57:16Z

@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

natalgar · 2021-07-08T18:01:48Z

@stevengum yes, the new build has additional logging

victorlamana · 2021-07-08T19:32:37Z

OK :) I'll try again with the nightly build later today

davidpp · 2021-07-09T18:04:18Z

Hi!

We just hit a similar issue trying to provision resources from Composer V2 into a customer resource group. That customer also use 2FA where we do not.

Error:

App create failed after 3 retries. Error: Request failed with status code 403" --> The status code 403 error is the only difference between a regular build and the nightly one.

{"name":"CREATE_APP_REGISTRATION","message":"App create failed! Please file an issue on Github.","stack":"Error\n at new CustomizeError (/private/var/folders/kf/m3grsrb15zjdypf9b7m6778h0000gp/T/AppTranslocation/3FA91673-EB1F-406B-BC2D-4518EB8EC11F/d/Bot Framework Composer.app/Contents/Resources/app.asar.unpacked/extensions/azurePublish/dist/extension.js:224307:25)\n at createCustomizeError (/private/var/folders/kf/m3grsrb15zjdypf9b7m6778h0000gp/T/AppTranslocation/3FA91673-EB1F-406B-BC2D-4518EB8EC11F/d/Bot Framework Composer.app/Contents/Resources/app.asar.unpacked/extensions/azurePublish/dist/extension.js:224312:10)\n at BotProjectProvision.createApp (/private/var/folders/kf/m3grsrb15zjdypf9b7m6778h0000gp/T/AppTranslocation/3FA91673-EB1F-406B-BC2D-4518EB8EC11F/d/Bot Framework Composer.app/Contents/Resources/app.asar.unpacked/extensions/azurePublish/dist/extension.js:225806:17)"}

Edit: We using Composer on MacOS

victorlamana · 2021-07-12T11:08:01Z

Hello! This is the error I get on the nightly build:

{"name":"CREATE_APP_REGISTRATION","message":"App create failed! Please file an issue on Github.","stack":"Error\n at new CustomizeError (C:\\Program Files\\Bot Framework Composer\\resources\\app.asar.unpacked\\extensions\\azurePublish\\dist\\extension.js:224307:25)\n at createCustomizeError (C:\\Program Files\\Bot Framework Composer\\resources\\app.asar.unpacked\\extensions\\azurePublish\\dist\\extension.js:224312:10)\n at BotProjectProvision.createApp (C:\\Program Files\\Bot Framework Composer\\resources\\app.asar.unpacked\\extensions\\azurePublish\\dist\\extension.js:225806:17)"}. See provision.AzureLABpub.log in your bot folder

This is the log created for the error:

{ "profileName": "AzureLABpub", "jobId": "b5825e42-7d1e-4a39-a6fd-d2c68d2157e9", "projectId": "18805.295347112682", "time": "2021-07-12T11:05:53.955Z", "log": [ "Creating Azure resources...", "Checking the Existence of the Resource Group ...", "Use the Resource Group: ldc-covid-aid at northeurope", "> Creating App Registration ...", "App create failed, retrying ...", "App create failed, retrying ...", "App create failed, retrying ...", "App create failed, retrying ...", "App create failed after 3 retries. Error: Request failed with status code 403", "{\"name\":\"CREATE_APP_REGISTRATION\",\"message\":\"App create failed! Please file an issue on Github.\",\"stack\":\"Error\\n at new CustomizeError (C:\\\\Program Files\\\\Bot Framework Composer\\\\resources\\\\app.asar.unpacked\\\\extensions\\\\azurePublish\\\\dist\\\\extension.js:224307:25)\\n at createCustomizeError (C:\\\\Program Files\\\\Bot Framework Composer\\\\resources\\\\app.asar.unpacked\\\\extensions\\\\azurePublish\\\\dist\\\\extension.js:224312:10)\\n at BotProjectProvision.createApp (C:\\\\Program Files\\\\Bot Framework Composer\\\\resources\\\\app.asar.unpacked\\\\extensions\\\\azurePublish\\\\dist\\\\extension.js:225806:17)\"}", "{\"name\":\"CREATE_APP_REGISTRATION\",\"message\":\"App create failed! Please file an issue on Github.\",\"stack\":\"Error\\n at new CustomizeError (C:\\\\Program Files\\\\Bot Framework Composer\\\\resources\\\\app.asar.unpacked\\\\extensions\\\\azurePublish\\\\dist\\\\extension.js:224307:25)\\n at createCustomizeError (C:\\\\Program Files\\\\Bot Framework Composer\\\\resources\\\\app.asar.unpacked\\\\extensions\\\\azurePublish\\\\dist\\\\extension.js:224312:10)\\n at BotProjectProvision.createApp (C:\\\\Program Files\\\\Bot Framework Composer\\\\resources\\\\app.asar.unpacked\\\\extensions\\\\azurePublish\\\\dist\\\\extension.js:225806:17)\"}. See provision.AzureLABpub.log in your bot folder" ] }

Thanks!!!! :)

flavio-neves · 2021-07-12T18:54:42Z

Hi guys,

This error is due to lack of Azure AD permission to create the App itself. You need to add your account into "Application developer" or "Application administrator".

The Composer console will try to create an Azure AD, App in Registration tab, as you may see on my screenshot.

Composer resource creation screen:

Azure AD Application Registration screen:

[Edited to add Composer screenshot as well]

flavio-neves · 2021-07-14T19:37:46Z

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.

stevengum · 2021-08-17T18:31:14Z

@natalgar do you have any new findings/workarounds to share?

natalgar · 2021-08-23T15:58:26Z

For anyone getting a 403 response, I have some more questions to help with the debugging. If you can answer these questions the next time you run into it that would help. Thanks!

Does this happen every time you provision?
What type of account are you using? Is it a work, school, or Microsoft account?
What is your "role" for the subscription you are using? You can find this by looking up your subscriptions in the Azure Portal.
Are you creating a new resource group or updating an existing one?
When the provision fails, what is the result in Azure Portal? What resources were successfully created?
If the App Registration is successfully created, navigate to it in the Azure Portal. In the left side panel of the App Registration, select Authentication. Check if there are any restrictions under "Supported Account Types".

prajwal-ainapur · 2021-12-09T09:30:46Z

Hi @natalgar ,

I am also facing same issue. Please find the required details below as asked in your earlier comment.

Does this happen every time you provision?
- Yes.This happens all the time

What type of account are you using? Is it a work, school, or Microsoft account?
- It is a Microsoft Paid Subscription through one of the vendor

What is your "role" for the subscription you are using? You can find this by looking up your subscriptions in the Azure Portal.
- My role is "Owner access", So authorization shouldn't be a cause for the issue

Are you creating a new resource group or updating an existing one?
- I tried both. It's not working in both option. When i try creating a new resource group, it creates the new group but again fails at app registration part

When the provision fails, what is the result in Azure Portal? What resources were successfully created?
- No resource is created. Only resource group gets created if you take the new resource group option

Hope this helps in fixing the issue. Any alternative solution in the meanwhile is highly appreciated.

sinnypan · 2021-12-29T02:05:52Z

Hi @natalgar,@dmvtech ,

I am also facing same issue. Please find the required details below:

Does this happen every time you provision?

No. But its happens all the time for my client's windows computer. He never be able to publish to azure.

What type of account are you using? Is it a work, school, or Microsoft account?

It is a customer-paid subscription, and its work MS account.

What is your "role" for the subscription you are using? You can find this by looking up your subscriptions in the Azure Portal.

The role is "Contributor", and we've tested he can create app and Azure resources using Azure portal

Are you creating a new resource group or updating an existing one?

Creating new resources (the first option)

We're using the latest version 2.1.1, we even tried nightbird version, still the same. Do you have any thoughts about this? Thanks!

manan0701 · 2022-03-04T03:45:50Z

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.

lesniara · 2022-03-09T21:04:50Z

Anyone got this working? Is there a way to create the profile on Azure, perhaps? Using composer v2.1.2
Thanks

Having the same issue:

Error:
Provision failure {"name":"CREATE_APP_REGISTRATION","message":"App create failed! Please file an issue on Github.","stack":"Error\n at new CustomizeError (C:\\Users\\alex\\AppData\\Local\\Programs\\Bot Framework Composer\\resources\\app.asar.unpacked\\extensions\\azurePublish\\dist\\extension.js:276418:25)\n at createCustomizeError (C:\\Users\\alex\\AppData\\Local\\Programs\\Bot Framework Composer\\resources\\app.asar.unpacked\\extensions\\azurePublish\\dist\\extension.js:276423:10)\n at BotProjectProvision.createApp (C:\\Users\\alex\\AppData\\Local\\Programs\\Bot Framework Composer\\resources\\app.asar.unpacked\\extensions\\azurePublish\\dist\\extension.js:277931:17)"}. See provision.ACDBotPublishingProfile.log in your bot folder

The file the error refers to:

{
"profileName": "ACDAzurePublishingProfile",
"jobId": "c857f53a-ae48-4e94-b6ee-4196cb1278c1",
"projectId": "77154.25052250133",
"time": "2022-03-09T20:33:42.192Z",
"log": [
"Creating Azure resources...",
"Checking the Existence of the Resource Group ...",
"Use the Resource Group: ACDBot at westus",
"> Creating App Registration ...",
"App create failed, retrying ...",
"App create failed, retrying ...",
"App create failed, retrying ...",
"App create failed, retrying ...",
"App create failed after 3 retries. Error: Request failed with status code 401",
"{"name":"CREATE_APP_REGISTRATION","message":"App create failed! Please file an issue on Github.","stack":"Error\n at new CustomizeError (C:\\Users\\alex\\AppData\\Local\\Programs\\Bot Framework Composer\\resources\\app.asar.unpacked\\extensions\\azurePublish\\dist\\extension.js:276418:25)\n at createCustomizeError (C:\\Users\\alex\\AppData\\Local\\Programs\\Bot Framework Composer\\resources\\app.asar.unpacked\\extensions\\azurePublish\\dist\\extension.js:276423:10)\n at BotProjectProvision.createApp (C:\\Users\\alex\\AppData\\Local\\Programs\\Bot Framework Composer\\resources\\app.asar.unpacked\\extensions\\azurePublish\\dist\\extension.js:277931:17)"}",
"{"name":"CREATE_APP_REGISTRATION","message":"App create failed! Please file an issue on Github.","stack":"Error\n at new CustomizeError (C:\\Users\\alex\\AppData\\Local\\Programs\\Bot Framework Composer\\resources\\app.asar.unpacked\\extensions\\azurePublish\\dist\\extension.js:276418:25)\n at createCustomizeError (C:\\Users\\alex\\AppData\\Local\\Programs\\Bot Framework Composer\\resources\\app.asar.unpacked\\extensions\\azurePublish\\dist\\extension.js:276423:10)\n at BotProjectProvision.createApp (C:\\Users\\alex\\AppData\\Local\\Programs\\Bot Framework Composer\\resources\\app.asar.unpacked\\extensions\\azurePublish\\dist\\extension.js:277931:17)"}. See provision.ACDAzurePublishingProfile.log in your bot folder"
]
}

prajwal-ainapur · 2022-03-10T04:08:40Z

@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.

lesniara · 2022-03-10T15:15:27Z

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.

pablodiloreto · 2022-09-23T05:57:25Z

Hello team! The context that start this issue is that you are working with a personal account into a default directory in your Azure Subscription. To resolve it, you do not need to create ANY resource in manual mode: you need to create a user in your Azure AD Directory (for example user1@xxxxxxxx.onmicrosoft.com) and give to this user a permission to create and register applications in your Azure AD Directory (for example Global Admin, Contributor, etc).

After that, you need to give to the same created user permissions to the Azure subscription (or resource group) where you will deploy your bot from Bot Framework Composer (for example Owner).

Lastly, you need to login to your Bot Framework Composer with this new user, and there the error will be gone.

I repeat: it is not an application error, it is an error because you are working with a personal user and not a business user. Working with a business, in this case, has no cost.

dsivajagan · 2023-02-09T03:50:53Z

Any fix/work around on this issue as I am also facing the same issue?. I tried the work arounds as suggested above, but no luck.

Pasting the exception here from the log file
{
"profileName": "adasfd",
"jobId": "95dd6834-2e35-471e-b668-7b11ff6ee353",
"projectId": "9392.584853167762",
"time": "2023-02-09T03:37:06.576Z",
"log": [
"Creating Azure resources...",
"Checking the Existence of the Resource Group ...",
"Use the Resource Group: OBAResourceGroup at eastus",
"> Creating App Registration ...",
"App create failed, retrying ...",
"App create failed, retrying ...",
"App create failed, retrying ...",
"App create failed, retrying ...",
"App create failed after 3 retries. Error: self signed certificate in certificate chain",
"{"name":"CREATE_APP_REGISTRATION","message":"App create failed! Please file an issue on Github.","stack":"Error\n at new CustomizeError (/Applications/Bot Framework Composer.app/Contents/Resources/app.asar.unpacked/extensions/azurePublish/dist/extension.js:276418:25)\n at createCustomizeError (/Applications/Bot Framework Composer.app/Contents/Resources/app.asar.unpacked/extensions/azurePublish/dist/extension.js:276423:10)\n at BotProjectProvision.createApp (/Applications/Bot Framework Composer.app/Contents/Resources/app.asar.unpacked/extensions/azurePublish/dist/extension.js:277931:17)"}",
"{"name":"CREATE_APP_REGISTRATION","message":"App create failed! Please file an issue on Github.","stack":"Error\n at new CustomizeError (/Applications/Bot Framework Composer.app/Contents/Resources/app.asar.unpacked/extensions/azurePublish/dist/extension.js:276418:25)\n at createCustomizeError (/Applications/Bot Framework Composer.app/Contents/Resources/app.asar.unpacked/extensions/azurePublish/dist/extension.js:276423:10)\n at BotProjectProvision.createApp (/Applications/Bot Framework Composer.app/Contents/Resources/app.asar.unpacked/extensions/azurePublish/dist/extension.js:277931:17)"}. See provision.adasfd.log in your bot folder"
]
}

amitkadu · 2023-08-14T12:58:13Z

Same issue for me, tried all possible answers provided here like providing contributor access on subscription, Application developer role on AD. But none help. @pablodiloreto @prajwal-ainapur

gersepa · 2024-01-30T02:08:13Z

Is there any resolution to this?

stevengum added the Type: Bug Something isn't working label Jul 7, 2021

stevengum assigned VamsiModem and natalgar and unassigned VamsiModem Jul 7, 2021

stevengum added the Area: Publish label Jul 7, 2021

natalgar mentioned this issue Jul 7, 2021

fix: log error message on final retry when "app create" or "add password" fails #8286

Merged

natalgar mentioned this issue Jul 8, 2021

Provision failure - App create failed! #8249

Closed

6 tasks

luhan2017 mentioned this issue Jul 27, 2021

Publish as skill failed: publishing from desktop 2.0 with new resources #8457

Closed

8 tasks

tonyanziano mentioned this issue Aug 26, 2021

Got a problem when publishing bot in azure #8603

Closed

dmvtech mentioned this issue Sep 6, 2021

App create failed after 3 retries. Error: Request failed with status code 403 #8633

Closed

abechelli mentioned this issue May 20, 2022

Chatbot can't be published to Azure #9192

Closed

8 tasks

dmvtech mentioned this issue Jan 4, 2023

Unable to create a publishing profile in Azure #9425

Closed

tracyboehrer unassigned natalgar Mar 8, 2023

Tz611 mentioned this issue Feb 6, 2024

Provision Failure in publishing by creating a new resource as well as using the existing resource #9697

Closed

5 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

App create failed when publishing from composer desktop 2.0 with new resources #8283

App create failed when publishing from composer desktop 2.0 with new resources #8283

stevengum commented Jul 7, 2021

stevengum commented Jul 7, 2021

victorlamana commented Jul 7, 2021

stevengum commented Jul 7, 2021

stevengum commented Jul 8, 2021

natalgar commented Jul 8, 2021

victorlamana commented Jul 8, 2021

davidpp commented Jul 9, 2021 •

edited

victorlamana commented Jul 12, 2021

flavio-neves commented Jul 12, 2021 •

edited

flavio-neves commented Jul 14, 2021

stevengum commented Aug 17, 2021

natalgar commented Aug 23, 2021

prajwal-ainapur commented Dec 9, 2021 •

edited

sinnypan commented Dec 29, 2021 •

edited

manan0701 commented Mar 4, 2022 •

edited

lesniara commented Mar 9, 2022 •

edited

prajwal-ainapur commented Mar 10, 2022

lesniara commented Mar 10, 2022

pablodiloreto commented Sep 23, 2022

dsivajagan commented Feb 9, 2023 •

edited

amitkadu commented Aug 14, 2023

gersepa commented Jan 30, 2024

App create failed when publishing from composer desktop 2.0 with new resources #8283

App create failed when publishing from composer desktop 2.0 with new resources #8283

Comments

stevengum commented Jul 7, 2021

Describe the bug

Version

Browser

To Reproduce

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

Expected behavior

Additional context

stevengum commented Jul 7, 2021

victorlamana commented Jul 7, 2021

stevengum commented Jul 7, 2021

stevengum commented Jul 8, 2021

natalgar commented Jul 8, 2021

victorlamana commented Jul 8, 2021

davidpp commented Jul 9, 2021 • edited

victorlamana commented Jul 12, 2021

flavio-neves commented Jul 12, 2021 • edited

flavio-neves commented Jul 14, 2021

stevengum commented Aug 17, 2021

natalgar commented Aug 23, 2021

prajwal-ainapur commented Dec 9, 2021 • edited

sinnypan commented Dec 29, 2021 • edited

manan0701 commented Mar 4, 2022 • edited

lesniara commented Mar 9, 2022 • edited

prajwal-ainapur commented Mar 10, 2022

lesniara commented Mar 10, 2022

pablodiloreto commented Sep 23, 2022

dsivajagan commented Feb 9, 2023 • edited

amitkadu commented Aug 14, 2023

gersepa commented Jan 30, 2024

davidpp commented Jul 9, 2021 •

edited

flavio-neves commented Jul 12, 2021 •

edited

prajwal-ainapur commented Dec 9, 2021 •

edited

sinnypan commented Dec 29, 2021 •

edited

manan0701 commented Mar 4, 2022 •

edited

lesniara commented Mar 9, 2022 •

edited

dsivajagan commented Feb 9, 2023 •

edited