Add Support for Retrieving User Email on Sign-In

[YASH-YADAV-dynamo]

Currently, there is no way to access the email ID of a user who signs in using their email. This limitation prevents proper user identification, communication, and account management.

Expected Behavior:
The system should capture and return the user's email upon successful authentication.

Actual Behavior:
The email is not accessible after sign-in, limiting its use for further actions.

Proposed Solution:
Modify the authentication flow to include email retrieval and expose it where necessary.

the file where I noticed this could be implemented through is Reference File

[emperorjm]

Hi @YASH-YADAV-dynamo. An email address is not the only authenticator that a user can utilize and each account can have more than one authenticators as shown in the settings app https://settings.testnet.burnt.com which means you can authenticate to the same meta account using multiple different methods. If the user decides not to use email then your app would break.

So the identifier I believe you should focus on is the Meta Account address.

Could you explain further your use case?

[YASH-YADAV-dynamo]

I want to use the email ID not for authorization but to store it and use it for various purposes, such as invites.

[emperorjm]

Got it, but email isn't the only authentication method available to users. If you need their email address, it's best to request it separately.

[YASH-YADAV-dynamo]

"Yes, I'm already doing that. However, since the user signs in using their email, it would be more consistent and seamless if we could directly access their email ID."

Would love to know your views .

[emperorjm]

If your dapp is dependent on users email address and 60% of your users decide to authenticate with Passkey, 20% deciding to utilize Keplr or another wallet and only 20% deciding to use email address, then 80% of your users will not be able to access features dependent on email address. This is why I recommend if you dapp needs access to users email addresses then you should request this from the users.

There is a privacy component to this as well and we wouldn't want to have that as issue.