Open LaurenWags opened 1 year ago
@LaurenWags I can't seem to repro this using the latest master. Specifically, at step 7 I'm not logged out. Curious if you're still seeing this on the latest nightlies?
@emerick interesting, I did get logged out at step 7 (opened panel to confirm).
Followed STR from description, here are some screenshots (not sure if they're helpful):
Step 4 | Step 7 | Step 8 | Step 12 | Step 12 |
---|---|---|---|---|
Used below version:
Brave | 1.51.31 Chromium: 111.0.5563.64 (Official Build) nightly (x86_64)
-- | --
Revision | c710e93d5b63b7095afe8c2c17df34408078439d-refs/branch-heads/5563@{#995}
OS | macOS Version 12.6.3 (Build 21G419)
Description
This is a problem likely unique to QA and perhaps development, not a problem that users are likely to face:
When you are connected to a custodian on staging environment and you accidentally launch the browser with production environment (not staging), you get logged out of the custodian which makes sense. If you try to login, you notice you're on production as expected so you close and relaunch w/ staging command line flags. However, after relaunching you cannot connect to custodian's sandbox as something appears to be caching the call to production.
Steps to Reproduce
Actual result:
Unable to reconnect to sandbox custodian
Expected result:
able to reconnect to sandbox custodian
Reproduces how often:
easily
Brave version (brave://version info)
1.48.x (@LaurenWags reproduced), 1.50.x (@MadhaviSeelam reproduced)
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
cc @Miyayes