Topics created by vinicius.campitelli

Those events without the complete suffix are sent before we commit the database transaction and the ones with complete are sent after we commit the transaction.

This means that the actual entities (user and user registration) don't actually exist when the first non-complete events are emitted.

Take a look at our Calling FusionAuth APIs In Webhooks guide for more details.

The Rolling Back From a Problematic Upgrade guide will walk you through the necessary steps.

We also recommend testing your upgrade in a non-production environment first and closely reviewing release notes to ensure you are aware of how the upgraded version of FusionAuth will interact with your integration.

You'll receive an error in both scenarios.

If you are using the web interface, you'll get a red message saying "Already exists".

forum-edit-user-email.png

And if you are trying to use the Update User API endpoint, you'll receive a HTTP 400 Bad Request error:

forum-edit-user-email-api.png

Even though we don't have specific SDKs for mobile apps, we do have a Flutter quickstart which uses our Dart client library.

If you want to develop natively, we recommend using AppAuth, which has iOS and Android SDKs and is maintained by the OpenId Foundation:

There's also a FusionAuth Swift Client maintained by the community.