Android Question the debug mode of b4a is very instable

[shugeyi]

the rapid debug mode of b4a is very instable ,before version 5.8 i use the old debug mode ,but now the old debug mode has been delete .the rapid debug mode sometimes success sometimes fail in same code. can you recovery the old debug mode?

 

[Mahares]

but now the old debug mode has been delete

No it was not removed from 5.8. It was simply moved. To get to it:
1. In the IDE, select 'Tools'
2. Select 'IDE options'
3. Put a check mark in 'Use legacy debugger'

 

[Erel]

What happens when it doesn't work? Do you get any error?

 

[b4auser1]

What happens when it doesn't work? Do you get any error?

The same problem. F.e. debugger doesn't stop on breakpoints. My impression that instablity raises with the growth of code. For small apps I believe you will not encounter many problems with debugger.

 

[Erel]

I'm looking for reproducible examples. If possible please send me the project to [email protected] with the breakpoints placements so I can test it.

 

[JakeBullet70]

I too have these issues but my app is huge. They do not always happen and honestly I use the legacy debugger 99% of the time as it seems more stable. Also It happens in both the emulator and on a real device using USB. But the point being it is not consistent.

Sometimes I have to compile 3 or 4 times before everything starts running. (Even when cleaning the project first) I have found that when this starts happening it helps to uninstall the app first.

Erel, If if can get it to break all the time I will send you the project. I do not envy any programmer chasing a bug like this.

Release mode works 100% of the time.

 

[JTmartins]

I also have some problems with a big project. 90% of times I cant compile if there are breakpoints set, and I need to clear breakpoints then clean project, and eventualy it will run properly. With old debugger I normally dont run into any problems...but i prefer the fast debugger as the information is more organized.

 

[JakeBullet70]

Ok, this is what happened 5 minutes ago.

Fresh start of b4a. Debugging in rapid mode. All is good.

1. received an error and b4a stopped at the offending line.
2. Fixed line and restarted. App failed to deploy, error below.
3. Tried to run a few more times and same error.
4. Cleaned project and and tried to run. Same error.
5. Restarted b4a, same error.
6. Switched to legacy debugger and my project ran.

I know this is not allot to go on but it really has no rhyme nor reason to the failures as they are so random.

 

[Erel]

This error means that there was a problem during the assets file transfer. You can disable the virtual assets feature with this line:
#DebuggerForceStandardAssets: true

This is an optional feature of the rapid debugger that allows changing the asset files without a full compilation.

 

[shugeyi]

thanks Mahares, i have find the legacy debugger