Jacob Neterer

@chilipeppr It sounds like the config of TinyG then, because movements have consistent incorrect behavior. @Quas7 I would consider the possibility of wiring being mixed up, however the original builder...

@chilipeppr being that the config of TinyG is wrong, do you know of any resources I could reference to fix it? Or a place I could get some help?

May have answered my own question here: https://capacitorjs.com/docs/guides/storage. > "...your app needs to expect that the data will be lost eventually. This is because the OS will reclaim local storage...

@j-berman Looking for your thoughts here. For [Capacitor](https://capacitorjs.com/) applications that use Userbase, local storage is not a long-term data storage solution, as the data can get cleared and session lost....

@j-berman wow, for some reason I wasn't aware of the Cordova plugin, or I forgot about it! I may be able to use the Cordova plugin in place of the...

@j-berman would be curious if you're using the Cordova plugin and if you've had session issues? I suppose it could have to do with my implementation, maybe a race condition...

I've just come to realize this is only an issue on iOS. I just picked up an old Android phone for testing, opened the app, and my session from months...

@j-berman Can you explain why `expirationDate` behaves this way? When I sign in, my `userbaseCurrentSession` has a value of: ```json { "username": "jneterer", "signedIn": true, "sessionId": "...", "creationDate": "2022-12-09T05:21:46.989Z", "expirationDate":...

Maybe it is! The only thing that makes me think it may not be, is this isn't an issue on Android. I just opened the app up a test device...

@j-berman Results from two tests on iOS: 1. **Don't set** `sessionLength` on `init`. Result - open more than 24 hours after sign in, **logged out**. 2. **Set** `sessionLength` on `init`...