Bug? Debugger exits after installing (activity not initialized)

[pixsys]

Hello, just upgraded from 3.5 to 5.8.
For some reason, i can't run the debugger anymore. I can install and run Release versions just fine, without any errors, but the debugger installs the app, goes into "waiting for ide..." and then leaves the foreground after a few seconds, out putting this log:

:null,0
java.lang.RuntimeException: Object should first be initialized (Activity).
Did you forget to call Activity.LoadLayout?

I just updated, so no starter service(or the newest additions) yet...

Sub Globals
        Dim TabHost1 As TabHost
...

Sub Activity_Create(FirstTime As Boolean)   
    Activity.LoadLayout("guihost")   
    TabHost1.AddTab("1", "splash")
    TabHost1.AddTab("2", "Layout1")
    TabHost1.AddTab("3", "Layout2")
    TabHost1.AddTab("4", "Layout3")
.....

Thanks

 

[DonManfred]

For some reason, i can't run the debugger anymore. I can install and run Release versions just fine, without any errors, but the debugger installs the app, goes into "waiting for ide..." and then leaves the foreground after a few seconds, out putting this log

when your last installation of your app is made during releasemode the app does not need the debugger.
If you compile it using debugger (it is per default the rapid debugger) you cant start you app manually. You can switch to the legacy debugger which is found in the Menu.

 

[DonManfred]

Ohh, i forgot... Did you updated your .net Framework to 4.5.1+???

 

[pixsys]

Thanks alot for the replies, the legacy debugger is indeed still working (didnt see it in the spinner so i thought it got removed entirely from the last builds)

For the .net i just checked and think i'm still on 4.0.3 .. i'll update asap and see if it solves my issue with the rapid debugger

 

[DonManfred]

check this too.
https://www.b4x.com/android/forum/threads/b4a-v5-00-has-been-released.54653/

 

[Erel]

Can you upload the project or send it to me (erel@basic4ppc.com)?

 

[pixsys]

Thanks for all the replies, i found the problem, had a

Dim MarginVisible As Int  = Activity.Width

buried somewhere in Process_Globals

Which i suppose is wrong because the debugger might not know the width of the layout at that point of execution, hence the "Did you forget to call Activity.LoadLayout?" message.

Not sure why only rapid debugger was affected thou, while release and legacy worked without problems.