Calling stop immediately after calling start doesn’t deregister the device nor stop the device from being registered! The device will be registered and will receive notifications.
Calling stop immediately after start invalidates the state of the SDK. Therefore, other method calls like setUserID cannot be called afterward.
Calling stop later, after the registration is already done, will deregister the device.
Calling start() after calling stop() (immediately or later) does not bring the SDK to a valid state anymore and it does not register the device.
Therefore calling setUserID will never work anymore and throws an error because start() doesn’t bring the SDK to a started state.
Issues:
This PR solves these behaviors.