Search Issue Tracker
Third Party Issue
Votes
0
Found in
2019.4
2020.3
2020.3.25
2021.2
2022.1
2022.2
Issue ID
1398485
Regression
No
[Android] Avast reports Unity projects as a suspicious app when the project is installed
How to reproduce:
1. Install the Avast app on the device (https://play.google.com/store/apps/details?id=com.avast.android.mobilesecurity&hl=en&gl=US)
2. Create a new Unity project
3. Build And Run on the device with Avast app installed
Expected results: When the app launches after the installation Avast doesn't flag it as suspicious
Actual results: When the app launches after installation Avast will flag it as suspicious
Reproducible with: 2019.4.36f1, 2020.3.27f1, 2021.2.10f1, 2022.1.0b6, 2022.2.0a3
Reproduced with:
VLNQA00391, Xiaomi Redmi 9A (M2006C3LG), Android 10, CPU: MediaTek Helio G25 (MT6762G), GPU: PowerVR Rogue GE8320
VLNQA00335, Samsung Galaxy S20+ 5G (SM-G986B), Android 10, CPU: Exynos 990, GPU: Mali-G77
Notes:
- "AvastReg has been reported as a suspicious app. APK:CloudRep [Susp]" message is given from Avast
- Avast security is not triggered on old installed Unity apps or when relaunching an installed Unity app
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Avast flags as suspicious any usigned app that comes from unkown sources. The issue has been observed as well when installing an empty Android Studio project, hence this is not Unity related.