-
-
Notifications
You must be signed in to change notification settings - Fork 146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Iphone forgets previously saved connected node #1463
Comments
This could happen if you skip v0.7.4 before upgrading to v0.7.5 Or has this happened entirely while using v0.7.5? |
I believe entirely on v0.7.5. Yesterday was first day that I added node. It happened immediately after adding the node. I then re-added and it was good for about 24 hours. I'm going to attempt to reproduce a 3rd time. I do have a fair amount of technical skills, just not familiar with apple products; this is my first iphone EVER! |
Kept the configuration for 3 days and just dropped it. This time i know it wasn't due to any upgrade. I found the .ips file associated with Zeus. I can post but am trying to ensure there isn't anything in there that i don't want public. |
Switched over to iPhone for my daily driver to diagnose this. Had this happen to me day 1 with a node connected over LNC |
My theory is that the keychain is often accessed by other apps and that causes this value to not be fetched properly, which then leads to the rest of the Zeus keychain data to be cleared Line 32 in 7d281e8
|
perhaps not though. related issue: emeraldsanto/react-native-encrypted-storage#116 |
Should be partially alleviated with #1561 - but there are still some cases in which it gets triggered without hitting the |
Describe the bug
after adding a tor connected node. App works as expected but at some point forgets the saved node causing me to have to re-add the node.
Reproduce
Reproduce the bug step by step.
Zeus version
v0.7.5
Node interface
LND (REST)
Network
Tor
Device
iPhone 13
Device operating system
IOS version 16.4.1 (a)
Log output
No response
The text was updated successfully, but these errors were encountered: