Hello everybody. I'm in a weird case. I'm trying to debug some code but my debugger never stops at finally blocks, does anyone knows why? To me the finally block should be reached all the time, right?

Are you returning from your try or catch blocks?

in some lines yes, others no

there has to be a little checkmark on the BP when you're running

yes

unfortunately the debugger has never been top notch

Do you have actual code in that

finally

block? You'll need to put the breakpoint on a line having this actual code, I don't think lines where the

finally

keyword is the only code can have breakpoints (the IDE shows you a checkmark or a stop mark to tell you about it once the class is loaded)

I tried that, but when running code that stop (circle with cross line) is shown

So if you’re returning before finally it will never get executed

@Robert Menke Wrong:

finally

is always executed after the

return

expression, just before the value is actually returned.

have to ask the obvious question... you're sure you built and ran after adding that line?

@louiscad 🤦‍♂️ Oh man I never use it like that. Just had to try it out in the editor. Kind of unintuitive tbh.

seems pretty intuitive to me 😛

Yes, I did @Kris Wong. I'm doing it right now 😛

that's quite strange then

It just don't stop at the line

is that function inlined and empty?

no, it is a regular one

i'm out of ideas

I'll print a logcat message just to check if the code running. This is first time I'm through that

Look in the gutter @cucharro: there's a barred sign meaning it couldn't find the corresponding line of code deployed on the device! You can try running the app again, and make sure you don't edit the code afterwards, as this will otherwise shift the code line numbers and deployed code under debugging would be out of sync with code in IDE, putting in at risk to encounter the same issue again.

I mean it doesn’t seem intuitive to me that

finally

intercepts a return in a try block.

fun foo(): String {
        try {
            return "hello"
        }
        finally {
            return "world"
        }
    }

but I suppose it makes sense

@Robert Menke It's very useful to unregister listeners/callbacks with coroutines. Also, almost no one uses the

return

keyword in a

finally

block.

Ya I see the utility. Tbh though I’d prefer something like Go or Swift’s

defer

keyword for that.

But I just learned thanks to you it works the intuitive way:

finally

wins.