since today while switching between debug & release I get some false alarms when B4A tries to dex/copy/merge some files. Defender then blocks it. Here I have to click on "clean project" 2 or 3 times and everything is fine until I switch again. Someone else with this behaviour? (WIN11)
since today while switching between debug & release I get some false alarms when B4A tries to dex/copy/merge some files. Defender then blocks it. Here I have to click on "clean project" 2 or 3 times and everything is fine until I switch again. Someone else with this behaviour? (WIN11)
If this just started to happen for multiple people, then that indicates that your copy of defender downloaded a new list of virus signatures and one of them now matches a B4x file and is false triggering.
So, if you can configure defender to "ignore" that flag, then somehow this has to be reported to microsoft to get them to whitelist it.
since today while switching between debug & release I get some false alarms when B4A tries to dex/copy/merge some files. Defender then blocks it. Here I have to click on "clean project" 2 or 3 times and everything is fine until I switch again. Someone else with this behaviour? (WIN11)
Anything new on this? Now I can't compile at all in debug mode. The trojan file name changes as does the file in the tmp directory. This has become a major issue now as I need debug mode.
Here it's only the temp folder(s). I clicked on "accept" (I've the German version so it may be an other word) in the Defender's options and now it seems to be ok.
Is this the "Writing on the wall" for a LINUX version of B4X? ((can't imagine how Erel would achieve that port, but, then, Its Erel ... should we just wait....?)