v17 ... v18

Breaking changes

Initial login state

The initial login state is now unknown (null) instead of true. This means that the SDK will not assume to be logged in.

In previous versions the SDK assumed to be logged in. This was because before version 7.1.0 authentication was done in the integration layer. And in order not to break existing integrations, the SDK assumed to be logged in. Except when deepdeskSDK.login() was called, the login state was reset to unknown (null) and updated when the login state changed.

This change will probably not break existing integrations, if you are already using deepdeskSDK.login(), deepdeskSDK.isLoggedIn() or deepdeskSDK.loginViaPopup(). If you are not using these methods, see the DeepdeskSDK reference for more information.