-
Notifications
You must be signed in to change notification settings - Fork 145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
java.lang.IllegalArgumentException: Unmanaged descriptor #414
Comments
I have the same issue and it's easy to reproduce. I have 200+ markers. By quickly tapping on the 200+ circle, map zooms in low res. Before it renders high res map and draw all markers, I navigate back to the previous screen. Within a second app crashes with the mentioned error. |
Just tested with the latest release 3.0.0 and the issue is still there. |
I found the cause of the crash in my case:
Looks like I even found a workaround:
With this I wasn't able to replicate the crash anymore. Anyway, I'm not 100% confident with this workaround. Proper fix should be that this library shouldn't try to update marker icons while it's being released. |
What is |
@Psijic it's just a var I created that I'm setting to true before navigating out of the screen. That way I can prevent recomposition of I'm going to check the source code of |
Got this crash too. |
Hi folks, The following PR might fix this issue. The Clustering was not being disposed, so probably with a large number of markers the process to deal with items in a cluster could be somehow taking longer, and by the time an item is going to be updated the map does not longer exist. I will let you know when it is merged and maybe you folks can take a look. |
Same problem, appeared when upgrading from 2.14.0 to 4.1.1. I only use markers without clustering.
|
@kikoso, hi! Has the problem been fixed in 4.3.0? |
Hi @0xffrom . The latest version (4.3.0) includes a fix that disposes of clusters, which was not happening in previous versions. If you aren't using Clustering, this is likely another issue. Could you provide another code snippet with the relevant code block? (for instance, the region where you are adding the Marker to the Map). |
@kikoso I've retested with version 4.3.0 and I wasn't able to reproduce the crash. I believe the clustering issue is now gone, thank you! |
Thanks for letting us know, @milosfec ! |
Closing this as fixed by #458 in v4.3.0. Please re-open if it recurs in v4.3.0 or later. |
Hello, I am facing this problem on version v4.3.0, when the number of markers in the cluster exceeds 100 elements
|
Hi @wangela , Firebase Analytics indicates that this issue is still happening in the newest release of our app, which uses version 4.3.0.
|
Hi everyone, I am also facing the issue with the 4.3.0
|
we need to reopen issue , if it still exists in current versions |
Any update on this? Can this ticket be reopened please? It blocks us from using the Compose map in our app. |
I'm also having the issue with a large number of markers on the screen. |
I am also facing the same issue |
Reopening this issue to further investigate it. Do you folks have any code snippet we can use to reproduce it? |
This bug wasn't solved.
Got it today. Just use a lot of markers in clustering - wait for them to start show on the map and then switch screens (navigate) before all of them became rendered.
Code:
selectedEvent
wasn't even used here. So, all markers had default view and their count was: 32632.The text was updated successfully, but these errors were encountered: