You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Open the browser extension where you are signed in the latest version of Edge
Click Generate
Select username
Select Forwarded e-mail alias
Select DuckDuckGo
Enter the API key if you don't have it registered already
Click on Regenerate username
Expected Result
New DuckDuckGo forwarded e-mail alias displayed in the username field.
Actual Result
An error has occured
Failed to fetch
Screenshots or Videos
No response
Additional Context
The desktop client with the same API key does not have the problem and succeeds in connecting to DuckduckGo API and acquiring a new forwarded e-mail alias
Operating System
Windows
Operating System Version
22635.2700
Web Browser
Microsoft Edge
Browser Version
120.0.2210.121
Build Version
2023.12.1
Issue Tracking Info
I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
The text was updated successfully, but these errors were encountered:
Thank you for your report, it seems like it is a duplicate of this one #7082
If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time in there - our engineering team will be happy to review these.
Steps To Reproduce
Regenerate username
Expected Result
New DuckDuckGo forwarded e-mail alias displayed in the username field.
Actual Result
An error has occured
Failed to fetch
Screenshots or Videos
No response
Additional Context
The desktop client with the same API key does not have the problem and succeeds in connecting to DuckduckGo API and acquiring a new forwarded e-mail alias
Operating System
Windows
Operating System Version
22635.2700
Web Browser
Microsoft Edge
Browser Version
120.0.2210.121
Build Version
2023.12.1
Issue Tracking Info
The text was updated successfully, but these errors were encountered: