Skip to content
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

Open
franconob opened this issue Apr 8, 2021 · 4 comments
Open

Unable to unlock after coming back from background #8

franconob opened this issue Apr 8, 2021 · 4 comments

Comments

@franconob
Copy link

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!

@franconob franconob changed the title Unable to unlock when service is on background Unable to unlock after coming back from background Apr 8, 2021
@jakov-clay
Copy link
Collaborator

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.
Is it possible for you to try with a different device?
Does scanning work if you initialise SDK again after coming from background?

@jakov-clay
Copy link
Collaborator

@franconob any updates on this? still have problem?

@robvolk
Copy link

robvolk commented May 17, 2021

Hi @jakov-clay, thanks for following up. We've implemented reloadKeys() and are waiting to hear back from our client. No news is potentially good news, and I'll keep you updated.

@robvolk
Copy link

robvolk commented May 17, 2021

@rodrigovive has taken over development on this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants