Open Jiayou-Chao opened 7 months ago
Hi there,
I attempted to reproduce your issue and was unable to do so. I think your error could have its origin in a network misconfiguration.
We use GitHub issues as a place to track bugs and other development related issues. If your issue persists, please write us back using our “Contact support” form located on our Help Center (https://bitwarden.com/help/).
You can include a link to this issue in the message content.
The issue here will be closed.
Thanks!
Hi @Jiayou-Chao,
Thank you for your report. I wanted to follow up and let you know that I was able to reproduce this behaviour after further testing, and have flagged it to our Engineering team. This report will remain open for now.
If you wish to add any further information, such as screenshots or screen recordings, please feel free to do so at any time - our Engineering team will be happy to review them.
Thank you again,
I am currently encountering the same issue and have taken the initiative to submit a bug report. Unfortunately, it has been a month, and the user experience with the Edge client has significantly deteriorated for me, considering Edge is my default browser. Specifically, I am unable to generate aliases seamlessly. The current workaround involves creating an alias on my mobile device, manually transcribing it onto paper, and then inputting it when saving a login on my desktop. This process is cumbersome and hampers the overall efficiency of using the application. I earnestly request the developers to address and rectify this bug, extending a plea for a swift resolution with folded hands.
Title: Failed to fetch error when generating emails with DuckDuckGo API on Edge
Summary: When using the Bitwarden extension on Microsoft Edge, the feature to generate email aliases with DuckDuckGo API fails with a "Failed to fetch" error message. This issue occurs on the latest version of the extension and the browser, and does not affect the mobile client. The issue started after two days of using the feature successfully.
Steps to reproduce:
Expected result: A new email alias is generated and filled in the email field
Actual result: A "Failed to fetch" error message is displayed and no email alias is generated
Environment: Windows 11, Microsoft Edge version 121.0.2277.98, Bitwarden extension version 2024.1.1, Bitwarden mobile client version 2024.1.1
Additional information: This issue seems to be related to the Edge browser, as the same feature works fine on the mobile client. There is no known workaround or fix for this issue at the moment.
Hi @Jiayou-Chao,
Thank you for your report. I wanted to follow up and let you know that I was able to reproduce this behaviour after further testing, and have flagged it to our Engineering team. This report will remain open for now.
If you wish to add any further information, such as screenshots or screen recordings, please feel free to do so at any time - our Engineering team will be happy to review them.
Thank you again,
Hi, it seems this issue is still present. Please tell us if this is being addressed.
Best regards!
I have the same problem Microsoft edge browser on Windows 11
I see the same “Failed to Fetch” for DuckDuckGo email generation using the Arc browser on macOS Sonoma. The same API works correctly in Chrome. It is almost like the API key is not even used. I do not know if the API key was mentioned above for Edge.
While it is not on the Edge or Windows, it seems to fail similarly. What is the latest info on this?
Steps To Reproduce
Expected Result
A duckduckgo email alias address
Actual Result
An error message:
Failed to fetch
.Screenshots or Videos
No response
Additional Context
There is already a discussion on the community forum. I can generate it on the Firefox extension, so it shouldn't be an issue with the API key. This error seems to only occur on the Edge extension.
Operating System
Windows
Operating System Version
Windows 11
Web Browser
Microsoft Edge
Browser Version
Version 119.0.2151.93 (Official build) (64-bit)
Build Version
2023.10.2
Issue Tracking Info