Thank you, but it did not solve the problem.
I removed and a webViewer but still says 'Trojan' security problem.
Simple app with sound files.
I don't understand what's wrong.
And I need to sell it asap.
What was to solve the problem? I wrote you to check what permissions your app is using and let us know. If you do not understand something, write that you do not understand, and not that it does not solve the problem.
This is an issue of the Avast or AVG virus checker on your phone.
No. The only way to 'fix' the problem is to contact the distributer of the software on your phone and ask them to white list your app.
See the numerous threads that explain the issue
Avast and AVG use heuristic methods to determine if an app is malicious. It seems that shortly after App Inventor makes a major update, their software starts to falsely identify apps created with App Inventor as a Trojan. Read the threads...one or more indicate how other developers solved the 'problem'' by contacting the virus software maker.
Sorry, we can not help you. You must contact the virus software developer.
2 Likes
Thank you very much.
The following link provides urls to post your apk to antivirus software companies.
[ https://www.professorcad.co.uk/appinventortips#TipsAntiVirus ]
I posted my apk and it had been accepted by antivirus check (in 24 hours).
Problem solved.
Ultimamente cuando instalo un .apk en el móvil aparece un aviso de posible troyano en el fichero (antes solo salia un aviso de falta de seguridad). Igualmente si envio el fichero por email, bloquea el envio por posible virus en el fichero. Esto no me ocurria anteriormente. Hay algun riesgo en instalar el .apk?
Gracias
Jordi
Unlikely. See the advice in post #4 and scan as indicated and make the decision yourself to gain confidence in the app you made.
What virus scanner do you have on your phone?
Avast is the scanner I have. As suggested I'm snding the file to be checked to Avast.
I'll inform about results.
Thanks
It also happens to me since the last update.
- Android 9 (Xiaomi)
- No extensions.
- Tested with DefaultScope: Legacy and App.
- Simple app:
borr_vir.aia (1.5 KB)
Hello @Juan_Antonio
This is what I see when I load the apk made from your aia file on my Samsung 8.1. It is the message I always received for the past several years when installing any apk that is not sourced by the PlayStore. I have a Webroot virus checker.
I expect the message you see is generated by the built in virus checker Xiaomi supplies with their hardware which probably uses Avast. The checker is trying to protect you using heuristic methods that often fail and produce false positives.
Hopefully soon someone who has an Xiaomi and / or and Android 10 or 11 will test your simple app which compiled here fine.
I don't remember that message getting out of me in the last few months.
Maybe it's an Automatic Avast Update, (updated to 2021-09-11.)
This permission causes problems. After removing it from the manifest, Avast does not report a virus.
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE"/>
In my opinion, this is a bug in Avast.
1 Like
Correct @Patryk_F , I removed the permission using APK Editor Studio and now installs directly.
The funny thing is that a few weeks ago I installed correctly without having to change that permission.
1 Like
Yes, old apps that have this permission are not causing the problem. I changed the API target level to 29, the problem persisted. Perhaps something else is causing the problem. I have scanned the apps on this page:
https://www.virustotal.com/gui/home/upload
The strange thing is that only Avast-mobile reports the virus.
I have recieved the information from Avast that my file has been checked and included in white liste. Nevertheless the problem continues when dowlanding any apk created in App Inventor. My problem is exactly the same that Juan Antonio reports. I have a Xiaomi-Redmi 6 version MIUI 11.0.4 with Avast.
Who should solve this problem?
Great 
Only Avast. I understand someone already contacted the company to get an indication of what is causing only Avast to black list App Inventor apps. They would not discuss the issue.
On your device, you could just ignore the warning (there should be a Button) and be happy 
knowing your own apps are not causing your device harm. What you do is up to you. You might be able to disable Avast and use a different virus checker.
Also note that although it is white listed, it may take Xiaomi to access the latest Avast white list files; so if you just wait a while, the issue might self correct. 
It takes some time for device manufacturers to update built-in Anti-Virus, which is obviously not ideal but it is what it is. If you have installed Avast yourself, that might be an issue in itself, though you should be able to update it more quickly:
- Unfortunately Avast has a reputation for false positives on Android and MS Windows;
- Android devices usually have Anti-Virus built-in. If you add another Anti-Virus App, it may well trigger the built-in one to report a Trojan or vice-versa, since Anti-Virus Apps do behave like Trojans themselves, using brute force methods to scan.
If you upload your APK to Virus Total, it will run your App through a number of Anti-Virus programs. That will give a better indication as to whether there is a genuine issue but note that some Anti-Virus programs do not use their own Engine/Database, they instead pay royalties to a central lab - consequence of which is that all the programs based on the same Engine will likely give the same result.........
Thanks for that investigation. I'm not sure that some of these permissions are actively needed in most apps other than the App Inventor companion app. I've submitted a potential patch for review that will address this, but we will need to have some internal discussion and testing to determine whether it will have any adverse effects.
Only strange is that this permission was also used when AppInventor was targeting API Level 29. But Avast does not report a virus in these apps. Maybe the combination with something else causes a problem?
With pretty much every SDK update this triggers Avast and AVG. I think until they get enough reports their heuristics take a while to update. Since their heuristics seem to be particularly sensitive to this permission based on your analysis, I think it's best if we eliminate its inclusion as much as possible.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.