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
If I call the following code more than once in a single process, using different developer tokens, the SharedSession continues to use the developer token that was supplied first.
Calling AuthenticateToEvernote() without checking IsAuthenticated makes no difference. ENSession continues to connect to the first users account.
I've had a skim through the code and it appears that it is intentionally a singleton whose state cannot be changed once it is initialised. The only way I can find to get around this without restarting the process is to use reflection to manually reset the internal state. Obviously this is not an appropriate solution.
The text was updated successfully, but these errors were encountered:
If I call the following code more than once in a single process, using different developer tokens, the SharedSession continues to use the developer token that was supplied first.
Calling AuthenticateToEvernote() without checking IsAuthenticated makes no difference. ENSession continues to connect to the first users account.
I've had a skim through the code and it appears that it is intentionally a singleton whose state cannot be changed once it is initialised. The only way I can find to get around this without restarting the process is to use reflection to manually reset the internal state. Obviously this is not an appropriate solution.
The text was updated successfully, but these errors were encountered: