The "positive false" problem ist continued in a new thread: https://www.b4x.com/android/forum/t...g-googles-false-positive-virus-checks.147537/
The following is no longer relevant:
The goal is to share a file located on Google drive so that a recipient of the link can install the file on their Android device using package installer.
This has worked for years without any problems.
With the last uploaded version, the apk file could no longer be installed on the recipient's device.
The investigation of the cause led to the conclusion that the Obfuscator generates strings that lead to a false positive from Google's virus detection service.
(among others: https://www.b4x.com/android/forum/t...-gdrive-flagged-for-abused.123103/post-769258)
The application is very large, so manually searching for the problematic section would take a disproportionate amount of time.
Is there any way to force the obfuscator to generate other strings (e.g. by changing a seed value)?
The following is no longer relevant:
The goal is to share a file located on Google drive so that a recipient of the link can install the file on their Android device using package installer.
This has worked for years without any problems.
With the last uploaded version, the apk file could no longer be installed on the recipient's device.
The investigation of the cause led to the conclusion that the Obfuscator generates strings that lead to a false positive from Google's virus detection service.
(among others: https://www.b4x.com/android/forum/t...-gdrive-flagged-for-abused.123103/post-769258)
The application is very large, so manually searching for the problematic section would take a disproportionate amount of time.
Is there any way to force the obfuscator to generate other strings (e.g. by changing a seed value)?
Last edited: