-
Notifications
You must be signed in to change notification settings - Fork 391
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
Sandbox authentication from vs code #5577
Comments
@sfsagar would you mind providing the information requested in the issue template? I will be happy to help once I have the needed information. |
@peternhale
Soon will share the required version of all app requested.But just FYI I can able to authorise othe sandbox but not dev |
@sfsagar I would suggest trying again but use -r https://test.salesforce.com instead of instance URL. Could you provide the org id of the org you are trying to auth to? |
@sfsagar were you able to try the suggestion? |
On Monday will check and confirm.
Thank you
…On Fri, May 10, 2024, 9:21 PM peternhale ***@***.***> wrote:
@sfsagar <https://github.com/sfsagar> were you able to try the suggestion?
—
Reply to this email directly, view it on GitHub
<#5577 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXGU2G6RP6EBAWXVYKQBBLTZBTUGLAVCNFSM6AAAAABHJMSOYGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBUHA2DAMZUHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
This issue has not received a response in 3 days. It will auto-close in 2 days unless a response is posted. |
Hi All,
I am trying to connect vs code to Salesforce Dev sandbox but i enter custom domain and org name details click enter
Then in browser the login page open but then suddenly the below error appears in my screen
Intresting thing is if I try to connect with my other sandbox like INT,QA,UAT they get authenticate properly and able to connect vs code.
Only facing issues while connecting to Dev sandbox, what could be the reason. Really appreciate someone input to resolve the issue
The text was updated successfully, but these errors were encountered: