Android Question Release mode error

[hongbii]

Hi,
I'm using B4A 6.5 beta#3
I have a question regarding the release/debug mode
my application first load the main layout

Activity.LoadLayout("Main")

when click the button, the activity load another layout

Activity.LoadLayout("Login")

and follow by some image and button adjustment

    Image_login.Width=Activity.Width
    Image_login.Height=Activity.Height/2 + 20dip
    Image_login.Top = Activity.Top
    Image_login.Left =Activity.Left
    Button_login.Top = Image_login.Height
    Button_login.Width = Activity.Width
    Button_login.Height = Activity.Height/8
    Button_login.Left =Activity.Left

There is no error occur when using debug mode,
But when come to release mode, the Error exception pop out"Object should first be initiallized(Button)"
Both image and button are initialized in the designer right?
The image shown properly without error.
But the button didn't shown when i press Continute?Yes.

Looking for solution.
Thank you.

 

[Erel]

Are you able to see logs in release mode? Can you post them?

Are you using FontAwesome or Material Icons fonts? If so then see post #12 - 13: https://www.b4x.com/android/forum/t...zed-when-using-fontawesome.73709/#post-470275

 

[hongbii]

Thank you Erel,
I upgrade the SDK version then the problem solved.
I upgrade to version 25.0.2
btw if i copy the file attach in #13: https://www.b4x.com/android/forum/t...zed-when-using-fontawesome.73709/#post-470275
into file folder, then i get this error:

B4A version: 6.50 BETA #3
Parsing code.    (0.00s)
Compiling code.    (0.06s)
Compiling layouts code.    (0.00s)
Organizing libraries.    (0.00s)
Generating R file.    (0.10s)
Compiling generated Java code.    (0.77s)
Convert byte code - optimized dex.    (1.66s)
Packaging files.    Error
..\Files\B4X_MaterialIcons.ttf: error: File is case-insensitive equivalent to: bin\extra\assets\b4x_materialicons.ttf

AAPT path: C:\Users\HongBii\AppData\Local\Android\sdk\tools\..\build-tools\25.0.2\aapt.exe
Exit code:1

 

[Erel]

That's true. The workaround only works if the build tool fails to add the files.