Sketchware-Pro / Sketchware-Pro

Sketchware Pro's sources in Java. Now anyone can contribute to Sketchware Pro.
https://sketchware.pro
Other
863 stars 254 forks source link

Play protect error #705

Closed subhash16 closed 1 year ago

subhash16 commented 1 year ago

Screenshot_2023-01-12-11-59-56-151_com android vending

subhash16 commented 1 year ago

Screenshot_2023-01-12-17-19-01-079_com miui global packageinstaller

subhash16 commented 1 year ago

This error occurs when build a project then RUN the project.

BeChris100 commented 1 year ago

So I'm not the only one here.

JavkhlanK commented 1 year ago

Looks like Play Protect started reporting apps signed with testkey as unsafe too, just like some Chinese OEMs' virus scanners sometime ago. I wonder why, as being signed with testkey doesn't necessarily have to mean the app's unsafe.

As the label says, this isn't really Sketchware Pro's fault.

subhash16 commented 1 year ago

How to fix this

JavkhlanK commented 1 year ago

Try exporting your project as unsigned APK, then signing that file with e.g. apk-signer or MT Manager. Play Protect shouldn't report it as "unsafe" then.

JavkhlanK commented 1 year ago

I'll try "appealing" to Play Protect using an APK that gets flagged by it. Let's see what they say.

subhash16 commented 1 year ago

I have to upload on play store

subhash16 commented 1 year ago

I got this error from today

subhash16 commented 1 year ago

I have uninstalled the skpro deleted sketchware file on storage then reinstall not solved

JavkhlanK commented 1 year ago

Doing that won't change anything. The APK is being generated normally, it's just that Play Protect started finding APKs built when you press the Run button harmful now.

When publishing to Google Play you should be safe, as .aab files shouldn't get signed with testkey and you'd be using your own key store anyway.

subhash16 commented 1 year ago

Doing that won't change anything. The APK is being generated normally, it's just that Play Protect started finding APKs built when you press the Run button harmful now.

When publishing to Google Play you should be safe, as .aab files shouldn't get signed with testkey and you'd be using your own key store anyway.

I use my own key

JorgeViais commented 1 year ago

I also have an error in my app, I try to "Sign an APK" using "Sign using testekey" or create a key in "Create Release Keystore", the app runs in the "signed_apk" folder but it appears with a ". APK" and when I try opening it pops up an error "There was a problem parsing the package". I also tried "Don't sign" and the result is the same. I ask for your help. Thanks.

EmStudio22 commented 1 year ago

Why is have Trojan Screenshot_20230114_190017_com android chrome

JavkhlanK commented 1 year ago

Looks like Play Protect started reporting apps signed with testkey as unsafe too, just like some Chinese OEMs' virus scanners sometime ago. I wonder why, as being signed with testkey doesn't necessarily have to mean the app's unsafe.

As the label says, this isn't really Sketchware Pro's fault.

@EmStudio22

subhash16 commented 1 year ago

Play protect stop detecting as virus. But still miui security avast detecting Trojans.

JavkhlanK commented 1 year ago

Nice! Not sure how to address that Xiaomi one though

subhash16 commented 1 year ago

Google play solved

JavkhlanK commented 10 months ago

Update: I created a (hopefully) helpful guide for fixing that issue at #901.