If the new version does not have a mechanism to recover the token from the old version (how to store it in the internal memory to read later) and you made the update available to all users, I believe that it will no longer be possible to solve efficiently. If the new release is in beta stage and/or you have how to submit a new update with the old version, I suggest encrypting the session data in the old version, persist them in the internal storage and read them in the new version.
UPDATING
Step by step, summarized:
- Store the existing token in the app that will be discontinued: it can be in txt, as explained in this answer;
- Read the token in the new app: explained in this answer. If you are using Expo, you will need of this method here.
This should be sufficient for the first run of the app after the update. Now you must persist the token "in the domain" of the new app (the same way you would if there was no old app). My suggestion is to use the library Redux-persist.
It was not clear to me if the loss of the "session" happens in the migration only or is a problem of the new architecture. So: the user needs to reload how many times after updating the app?
– Mathias Berwig
the loss of session happens on migration, because I do not have access to the user token to authenticate it after it updates the app
– Andre Bordignon