![]() ![]() Maybe this will guide me to a lead as what's causing this. I think that I will try to boot an old backup of my virtual dev machine and compile a project to see if it is affected with the problem. Let me know if you have the same result has me. Right after it gets installed Avast will check the app and you'll get the warning. ![]() Either by pushing it like you do for all your project or by compiling an APK and transfering and installing it on the device. Create a new project, save it, rename its package name and #ApplicationLabel then compile it and run in on your device. RandomCoder: Can you try this? Install Avast! if you do not have it and make sure you have the latest virus definition. I also tried to reinstall v3.00 and it is happening with that version too. I know that nothing special has changed in v4.00 and that it's not directly related to B4A. I downgraded the Android SDK Tools, Platform Tools and SDK Build-Tools and it did not make any difference. I recently updated the Android SDK Tools, Platform Tools and SDK Build-Tools to the latest version. ![]() Or maybe it is something updated in SDK manager. Otherwise, it would have detected it from old compiles. Something must be flagged in recent compiles. I reinstalled my previous version an it did not. In fact, I installed a build I did 2 weeks ago and it got flagged. I reported many compiles of different projects as false positive but nothing seems to change on Avast side. I'm delaying my app update and really see it as a problem. So that means that they will get the problem if they install a new APK version from Google Play. So even an APK is detected after installation. I also compiled an APK, then sent it to another test phone I have, that have the same Avast version, and installed it from the SD card. Even if I change the package name, it is still detected as a "Suspicious file detected - Cloud Reputation ". If you have the same error, please let me know. It's hard to get a good ratings for our apps and un-experimented users may report 1 star rating if they happen to experience this same error. I think that someone from Anywhere Software should check with Avast as to why it detects a suspicious file in B4A projects. As soon as I updated the virus definition file and tried it again, I got the warning. I tried the same test and did not receive any warning. The definition was dated 141111 instead or 150108. I'm wondering that If I update my app and distribute it to users that runs Avast that they may complains and worst start receiving bad reviews. Of course, I know there is no problem but was wondering if any of you had the same error. This is with a simple compilation (either debug or release) of a newly created, unmodified project. If I go inside Avast by selecting the notification entry, it shows « B4A Example Suspicious file detected - Cloud Reputation ». Yesterday I started to receive errors from Avast Antivirus when I compiled a project with B4A 4.0 that got installed on my device.Īvast reports "1 problem found" in its notification entry. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |