Dealing With A Change in appDetails

[dominic-ks]

Presently, the SDK will store the appDetails provided in the localStorage. This could be a problem if you subsequently want to change the details provided, e.g. the callback function, as those changes will be ignored in favour of the stored details.

There should be some way of invalidating the cached details if new details are detected and this may also require a complete scrapping of stored auth credentials requiring a user to sign in again.