generating Firefox relay address set to block #1597

Closed
opened 2025-11-26 22:53:17 -06:00 by GiteaMirror · 2 comments
Owner

Originally created by @ButlerJoseph on GitHub (Feb 16, 2023).

Steps To Reproduce

  1. Go to 'generator'
  2. Click on 'forwarded email alias'
  3. Select service 'firefox relay'
  4. Click on 'generate username.'

Expected Result

A new Firefox relay address is created which is set to block emails set to none.

Actual Result

A new Firefox relay address is created which is set to block emails set to all.

Screenshots or Videos

No response

Additional Context

No response

Operating System

Android

Operating System Version

13

Device

No response

Build Version

2023.1.0 (5786)

Beta

  • Using a pre-release version of the application.
Originally created by @ButlerJoseph on GitHub (Feb 16, 2023). ### Steps To Reproduce 1. Go to 'generator' 2. Click on 'forwarded email alias' 3. Select service 'firefox relay' 4. Click on 'generate username.' ### Expected Result A new Firefox relay address is created which is set to block emails set to none. ### Actual Result A new Firefox relay address is created which is set to block emails set to all. ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Operating System Android ### Operating System Version 13 ### Device _No response_ ### Build Version 2023.1.0 (5786) ### Beta - [ ] Using a pre-release version of the application.
GiteaMirror added the bug label 2025-11-26 22:53:17 -06:00
Author
Owner

@atjbramley commented on GitHub (Feb 17, 2023):

Hi @ButlerJoseph ,

Thank you for your report!

I was able to reproduce this issue, and have flagged this to our engineering team.

If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these.

Thanks once again!

@atjbramley commented on GitHub (Feb 17, 2023): Hi @ButlerJoseph , Thank you for your report! I was able to reproduce this issue, and have flagged this to our engineering team. If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these. Thanks once again!
Author
Owner

@jwhitlock commented on GitHub (Feb 22, 2023):

We (the Firefox Relay team) have been able to reproduce this with the Bitwarden Android client (2023.1.0, Android 11, SDK 30).

The POST from the Bitwarden Android client appears to send a JSON body based on the request size. We do not log the body of the POST, so we can't see what is being sent by Bitwarden. It may be sending enabled: false or some other value that we're interpreting as False. Explicitly sending {"enabled": true} will work.

If you generate a Relay Address with an empty JSON body, then the address has enabled:true, and Block is set to None.

The Bitwarden website correctly generates addresses with Block set to None.

@jwhitlock commented on GitHub (Feb 22, 2023): We (the Firefox Relay team) have been able to reproduce this with the Bitwarden Android client (2023.1.0, Android 11, SDK 30). The `POST` from the Bitwarden Android client appears to send a JSON body based on the request size. We do not log the body of the `POST`, so we can't see what is being sent by Bitwarden. It may be sending `enabled: false` or some other value that we're interpreting as False. Explicitly sending `{"enabled": true}` will work. If you generate a Relay Address with an empty JSON body, then the address has `enabled:true`, and Block is set to None. The Bitwarden website correctly generates addresses with Block set to None.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#1597