-
Notifications
You must be signed in to change notification settings - Fork 15
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
Synchronous backups #166
Synchronous backups #166
Conversation
0138012
to
537c6da
Compare
fix: returning bearer in magic link code fix
537c6da
to
8829635
Compare
chore: removed default backup server details fix: removed slashauth fix: remove test code
After performing the following steps in the example app.
The following error is received:
|
Nice find thanks @coreyphillips. It was the cached bearer token from the previous wallet that just needed to be cleared here. When creating the new wallet the backup client still had the bearer token from the previous wallet and if that didn't expire it tried to use that token to restore the wrong file but couldn't decrypt it because wallet's seed changed. |
fix: return self check after error
Enables apps using react-native-ldk to securely persist node state remotely and restore it using a seed. Backups now happen synchronously in the native code instead of unreliable async RN events to trigger backups.
Clients in Swift, Kotlin, and NodeJS (for testing).
See server readme for details on setting up and how it works.
Testing:
Once server is setup update constants.ts in the example app with the server details.
Server test:
npm run test
App test: Try restore from server button in example app.