-
Notifications
You must be signed in to change notification settings - Fork 2
Description
Description
Problem
When using the FusionAuth Swift SDK, I'm encountering an issue where the AuthorizationManager appears to persist configuration from a previous FusionAuth instance, specifically the base URL. This occurs when attempting to log in to a new FusionAuth instance (with a different URL) after having used a different one previously.
Solution
If dispose is not intended to clear all state, or if a more granular control is desired, a new public method like clearState() or resetConfiguration() could be added to the AuthorizationManager. This method would provide developers with a explicit way to force a reset of the SDK's internal configuration without needing to dispose and re-initialize the entire manager.
Alternatives/workarounds
Reset the emulator/app
Additional context
This issue arises in scenarios where applications need to authenticate users against different FusionAuth instances, rather than just different tenants or applications within a single instance.
The same issue was originally opened in the Android SDK, FusionAuth/fusionauth-android-sdk#219
Additional context
No response