On Ios updating a app build with the mobile sdk is losing the user session information and user need to logon on again after every update.
Is there a way to save the user session information?
Where is the user information stored on the device ?
For what I know there are some folders of the private app filesystem, for example the folder Application Support Directory, which are not deleted during app updates.
Thanks for posting the question on the community.
Just to give you a high level overview of how Mobile SDK works, here are few things.
1. Mobile SDK is utilizing Keychain Services for iOS, and Keystore and Account Manager for Android to persist, and manage all credentials which are provided by Apple, and Google for the most secure storage solution in Mobile Operation Systems.
2. For upgrading scenario, if the application was not uninstalled, and re-installed, the SDK will persist the credentials upon upgrading the application by design. When it was removed from the device, and reinstalled, the credentials may get wiped out.
3. If you are using iOS SDK version below 1.6.00, then was upgraded to the version above 1.6, you may experience re-login enforcement from Mobile SDK due to the change that we have made in 1.6 to improve device registration process.
So, from my understanding, the only situation where you will experience re-login upon reinstallation is when you were using the SDK version below 1.6, then upgraded to above 1.6.
Just for us to help you better, if you could please provide us information about your environment, such as SDK version, MAG/OTK version, that would help us to investigate and identify the root cause of the problem.
the issue arises upon a app updating, without uninstalling it. Both the old app and the new app are using SDK 1.6.10.The MAG version: 4.1
Is there any further information on their testing environment?
What you have described is not the expected behaviour of SDK if the SDK was used properly.
Please let me know further details, and please feel free to escalate through Support if you think that it needs to be handled through Support or as escalation.
Client found that the problem with lost user session information was caused by Fabric.
Using TestFlight is working fine .
Thanks for getting back to us with the update.
It's good to hear that the issue has been resolved; however, it is not what we were expecting.
From the engineering perspective, Mobile SDK should not be impacted by third-party library especially those popular SDKs that are widely being used by other developers.
We will still investigate the issue further from our perspective, but in the meantime, if you could provide us bit more information about what the customer's findings were, that would be appreciated.
Just wanted to double check, was the problem caused as part of distribution process with Fabric on customer's end?
or is it more generic problem with both products?