AllyAndroid Member Licensed User Longtime User Dec 10, 2014 #1 My Anti-Virus software just flagged one of my B4A class modules as a Trojan and tried to delete it. Has anyone else experienced something like this?
My Anti-Virus software just flagged one of my B4A class modules as a Trojan and tried to delete it. Has anyone else experienced something like this?
AllyAndroid Member Licensed User Longtime User Dec 10, 2014 #3 What concerns me is when I upload it to Google Play. I wouldn't want to lose my account over a flashlight app that blinks Morse code. Upvote 0
What concerns me is when I upload it to Google Play. I wouldn't want to lose my account over a flashlight app that blinks Morse code.
AllyAndroid Member Licensed User Longtime User Dec 10, 2014 #4 This is interesting. It only does it when I try to run Debug (Rapid). If I use Debug (Legacy) or either Release, my Anti-Virus doesn't complain. Upvote 0
This is interesting. It only does it when I try to run Debug (Rapid). If I use Debug (Legacy) or either Release, my Anti-Virus doesn't complain.
Kevin Well-Known Member Licensed User Longtime User Dec 10, 2014 #5 I believe when using the rapid debugger, your "code" gets executed on the pc and only a "shell" app runs on the Android device. This may explain why your A/V software only complains when rapid debugging, but I don't know what is in the code that it doesn't like. Upvote 0
I believe when using the rapid debugger, your "code" gets executed on the pc and only a "shell" app runs on the Android device. This may explain why your A/V software only complains when rapid debugging, but I don't know what is in the code that it doesn't like.
Erel B4X founder Staff member Licensed User Longtime User Dec 10, 2014 #6 This is of course a false positive. It will not affect in any way the compiled APK file as it happens from the "rapid engine" that runs on the PC (in debug mode only). Upvote 0
This is of course a false positive. It will not affect in any way the compiled APK file as it happens from the "rapid engine" that runs on the PC (in debug mode only).
AllyAndroid Member Licensed User Longtime User Dec 10, 2014 #7 Kevin said: I believe when using the rapid debugger, your "code" gets executed on the pc and only a "shell" app runs on the Android device. This may explain why your A/V software only complains when rapid debugging, but I don't know what is in the code that it doesn't like. Click to expand... I was converting letters into a string of 0's and 1's. It didn't like that. I now convert them into a string of a's and b's and it quit complaining. Upvote 0
Kevin said: I believe when using the rapid debugger, your "code" gets executed on the pc and only a "shell" app runs on the Android device. This may explain why your A/V software only complains when rapid debugging, but I don't know what is in the code that it doesn't like. Click to expand... I was converting letters into a string of 0's and 1's. It didn't like that. I now convert them into a string of a's and b's and it quit complaining.