Thanks a lot. I have been using evaluate expression before, and that is one of the coolest tool. I learnt a lot, can't wait to use them for my next debugging session.
1:08 This game should be the easter egg on Android 11 ! 11:53 About drop frame, could be nice that instead of going to what called the function, we could drag the current execution line to anywhere in the code (or at least in the current function). I think it was possible on Java for PC, no? They also talk about "time machine". Could be nice to have a debug-only function (in both code and in the IDE) that saves the current state, so that we could re-reach it. 16:50 An even more efficient solution to reach a "heavy" breakpoint would be to run the app normally, and make it switch to debug on the breakpoint, using `Debug.waitForDebugger()` .
Can you just keep the view of the IDE the presenter is working with? We don't need to see the room. Meanwhile we are missing parts where he points to a button and we have to guess which button he was referring to...
Google pay the audience to applaud and “Wooooooo!!!” at the end of every sentence. The more you cheer the more $$$ and useless Alphabet swag they Chuck at ya
I've been using Android Studio for ages, and I didn't know half the tips here. And now I do! Super useful!
Me too, kudos for that filter option on logging.
This is amazing, didn't know most of those!
“Click this icon over here”...camera doesn’t show it.
Attach Debugger button which is next to Run and Debug buttons
Thanks a lot. I have been using evaluate expression before, and that is one of the coolest tool. I learnt a lot, can't wait to use them for my next debugging session.
Excellent. So many ways to reduce the noise of the debugger that I didn't know existed.
This is amazing, I haven’t known most of those. Thank you ☺️
1:08 This game should be the easter egg on Android 11 !
11:53 About drop frame, could be nice that instead of going to what called the function, we could drag the current execution line to anywhere in the code (or at least in the current function). I think it was possible on Java for PC, no?
They also talk about "time machine". Could be nice to have a debug-only function (in both code and in the IDE) that saves the current state, so that we could re-reach it.
16:50 An even more efficient solution to reach a "heavy" breakpoint would be to run the app normally, and make it switch to debug on the breakpoint, using `Debug.waitForDebugger()` .
Me applauding to the screen
Amazing video, thanks for sharing such useful debugging tips
it's really cool tips. Thank you!
Whata super improvement! Now I like the android studio more than just crying to the bugs lol
Fantastic tips, thanks guys!
Thank you very much, well done!
Very nice presentation, thank's guys!
Analyzing stacktrace is great. Also Drop frame could be very useful when applying changes.
Not seeing any extra links in the description
What a criminally underrated song
Can you just keep the view of the IDE the presenter is working with? We don't need to see the room. Meanwhile we are missing parts where he points to a button and we have to guess which button he was referring to...
Very useful tips tks
We want loh data of getters in Android Studio, only adding this feature will improve the debugger very much
Thank you so much.
Guys, could you please open source this game?)
@@davidhermanyt hey man, nice presentation!
Would love to see the open-source here!
Stupid to not film the ide at all times, some things were not shown because they film the guy talking.
Google pay the audience to applaud and “Wooooooo!!!” at the end of every sentence. The more you cheer the more $$$ and useless Alphabet swag they Chuck at ya
intellij is so horrible, would love to use visual studio
This is too complicated it should've been like lkg std.
All I have to say is AS sucks
Worst IDE, thanks to intelliJ for making android coding and testing easier
IntelliJ and Android Studio are almost the same thing. What's so bad about AS?
they are basically the same, both garbage compared to vs