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
When you enable setting "require login after app returns from background", Zeus is always reconnecting to your node when you start the app. Even if the last app usage is seconds ago.
With this setting disabled, reconnect only happens if last app usage is some time ago.
Of course after some time it is reasonable to reconnect to the node instead of loading data from cache, but it shouldn't have anything to do with this setting.
Reproduce
Set PIN, enable "require login after app returns from background", leave app, open it immediately again, enter PIN.
I can see this with
LND (REST) -> Tor
LND (REST) -> Clearnet
LND (Lightning Node Connect)
Zeus version
v0.7.1
Node interface
Multiple (specified in comments)
Network
Clearnet
Device
Samsung Galaxy S20+
Device operating system
Android 13 (Kernel 4.19)
Log output
No response
The text was updated successfully, but these errors were encountered:
Tested with v0.7.3 and I still see "Zeus is connecting to your node." after I entered the PIN and it loads for a while (with Tor its obviously easy to notice).
Describe the bug
When you enable setting "require login after app returns from background", Zeus is always reconnecting to your node when you start the app. Even if the last app usage is seconds ago.
With this setting disabled, reconnect only happens if last app usage is some time ago.
Of course after some time it is reasonable to reconnect to the node instead of loading data from cache, but it shouldn't have anything to do with this setting.
Reproduce
Set PIN, enable "require login after app returns from background", leave app, open it immediately again, enter PIN.
I can see this with
Zeus version
v0.7.1
Node interface
Multiple (specified in comments)
Network
Clearnet
Device
Samsung Galaxy S20+
Device operating system
Android 13 (Kernel 4.19)
Log output
No response
The text was updated successfully, but these errors were encountered: