MapCompose 2

[Nohus]

The first issue is that creating a map and not adding any layer results in a crash:

java.lang.IllegalStateException: Compose Runtime internal error. Unexpected or incorrect use of the Compose internal runtime API (Start/end imbalance). Please report to Google or use https://goo.gle/compose-feedback

The stacktrace contains no app code and no library code, it's a crash of Compose. The library shouldn't crash when there are no layers, just display nothing.

[p-lr]

I've fixed it, along with the gesture break in my last two commits on v2.

[Nohus]

Thanks, can confirm it's fixed.

[p-lr]

As you can see, I'm currently fixing issues in v2 branch only. However, I'll backport some fixes to master right before publishing the last version of 1.x.x branch.

[p-lr]

I'm currently facing another issue which is kind of a blocker for me. v2 is based on Compose 1.1.0 beta04, and we're sometimes hitting this bug using the markers API. I may have to revert to using Compose stable for v2.
To be able to continue developments in my app, I had to manually downgrade v2 to use Compose stable and Kotlin 1.5.31 (also revert the TileStreamProvider to non suspend). I haven't committed anything, hoping that will be fixed in 1.1.0-beta05.

[Nohus]

Looks like the bug you refer to was fixed yesterday, maybe it's worth just waiting for the next release of Compose with the release of v2?

[p-lr]

I hope so, yes.

[p-lr]

If everything goes well after you test init-values, I'll release 2.0.0-beta02 using Compose 1.1.0-rc1 which was released yesterday.

[Nohus]

I see it got released, great!

[p-lr]

As you can see, I've changed my user name for p-lr. This is something I wanted to do for a while. You might have to update your local git remote (in the unlikely but possible event that someone picks my old username).