It's easy for an android app to get killed when the device runs out of memory, etc. When the app is brought back up (e.g. when the user taps the app launcher icon again), it creates a new observatory port. Unfortunately, it's difficult to re-establish the connection unless you know about adb logcat and adb forward. During profiling and debugging, it's all about Observatory and so when the Observatory connection dies, my profiling workflow dies.

I was doing a full flutter run --profile but that's a slow process to run if all I'm trying to do is bring back Observatory.

May I suggest we offer something like a flutter connect command that finds the running Flutter app on the device/emulator and does any port forwarding/mapping business.

That would be a YUGE time saver as we're profiling our Flutter apps.

Thanks!