waitForBaseMap failed error causes Geoman load issues

[slakshmanan-lightbox]

Hello, We are seeing this error occasionally when geoman is initialized as new Geoman(map, options) . The problem is it's not reliably replaceable. Geoman pro v0.5.6.

Also when it happens drawing does not seem to be working correctly on the map.

We have seen this error once in our prod application in the last 2 days and about ~40 times on our stage environment in the past day which is very concerning. Any idea why this is happening? In the meantime I am doing my best to try and replicate this on a standalone smaller example to get it over to your team. Many thanks for investigating this.

[mscno]

Is this something that only started to occur in the past 2 days? Did 0.5.6 work ok before this?

Are you also seeing this in 0.6.0?

[mscno]

I think I was able to narrow it down to a race condition. I have made the initialization code more defensive, and I think I have weeded out the bugs. Feel free to reopen if this surfaces again.

[slakshmanan-lightbox]

Is this something that only started to occur in the past 2 days? Did 0.5.6 work ok before this?

Are you also seeing this in 0.6.0?

@mscno When we were in 0.3.1 it did not happen. We started seeing this when we went to 0.5.6. Then when I upgraded to 0.6.0 Friday (I also bumped maplibre-gl from 5.14.0 to 5.15.0, I started seeing

console with the error typeError:
and the error messageError: r.createBucket is not a function

That looks like a maplibre error given that they have a bunch of those methods - https://github.com/search?q=repo%3Amaplibre%2Fmaplibre-gl-js%20createBucket&type=code

when we were testing the build on stage. So I had to revert back to 0.5.6. Question is if 0.6.1 fixes this I can try it, however what's the maplibre-gl supported library version with that? Thank you.

[mscno]

Yes, this is fixed in 0.6.1. It supports ML version 5.14.0 and 5.15.0.

I havent encountered the r.createBucket is not a function errors on my end, but will try to reproduce.

[slakshmanan-lightbox]

@mscno r.createBucket - was related to our code where there were dupe layer id collisions causing this error. So please disregard. We are fixing that at our end. Please give me a few days to test 0.6.1 + 5.15.0 to confirm waitForBasemap error is gone. I will report back. After that we can close this ticket thanks

[slakshmanan-lightbox]

@mscno we had a chance to upgrade to @geoman-io/maplibre-geoman-pro": "^0.6.1" and "maplibre-gl": "^5.16.0", and still see this error after the upgrade:

[slakshmanan-lightbox]

@mscno - This error is still happening on Production for us. Any update on this?