-
Notifications
You must be signed in to change notification settings - Fork 372
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"User was not found" While following publish steps after Azure login #3324
Comments
@zxyanliu - As I mentioned that error is on step 3, which is kind of first step because if you see my snapshot, i opened the command prompt pointing to correct location and then it was just npm install. |
@GAURI02X ok. So you have two Azure accounts: a personal and a org's account. You tried with your personal azure account and failed, and you did not get the error if using your org's Azure account? |
@zxyanliu I am not supposed to use that account till we have POC ready. Can't try with that account but its there on machine and it shows when I do azure login with code provided in command prompt. Could you please help me with workaround or solution. My POC is stuck due to this. |
Thanks @zxyanliu
|
Hi @GAURI02X , maybe you should add a unique identifier to your bot name. Have you solved this problem? |
Works for me .Thanks! |
Subject error with 1.0.0 & 1.0.1 version. I used 1.0.0 version and on first step after Azure login with Hotmail Id, got subject error. Same happened after today's update to 1.0.1
node provisionComposer.js --subscriptionId=XXXXXXXXXXXX --name=XXXX --appPassword=XXXXXXX --environment=Dev
I created a sample project from template but on first publish step again got same error.
Version
Composer version 1.0.0 & 1.0.1
and
SDK runtime packages
4.9.3
Browser
Developing on composer and script execution on command prompt
OS
To Reproduce
Steps to reproduce the behavior:
Hope above steps are sufficient.
Expected behavior
Publish should happen as mentioned in tutorial.
Screenshots
Additional context
The text was updated successfully, but these errors were encountered: