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
I tried to install version 2.1 from F-Droid and a dialog appeared saying it was blocked by Play Protect. Play Protect does not recognize the developer. It offers to stop the installation or to install anyway. I stopped it.
I have installed lots of applications from F-Droid without ever seeing this problem.
In https://gitlab.com/fdroid/fdroiddata/-/blob/master/metadata/com.tananaev.passportreader.yml I see:
MaintainerNotes: masterList is a bundle of x509 certificates the scanner otherwise
blocks
Maybe the error is related.
The text was updated successfully, but these errors were encountered:
Hi,
I also noticed this problem, however I don't think it has anything to do with the masterList file. We had to add this in the metadata because by default F-Droid doesn't allow any binary file in the APK, but Play Protect shouldn't care about this, and in the Play Store version we don't have this problem, even if the APK is the same except for the signature.
It is also probably unrelated, but I left the dialog on and forgot about it. Several minutes later (more than 20), the phone did a partial restart (it didn't ask for the SIM PIN). When I unlocked the phone, the icon of e-Passport Reader appeared on the launcher. It seems that Play Protect doesn't work for long. Strange.
I tried to install version 2.1 from F-Droid and a dialog appeared saying it was blocked by Play Protect. Play Protect does not recognize the developer. It offers to stop the installation or to install anyway. I stopped it.
I have installed lots of applications from F-Droid without ever seeing this problem.
In https://gitlab.com/fdroid/fdroiddata/-/blob/master/metadata/com.tananaev.passportreader.yml I see:
MaintainerNotes: masterList is a bundle of x509 certificates the scanner otherwise
blocks
Maybe the error is related.
The text was updated successfully, but these errors were encountered: