Testing the new Fleet KMP functionality and came a...

# fleet

[Jeff Lockhart]

Testing the new Fleet KMP functionality and came across a couple issues:
• Opening a couple projects, the Android app run configuration isn't created automatically for one of them.
• Constant high CPU usage from the fleet_backend process.

[Jacob Ras]

+1 for Android run configuration not being created

[Jeff Lockhart]

The two projects are simple example apps for my library. This project has the androidApp run configuration automatically created. This project does not, but I am able to manually define the android-app run configuration in .fleet/run.json, which works to run. And Fleet autocompletes the module and destination device as well. Both projects have an Android, iOS, and JVM desktop app module. The one that doesn't auto-generate the Android app run configuration additionally has a native CLI app module. Otherwise the two projects are quite similar.

[Jeff Lockhart]

The fleet_backend process high CPU usage seems to happen when I open both my root library project as well as the first Compose Multiplatform example project at the same time. It doesn't happen with the root library and the other example project both open. It's the root library's fleet_backend process that has the high CPU usage. But as soon as I close the Compose example project, the usage recedes. Open the Compose example project again and it spikes again.

[Yulia Nizienko]

Hi, thanks for you feedback
1. We’ll take a look. Have you try Re-Import Gradle Project?
2. FL-23155

[Jeff Lockhart]

I closed and re-opened the project in Fleet and restarted Fleet with the project still open, and this didn't make a difference with the Android app run configuration. But I just tried Goto->Actions->Import Gradle Project to re-import and the Android app run configuration is properly created afterwards.