Is there a possibility the debugger hasn’t been attached yet? You should see a checkmark (or `X`) on...

# android

[kingsley]

Is there a possibility the debugger hasn’t been attached yet? You should see a checkmark (or X) on that red dot if everything is indeed setup properly

[Erfan]

In the image the debugger the app was not running. But even when I run it with the debugger attached (all other breakpoints work as expected) doesn't stop on any line in this observable block. (although it's Log.d does log it in the console)

[Kurt29]

I think the debugger has still problems with lambdas

[Kurt29]

@Erfan Can you try to make 2 logs after each other there, and set breakpoints at both lines, and see what happens?

[Erfan]

@Kurt29 No difference

[rkeazor]

Put the breakpoint in the line above ,and see if you can step down

[rkeazor]

if you can’t , this either your debugger isn’t attached to the right device(or at all) , or your code isn’t reaching it

[rkeazor]

Where are you actually resetting the variable?

[Erfan]

@rkeazor As I said I can get the debugger to work any where outside of these observable blocks. So the debugger is attached.

(I can put a breakpoint in call site of the setter and with step into get into the block, but the problem is that the breakpoint inside the block doesn't work)

and the logs are printing to console.

[drofwarcs]

I've seen similar behavior if proguard was set on debug builds or when testing with instant run enabled.

[droidrcc]

AS still has problem with debug lambda and kotlin. Give them time to fix.

[droidrcc]

I would say try the same code in IntelliJ, if it works open a bug on AS, if not works on IntelliJ neither, open a bug there too.