DuckDuckGo Email Alias Generator Error on Android

Nail1684 · August 21, 2025, 12:18am

@ehill27 Seems like a current bug that was reported on GitHub:

github.com/bitwarden/android

[PM-24637] Unable to generate Username using API Key

opened 08:33AM - 11 Aug 25 UTC

closed 08:15PM - 20 Aug 25 UTC

maz-saify

bug app:password-manager

### Steps To Reproduce 1. Go to 'Generator' tab. 2. Click on 'Username' tab. 3.… Select Username type as 'Forward Email Alias'. 4. Select service as 'SimpleLogin' or 'DuckDuckGo'. 5. Provide API Key. 6. Click on generate button. ### Expected Result It should generate random email address. ### Actual Result It shows error "Error sending request" and does not generate the username. ### Screenshots or Videos ![Image](https://github.com/user-attachments/assets/144982ff-9dc2-479d-9f38-6e6a0e1d1185) ### Additional Context See Flight Recorder Logs in attachment. [flight_recorder_2025-08-10_00-20-37.txt](https://github.com/user-attachments/files/21774261/flight_recorder_2025-08-10_00-20-37.txt) ### Build Version 2025.07.02 (20551) ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details - Device: Galaxy A55 - OS Version: 15 ### Issue Tracking Info - [x] 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.

And it already has a merged fix (though I can’t tell, if it will make it into the next Android release 2025.8.0):

github.com/bitwarden/android

[PM-24697] Allow cleartext traffic on OCSP and CRL servers

main ← PM-24697/add-ocsp-crl-responder-cleartextallowed

opened 05:35PM - 20 Aug 25 UTC

aj-rosado

+12 -0

## 🎟️ Tracking https://bitwarden.atlassian.net/browse/PM-24697 ## 📔 Object…ive SDK is using HTTP uris for CRL and OCSP checking and was causing the generator to fail when verifying forwarders. This adds the servers for the `cleartextTrafficPermitted` exception list on the `network_security_config` file ## ⏰ Reminders before review - Contributor guidelines followed - All formatters and local linters executed and passed - Written new unit and / or integration tests where applicable - Protected functional changes with optionality (feature flags) - Used internationalization (i18n) for all UI strings - CI builds passed - Communicated to DevOps any deployment requirements - Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team ## 🦮 Reviewer guidelines - 👍 (`:+1:`) or similar for great changes - 📝 (`:memo:`) or ℹ️ (`:information_source:`) for notes or general info - ❓ (`:question:`) for questions - 🤔 (`:thinking:`) or 💭 (`:thought_balloon:`) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion - 🎨 (`:art:`) for suggestions / improvements - ❌ (`:x:`) or ⚠️ (`:warning:`) for more significant problems or concerns needing attention - 🌱 (`:seedling:`) or ♻️ (`:recycle:`) for future improvements or indications of technical debt - ⛏ (`:pick:`) for minor or nitpick changes