You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ProofMode Version: 0.0.14-RC-3
Release Date: February 7th 2022
First I change the settings to Streghten media's verifiability given all the permissions
When I share an image with ProofMode apperars:
Proof found! Choose what level of proof to share
when I select Basic the error message appears:
Error: No proof exists yet, Try again in one minute
If I try again the same error appears
And with advanced nothing happens either
I have to say that with another telephone: Motorola Moto G5 (codename: cedric) works perfect with same proof mode version
thanks for this awesome work
The text was updated successfully, but these errors were encountered:
Seems like we need to get a Redmi Note! I have a much older version of that device, but will look into getting a newer one, since we can't reproduce this issue otherwise.
update: It works fine
I update to 0.0.15-RC-1 today and the behavior was the same, unable to generate proof
but
I change permissions: Restrictions on starting activities from the background -> show activities from the background on applications settings. https://share.mayfirst.org/s/2SM5N7nrNfNimm6 (screenshot)
And it works
thanks for your time
c.
Telephone Model:
Redmi Note M2101K6R
Android Version:
11
MIUI Version:
12.0.5
ProofMode Version:
0.0.14-RC-3
Release Date:
February 7th 2022
First I change the settings to Streghten media's verifiability given all the permissions
When I share an image with ProofMode apperars:
Proof found! Choose what level of proof to share
when I select Basic the error message appears:
Error: No proof exists yet, Try again in one minute
If I try again the same error appears
And with advanced nothing happens either
I have to say that with another telephone: Motorola Moto G5 (codename: cedric) works perfect with same proof mode version
thanks for this awesome work
The text was updated successfully, but these errors were encountered: