You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here are some cases where FIDs could be deleted or rotated:
Uninstallation or reinstallation of the app, for instance when an end user installs on a new device.
The end user clears the cache of the app or the device.
FID deletion is triggered in the backend due to app inactivity (currently the threshold for this is 270 days of inactivity).
We use FID as the base of database encrypted key by its lifecycle (only if user reaches three cases above). But in reality, our daily active user still may face to FID rotate unexpectedly, thus database decryption failed.
For a daily active user, is there any other reason causing FID rotation?
I face this issue as well after updating app through Google Play. Just use our app normally a hours ago.
The text was updated successfully, but these errors were encountered:
According from Document:
We use FID as the base of database encrypted key by its lifecycle (only if user reaches three cases above). But in reality, our daily active user still may face to FID rotate unexpectedly, thus database decryption failed.
For a daily active user, is there any other reason causing FID rotation?
I face this issue as well after updating app through Google Play. Just use our app normally a hours ago.
The text was updated successfully, but these errors were encountered: