-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
ProofMode crashes consistently when generating proof #91
Comments
I don't understand how you are getting a null pointer there... |
One clue is that the primary shareProof method isn't working, and it is falling back to "shareProofClassic" secondary approach. |
I did not experience this issue. Sharing a photo from my gallery, I was able to generate a robust proof and then share it with Signal. No crashing or issues. Samsung Galaxy A50, Android 11, Proofmode 0.0.14-RC-3 |
I am on Related question. Why does my phone consistently fail
|
Thanks @benhylau . I was looking at a different branch of code, so had my line numbers off. Definitely shouldn't be null, and glad we can make a quick fix. As for what shareProof fails... I'll add some more debugging so we can make it more important exactly what is failing. It could be related to some kind of post-processing of the photo (HDR, exif injection), it could be related to where it is storing the file (external vs internal), or the inability to persist the proof hash data. |
(Also another reason to convert all this code to Kotlin asap) |
New release for testing: https://github.com/guardianproject/proofmode/releases/tag/0.0.15-BETA-1 Resolves this. |
…ms vs file paths - whenever possible use URIs, only access via filepaths in order to get extra metadata
I am getting this whenever I try to generate a proof by going to Gallery, then sharing a photo to ProofMode and selecting
SHARE ROBUST
. My phone is a Nokia 6.1 running Android 10. The version of ProofMode is just downloaded fresh from Play store.Choosing
SHARE BASIC
also does not work. I cannot generate a proof in any way.The text was updated successfully, but these errors were encountered: