Android Question Unable to compile

It appears this has been asked before. Hope this helps. <- click here

Make sure that there isn't any huge file in the Files folder.

No huge files, just a simple program like the one in my original post. I've copied zipalign.exe to android/tools.

After I've removed 64 bits Java JDK and installed the 32 bit, it seemed a bit better.

I've used B4A the whole morning, although packaging took ~10 seconds. It is much slower than the version I was using before: V2.70.

15 minutes ago, the time-out error in the ZIP Align reappeared.

How can I overcome this? Can I send you some logs for analysis? This basically makes my B4A installation useless.

Please provide me your support. It's very frustrating why is compiling a simple program so slow, when in the version I was using before it was quick.

B4A v5 compilation is not slower than previous versions. The problem is somewhere else.

It is also not related to the Java version as it happens during the ZipAlign step which is an Android SDK tool.

What is the size of the generated APK file?

Thanks for the quick feedback Erel.

Just two examples:
WebViewSettingsDemo_RAPID_DEBUG.apk 182KB
=> Small changes to the demo included in the WebViewSettings library
Test4_RAPID_DEBUG.apk 156KB
=> Presents a simple toast message

It takes about 30-40s to compile and send the app to B4A-bridge.

BTW, I'm using now a Windows 10 laptop, if that makes a difference.

Thanks

Is the ZipAlign the slow step?

Try to reinstall Android SDK in a different folder and make sure that B4A uses the new installation (Tools - Configure Paths).

Packaging files and ZipAlign are the slowest steps.

=> For a hello world app
B4A version: 5.20
Parsing code. (0.00s)
Compiling code. (0.14s)
Compiling layouts code. (0.01s)
Generating R file. (0.56s)
Compiling debugger engine code. (0.92s)
Compiling generated Java code. (0.87s)
Convert byte code - optimized dex. (0.33s)
Packaging files. (11.21s)
Copying libraries resources (0.01s)
Signing package file (debug key). (0.37s)
ZipAlign file. (32.83s)
Installing file to device. (4.44s)
Installing with B4A-Bridge.
Completed successfully.

Is the duration of these steps normal (11 and 32 seconds)? I had to increase the process timeout value otherwise it would not compile.

I've reinstalled Android SDK to a different directory. This time I've used R24.3.4 instead of R23.0.2. I've not copied zipalign.exe to android/tools.

Right now is working again. Let me use it a bit more and then I'll send feedback.

Thanks

DDC said:

Is the duration of these steps normal

Click to expand...

No.

Normal values for a small project:

B4A version: 5.20
Parsing code. (0.01s)
Compiling code. (0.06s)
Compiling layouts code. (0.01s)
Generating R file. (0.03s)
Compiling debugger engine code. (0.61s)
Compiling generated Java code. (0.69s)
Convert byte code - optimized dex. (0.42s)
Packaging files. (0.09s)
Copying libraries resources (0.00s)
Signing package file (debug key). (0.32s)
ZipAlign file. (0.01s)
Installing file to device.

I believe I've found the problem: McAfee LifeSafe Real-Time Scanning! After disabling this feature, the compilation duration was inline to the values you've posted.

Unfortunately, I cannot configure McAfee to exclude folders and sub-folders. Only individual files can be excluded.
https://community.mcafee.com/thread/76428

Does anyone uses McAfee and has a similar problem?

Thank you

can't you add wildcard based exclusions?

like

*/objects/*
*.apk
*.dex

I'm afraid, no

weird, their enterprise solutions have that but the home user one not.