Fastmail email alias returning error message "forDomain" cannot be null

[hongyilyu]

Steps To Reproduce

1. Go to Generator Tab
2. Select Username to generate
3. Select Forwarded email alias as Username type
4. Select Fastmail as service provider
5. Input API Key
6. Tap on generate on top right next to copy button

Expected Result

An email alias being generated

Actual Result

Error Message dialog pop up, indicating 'forDoamin' in 'masked email' cannot be null

Screenshots or Videos

Additional Context

No response

Build Version

2024.12.0(1740)

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

Device: iPhone 15 PM
iOS version: 18.1.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.

[atridadl]

Same here. Have not tried other providers to see if similar.

[liambresnahan]

+1 I see the same issue here.

[liambresnahan]

To add, this is a problem in Version: 2025.1.3 (1884) as well

[mpeterson]

This was addressed on other clients as a fix for bug #9183.

[philnagel]

This was addressed on other clients as a fix for bug #9183.

It looks like the fix was to change from sending null to an empty string. I think the fix in that issue is not correct. It may be valid when the alias does not get created in the context of creating or editing a login, but when this is part of a login form, it should be sending an actual value for forDomain as it is available. Instead, it seems to be sending an empty string all the time.
It would be very helpful to have the forDomain populated by Bitwarden as it shows up in the Fastmail UI - otherwise, we have no idea which website the alias is associated with.

[mpeterson]

I agree it’s not the best behavior but at least make it consistent across clients