-
Notifications
You must be signed in to change notification settings - Fork 1
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
Unable to unlock after coming back from background #8
Comments
Hi @franconob , we did not experience those problems. Inside constructor we load private keys from keychain. Opening process starts when you call openDoor and scanning locks should not be affected. You can maybe try calling reloadKeys() method which will reload private keys and return true if that was successful. |
@franconob any updates on this? still have problem? |
Hi @jakov-clay, thanks for following up. We've implemented |
@rodrigovive has taken over development on this issue |
Hello there. I'm having a problem trying to unlock a door and it's happening when the user moves the app to background and the app stays there for a long period of time. After the user brings the app again to foreground and tries to search for locks, nothing happens. Do I need to initialize the sdk again after some period of time when the app is in background and changes to active to be able to find locks?
Thanks!
The text was updated successfully, but these errors were encountered: