Long preview launch time

[krestyanikov]

Hello,

The launch of a preview on a local emulator takes about one and a half or two minutes, which is very long.
When I make a launch in Android Studio, it takes only 10-15 seconds

Assembly less than 1 second

Installation 2-3 seconds
Launch of the application up to 5 seconds

When I do this through ComposeFlow it takes from one and a half to 2 minutes
Search for a running emulator (it is already launched) - 1 minute

Stop and launch of the Gradle demon - 15 seconds

Assembly - 25 seconds

Installation 2-3 seconds

Launch of the application up to 5 seconds

I tried to understand why it takes much more time than Android Studio.

1. The search for the emulator takes a whole minute, although Android Studio is not looking for an emulator at all. Is it possible to remember the descriptor of an already running emulator?
2. There is some kind of problem with Gradle demons, you may need to use some other approach to starting the assembly, since there is no problem in Android Studio.
3. For some reason, the assembly itself takes 25 times more time than the same assembly in Android Studio. This is quite strange.
4. Installation and launch in time as well as Android Studio.

Is it possible to reduce the time of launching a ComposeFlow for a local emulator?

The launch of the Web previews for a very long time, this can reach up to 10 minutes. I will provide information about this later...

[thagikura]

Hi,

It turned out that gradle daemon wasn't enabled for building the app.

When I enabled it on my local environment, the time to install the Android app changed from about 20-30 seconds to less than 10 seconds.
0.7.7.2 version includes the change to enable the gradle daemon.

Can you try the version to see if the build time is reduced? Thanks.

[krestyanikov]

Hello

Search for a running emulator (it is already launched) - also 1 minute

Stop and launch of the Gradle demon - Now it doesn't end at all. I received the following message

Then I closed Composeflow, launched it again and pressed the launch of the preview. The message became so

Something wrong with the use of Gradle daemons

[krestyanikov]

Addition, I reboot my pc and the message disappeared. Perhaps it was some kind of Gradle problem. Now the assembly really has become faster, but slightly. The search for the emulator still takes about a minute, the assembly of 20 seconds

[thagikura]

Thanks. I think I figured out the root cause of why waiting for the emulator status is taking long.

0.7.7.3 includes that fix. Please let me know if the emulator issue still persists with that version.

[krestyanikov]

Hello

Now everything works wonderful. Now the emulator has been looking for a long time only when starting, then everything is very fast!

Then 2 and 3 assemblies were slightly slow because of the assembly

Then it became comparable in time with Android Studio!

Great job! Thank you!

[thagikura]

No worries, thanks for reporting it and help improving ComposeFlow!