Perhaps a Studio question more-so than compose, bu...

# compose

[Bradleycorn]

Perhaps a Studio question more-so than compose, but ... has anyone else had trouble getting the debugger to attach since updating everything to latest stuff for alpha 12?

[Denis]

I have seen this problem since before alpha12. I don't understand what's the cause of it. Sometimes it works, sometimes it doesn't.

[Denis]

I think, restarting adb server helps.

[Bradleycorn]

helps, but doesn't always fix it. I've restarted everything multiple times only to have it still not work.

[Denis]

You sure you've killed all relevant processes? Sometimes I see a process that doesn't get killed until I SIGKILL it.

[Bradleycorn]

yeah

[Bradleycorn]

Anecdotally ... I think it crops up when you have a stable build of AS running, AND a Canary build running as well ...

[Denis]

Hm. Maybe. Though I have only Canary build installed. Still happens to me

[Bradleycorn]

My guess is a bug report would be closed as "Won't Fix" with a reason of, "Don't run 2 instances of Android Studio at the same time"

[Denis]

OT: why do you need to run 2 instances? Doesn't Canary provide all the stuff you need?

[Bradleycorn]

Don't really need to. Business rules I guess.
For our production app, they want everyone on the same (stable) version of AS.
To play with Compose, I need a Canary build.
So ....

[Bradleycorn]

Which also explains why I have both open.
Don't tell my boss that I pad the estimates on all my stories, so that I have plenty of time in each sprint to work on my side project, which is to rebuild our app from the ground up in compose 😁

[Bradleycorn]

that's actually a gross over-exaggeration. My company is actually really great about R&D. They are letting me put together a "hack day" once every 2-3 sprints to train up my team on compose so that we can start using it as soon as it reaches a stable build.