Other B4A v3.82 is released!

[Erel]

B4A v3.82 is now available for download. All customers who received v3.80 can download this update. It is available from the same link as the previous download (you will also receive an email with this link).

New features and improvements:

• Support for Android L (preview version).
• Support for the files structure of latest Android SDK.
  
• Sender keyword - correctly manages events from multiple threads.
• Optimized dexer supports Java 7 classes. This is required in order to compile apps with the latest Google Play Services version.
• Rapid debugger - several bug fixes and improvements to error reports.

 

[padvou]

Thank you very much!

 

[westingenieria]

Thanks Erel

 

[BPak]

I installed 3.82 and it will not compile an app..

Gives following error.

checked config path and it is correct?

Parsing code. 0.06
Compiling code. 0.17
Compiling layouts code. 0.00
Generating R file. 0.03
Compiling generated Java code. 0.66
Convert byte code - optimized dex. 0.39
Packaging files. 0.11
Copying libraries resources 0.00
Signing package file (debug key). 0.31
ZipAlign file. Error
Cannot find:
Please configure paths (Tools - Configure Paths).

EDIT: Think the reason is ZipAlign is not in the Tools folder of C:\Android.
I was updating the Platforms and cancelled one. Maybe that caused it to be deleted and not updated. Will try update again.

EDIT: Works Ok now. Installed BuildTools 20 and found the ZipAlign in this directory and B4A works with it there.
C:\Android\build-tools\20.0.0

 

[alexwekell]

I was able to compile and update my app to work on Android L (no fancy animations though), but I can't change my version code. It stays at whatever I last released it at and is preventing me from uploading an updated version of my app. The B4A source shows that the version number is different, but google play keeps throwing an error no matter what I change it to:

UPLOAD NEW APK TO PRODUCTION

Upload failed
You need to use a different version code for your APK because you already have one with version code 14.

Upload another APK
By publishing this application you confirm that it complies with the Developer Program Policies, including the developer ads policy. Your application may be subject to United States export laws and you confirm that you have complied with all such laws. Learn more

 

[Erel]

Please start a new thread for this issue.

 

[bitstra]

I was able to compile and update my app to work on Android L (no fancy animations though), but I can't change my version code. It stays at whatever I last released it at and is preventing me from uploading an updated version of my app. The B4A source shows that the version number is different, but google play keeps throwing an error no matter what I change it to:

UPLOAD NEW APK TO PRODUCTION

Upload failed
You need to use a different version code for your APK because you already have one with version code 14.

Upload another APK
By publishing this application you confirm that it complies with the Developer Program Policies, including the developer ads policy. Your application may be subject to United States export laws and you confirm that you have complied with all such laws. Learn more

THIS IS NOT b4A related!

I had that too some weeks ago when uploading an Eclipse-Java-Project...

I've solved that in this way:

deactivated the aktive apk (in your case ver code 14) in google play;

activated the older apk (in your case ver code 13 or less);

uploaded the new one apk (in your case ver 15 or higher);

for me the "Upload failed" Msg was gone and the newest ver. was activated...


regards

bitstra


SORRY FOR STAYING OT!

 

[Hans- Joachim Krahe]

...thanks, Erel

 

[tdocs2]

Greetings.

Thank you in advance for answering my question.

I upgraded B4A to v3.82. I upgraded to Version 20 L and Android SDK tools to rev 23 using SDK Manager (had to run as Administrator).

I changed the configure paths to:

C:\Program Files (x86)\Java\jdk1.7.0_51\bin\javac.exe

C:\Program Files (x86)\Android\android-sdk\platforms\android-L\android.jar


I get the following error:

Parsing code.                          0.02
Compiling code.                        0.02
   
ObfuscatorMap.txt file created in Objects folder.
Compiling layouts code.                0.00
Generating R file.                      0.03
Compiling generated Java code.          0.34
Convert byte code - optimized dex.      0.20
Packaging files.                        0.14
Copying libraries resources            0.00
Signing package file (private key)      0.26
ZipAlign file.                          Error
Cannot find:
Please configure paths (Tools - Configure Paths).

How do I solve it?

Thank you.

 

[tdocs2]

Greetings.

Thank you in advance for answering my question.

I upgraded B4A to v3.82. I upgraded to Version 20 L and Android SDK tools to rev 23 using SDK Manager (had to run as Administrator).

I changed the configure paths to:

C:\Program Files (x86)\Java\jdk1.7.0_51\bin\javac.exe

C:\Program Files (x86)\Android\android-sdk\platforms\android-L\android.jar


I get the following error:

Parsing code.                          0.02
Compiling code.                        0.02
  
ObfuscatorMap.txt file created in Objects folder.
Compiling layouts code.                0.00
Generating R file.                      0.03
Compiling generated Java code.          0.34
Convert byte code - optimized dex.      0.20
Packaging files.                        0.14
Copying libraries resources            0.00
Signing package file (private key)      0.26
ZipAlign file.                          Error
Cannot find:
Please configure paths (Tools - Configure Paths).

How do I solve it?

Thank you.

I tried the following:

Deleted the android sdk folder.
Downloaded sdk.
It took me thru several gyrations: did not show android L, then had to run as administrator.
It finally installed and B4A 3.82 is running fine.

Hope this helps someone else.

Best regards.

 

[NJDude]

It is not recommended to install the SDK on protected directories such as Program Files or Program Files (x86), this is to avoid issues with permissions.

 

[roncoa]

The menu "Project/Package Name" return me the "Build configurations" menu ..... is it a bug?

 

[NJDude]

The menu "Project/Package Name" return me the "Build configurations" menu ..... is it a bug?

No, that's a new feature.

 

[roncoa]

No, that's a new feature.

I have not found how to change the package name.
The two menu : "Project/Package Name" and "Build configurations" return me the same menu.

 

[NJDude]

On the same screen. look here:

 

[rproberto]

Sorry for the English ...
Thanks to all the staff for this excellent compiler that also urges us to improve our app with all of its updates are very close!
What you can not ask for more!

 

[Euxaes]

Thank you for this update!

 

[Guardian17]

B4A v3.82 is now available for download. All customers who received v3.80 can download this update.

I currently have Version 3.00 installed. You indicate that customers who received v3.80 can download this update. Can v3.82 be installed directly over v3.00, or do I need to install v3.80 first?

 

[Erel]

No need to install v3.80. You can directly install the latest version (from any version).

 

[namnach]

Dear Erel,

Your work and effort are priceless.
Thank you for your time and dedication to Basic4Android.
Your service is unbeatable!

Thank you very much!

 

[jjmairena]

genial hermano ......................