
Hey there,
I am trying to implement the e-mail verification. In general my app uses primarily Flutter (iOS and Android). Maybe in the future I would like to add a web frontend.
So the current state is that I have my SMTP set up. In the Flutter app I trigger the account.createVerification()
-Function. As a respond I get a confirmation mail, as a user.
The URL which I would like to use, is a Firebase dynamic link, so I could redirect it to my app with the query parameters as values. My next step would be to use the updateVerification()
function within the flutter app and pass the values of the userId
and secret
query parameters of the link to confirm the verification. My expectation would be, that I that this is possible instead of creating a confirmation page.
The problem is, that it is not allowed to use an URL other than (I think) localhost
and the backend URL. I get the following error in the flutter debug console:
AppwriteException: general_argument_invalid, Invalid url: URL host must be one of : localhost, my.backend.url (400)
Other than that: I would also customize the confirmation mail with my labeling. Is that possible?
kind regards <:appwriteheart2:1073243188954935387>

to add an allowed hostname, add a platform to your project. It can be a flutter web or just a web platform.

Works like a charm. I added a web platform called Firebase Dynamic Links with the dynamic link URL and now the dynamic links are accepted 🙂 . Thanks! <:appwriteheart2:1073243188954935387>
The second question was answered here: https://discord.com/channels/564160730845151244/1074070333436481616

[SOLVED] E-Mail Verification with Firebase dynamic links
Recommended threads
- API Endpoint to Verify Password.
I have 2 use cases where i need to verify a users password outside of login, e.g. Updating user account data (such as name, or prefs, or data in a users databa...
- search collection by document ID
How to filter or search collection for a document using document ID, I can't find this item on the filter menu
- Database Migration/Sync Between Two Proj...
Overall The migration failed mainly due to conflicts with existing data (documents, attributes, collections, etc.), exceeding attribute limits, and unsupported ...
