Libs I'm using in my app:
I'm also using B4XLoadingIndicator.bas and B4XDrawer.bas. On app start I get this message:
When I see "Class not found..." message in log, app run fine.
Sometime after app is compiled and started, app crash with this info:
After closing B4A and start it again, app compile successful and run as expected, but sometimes I need to clear project multiple times or to restart B4A and compile app again multiple times to be able to run app without error: "Field Indikatorx was declared with the wrong type". It's totally random. Changing Build Configuration also sometimes trigger same error.
Also using latest CustomListView.bas (as class) instead of xCustomListView lib, trigger similar error: "Field clv was declared with the wrong type". As workaround I'm using lib, but with lib I'm not able to customize CLV as I want. I have tried to remove xCustomListView lib and change name of CustomListView.bas to CuLiv.bas and add it again in Designer as CustomView -> CuLiv, but without success, same error is triggered.
None of those problems exist in previous B4A version, only on B4A 9.00
I'm also using B4XLoadingIndicator.bas and B4XDrawer.bas. On app start I get this message:
Declaration is:Class not found: app.debug.b4xloadingindicator, trying: app.debug.myapp.b4xloadingindicator
B4X:
Private Indikatorx As B4XLoadingIndicator
Sometime after app is compiled and started, app crash with this info:
error is triggered inside B4XDrawer (line 228)Field Indikatorx was declared with the wrong type
B4X:
Public Sub getCenterPanel As B4XView
Return mCenterPanel '<- line 228 - error: Field Indikatorx was declared with the wrong type
End Sub
Also using latest CustomListView.bas (as class) instead of xCustomListView lib, trigger similar error: "Field clv was declared with the wrong type". As workaround I'm using lib, but with lib I'm not able to customize CLV as I want. I have tried to remove xCustomListView lib and change name of CustomListView.bas to CuLiv.bas and add it again in Designer as CustomView -> CuLiv, but without success, same error is triggered.
None of those problems exist in previous B4A version, only on B4A 9.00