Skip to content

Troubleshooting

Jump to bottom
Ben Weeks edited this page Oct 17, 2024 · 12 revisions
Problem description Resolution
When trying to purchase a Microsoft 365 Business Basic license you receive Please try again in a few minutes. We are unable to complete the verification check on your payment method at this time According to Microsoft:

For this, this error is generally just created an account, the company information is still being verified. For this, you need to contact billing support team to provide company information - name, address, phone, email, etc. After do a verification, this can be unlocked. For contacting, please refer to Get support - Microsoft Support.

Possible solutions:

  1. Wait 24 hours for the accounts team to verify your account.
  2. If you already have a billing tenant (such as in another tenant), you could trying copying your tenant ID from there (see Learn more about associated billing tenants and into the Microsoft Admin Portal by going to Billing > Billing account and selecting Add an associated billing tenant (give your tenant a display name of "Bens Dev" for example when sending the request). You will need to copy/paste the request link for it to be approved. Ensure that is says Active for Provisioning.
  3. If you sign-up as a business, check your company name, VAT number, company address and VAT registration number are are correct in Billing > Billing accounts section.
  4. Edit your card details and try again.
Unable to deploy bot.

Ensure that custom app uploads are allowed:

  1. Login to Microsoft Teams Administration using the global administrator account you created above.
  2. Go to Teams apps > Setup Policies > Global.
  3. Make sure that Toggle for Upload custom apps is in On position.
  4. Click Save and your test tenant can permit custom app upload.

Try deleting the following files and trying again:

  1. build > aad.manifest_local.json
  2. env\.env.local
  3. env\.env.local.user
  4. .localConfigs

Try incrementing the version number in appPackage\manifest.json

Try closing and re-opening VS Code.
invalid_client: AADSTS650057: Invalid resource. The client has requested access to a resource which is not listed in the requested permissions in the client's application registration. Client app ID: 6070a4e4-56eb-4c93-b889-56955b9d95d8(Zapp.ie). Resource value from request: https://api.powerapps.com. Resource app ID: 475226c6-020e-4fb2-8a90-7a972cbfc1d4. List of valid resources from app registration: 00000003-0000-0000-c000-000000000000.
  1. Navigate to Azure Portal
  2. Go to App registrations and All applications and search for the application with the Client app ID given in the error.
  3. Open the app registration, and open API registrations.
  4. Add the PowerApps runtime service.
  5. Grant Admin consent.
You receive the following error when you try to deploy the bot:

Failed to Execute lifecycle deploy due to failed action: cli/runNpmCommand. ScriptExecutionError:Unable to execute script action.. Env output: {}
  1. Delete the nodule_modules folder. From the command line you can run Remove-Item -Recurse -Force node_modules
  2. Delete package-lock.json file. From the commmand line you can run Remove-Item -Force package-lock.json
  3. Run npm install
You cannot see the bot in Teams Ensure that the Provision and Publish steps have been run in VS Code Teams Extension.

Go to Teams Administration and ensure your app has been published and is not blocked.
Failed to parse URL from undefined/usermanager/api/v1/users?extra={"aadObjectId":"aaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaaaa"} The environment variables are not available.
You receive the following error when you try to provision the bot:

(×) Error: coordinator.ResourceGroupNotExistError: The resource group 'rg-Zapp5db0f0-dev' cannot be found in subscription '00000000-0000-0000-0000-000000000000'. 		This can occur if you try to delete a previous installation, and the resource group no longer exists. To restore the resource group, you can run:

az group create --name rg-Zapp5db0f0-dev --location "UK South" --subscription 00000000-0000-0000-0000-000000000000

Delete the localConfig file and run the provisioning again.
Uploading customised apps is not allowed.
  1. Open a web browser and go to the Microsoft Teams admin center.
  2. Sign in with your admin credentials.
  3. In the left-hand navigation pane, go to Teams apps.
  4. Click on Manage apps.
  5. In the Manage apps section, click on Actions > Org-wide app settings.
  6. Ensure Let users install and use available apps by default is switched on.
When trying to publish the app in the Microsoft Teams Admin, you see:

We can't get details related to this app. Try again. If you continue to have problems, contact Microsoft.

Or in the console you see:

safeFunc() unexpected failure in onInvoke: TypeError: Cannot read properties of undefined (reading 'stagedAppEntitlement') at TypeError: Cannot read properties of undefined (reading 'stagedAppEntitlement') 		The error message indicates that there is an issue with reading a property (stagedAppEntitlement) that is undefined. This could be due to a misconfiguration in your app manifest or an issue with the environment variables not being correctly loaded.
You see Failed to load when running commands on a local bot ⁠Remove the BOT_ENDPOINT, BOT_DOMAIN and BOT_ID from .env.local and try again.
When trying to run the React web app, you receive

chroma__default.default.scale is not a function TypeError: chroma__default.default.scale is not a function
  1. Clear the browser cache.
  2. Rebuild the node_module folder running:
    Remove-Item -Recurse -Force node_modules
Remove-Item -Force package-lock.json
npm install
Clone this wiki locally