-
-
Notifications
You must be signed in to change notification settings - Fork 87
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
Latest version doesn't respect lockdown rules #347
Comments
It looks like Molly might be locking due to a crash while it's running in the background. This could explain why you're being prompted for a passphrase sooner than expected. We'll need to see the debug log to figure out what's happening. Could you please provide the debug log? It's in app's Settings > Help > Debug log |
Unfortunately I disabled the debug log some weeks ago and newest version of Molly seems to solve the issue. Hold opened this issue for one-two weeks yet, to see if this version run properly. |
@valldrac please provide me an email support contact, I send you the debug log. The issue is comeback even with 672 hours (4 weeks) pin unlock. |
|
Thanks for providing the log. I reviewed it and found an unrelated bug that might be hiding the real issue. We're fixing this in the next release. Once you've updated, please send the debug log again if the problem reoccurs. It seems Android might be killing the app, due to low memory? |
RAM or ROM, you mean? |
RAM. When the available free RAM reaches a low threshold, Android first kills background apps. |
Got it. |
Cannot you write a remember state function for the unlock? Basically when I launch the app Molly does a control like this one:
Can you store this information somewhere without compromizing security? |
Is there an existing issue for this?
Bug description
I set 720 hours automatic lockdown, but Molly (foss) ask me passphrase much time before.
Steps to reproduce
Molly version
7.8.1-2
Android version
14
Device
OnePlus CPH2399
Link to debug log
No response
The text was updated successfully, but these errors were encountered: