You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently using the AppleAuth.NET library to handle Apple authentication for both a web application and a mobile app. However, I have encountered an issue when trying to manage multiple Apple clients simultaneously (i.e., using different configurations for web and mobile).
The AppleAuthProvider class in the library uses static fields to store the Apple client configuration, such as ClientID, TeamID, KeyID, and RedirectURL. This design causes the configuration to be shared across all instances of AppleAuthProvider, making it impossible to use different configurations for web and mobile in the same application.
The text was updated successfully, but these errors were encountered:
Hi!
Thanks for the feedback.
I guess you can easily cope with this with creating two different (or as many as you need) instances of the provider class and use the specific instance for authenticating either for mobile or web.
I am currently using the AppleAuth.NET library to handle Apple authentication for both a web application and a mobile app. However, I have encountered an issue when trying to manage multiple Apple clients simultaneously (i.e., using different configurations for web and mobile).
The AppleAuthProvider class in the library uses static fields to store the Apple client configuration, such as ClientID, TeamID, KeyID, and RedirectURL. This design causes the configuration to be shared across all instances of AppleAuthProvider, making it impossible to use different configurations for web and mobile in the same application.
The text was updated successfully, but these errors were encountered: