Debug not pausing on first breakpoint

With the final 1.6, debug is still not pausing on the first breakpoint (Android 3.1). Below is a screen shot of the unfiltered log.
When I press F8 while on the yellow highlighted line, instead of single-stepping, it takes off excuting and doesn't stop on the next breakpoint. (Well, next try, it did.)

I have encountered this error before too. However v1.6 should have fixed it. Apparently the fix doesn't work on your device.
I will contact you by mail about this issue before the next update.

BTW, this only seems to happen near the start of the app. If the breakpoint comes after the app has been going for a while, debug stops on the breakpoint.

I have sent you an email with a fix for this issue. Please test it and see if it works for you.

No, it still went past the first breakpoint to the second a few lines down. Again, this only happens near the start of the app.

Hmm. I just created a test app of a few lines for a different problem and without thinking, but a breakpoint in it. Debug stopped on the breakpoint. So I guess the failure of it to stop in my big app involves something else. Of course, I know absolutely nothing about the nuts and bolts behind this, but does it mean anything that it stops on the first breakpoint in a small app and on a breakpoint deep into the code, but not early on in a very large (9000+ lines) app?

If you still have that app, which I emailed you the link for when we were looking at the "ghost panel" problem, you could set a couple of breakpoints in Activity_Create and see for yourself. If you don't still have the code, it's still at the link that I gave you.

Can you post the unfiltered log when the breakpoint is skipped?

I just tried it again on my big app and it stopped on the first line. Don't know why it didn't work last time I tried it, but it's working now. I didn't restart B4A after putting the new jar file in place; was I supposed to have? -- not that I remember restarting it since the time it didn't work, but I remember thinking that it might be needed...

nfordbscndrd said:

I didn't restart B4A after putting the new jar file in place; was I supposed to have?

Click to expand...

Yes! Or right-click and Refresh on the Libs tab. The IDE caches the library jars for efficiency and needs to be told, or restarted, if one changes.

Okay. All's well now, then. Sorry about the false report before.