KMZ loads fine, onFeatureClick callback sometimes brings null features

[dkati]

Summary

Loading KMZ works perfectly but onFeatureClick callback, sometimes brings null property.

same kmz with same feature all the time, sometimes it says that property is null.

actually,

if (!feature.hasProperties()){
                        Log.e(TAG,"no properties.");
                    }

triggers

Environment details

1. Device (ARM based)
2. android 8.1
3. com.google.maps.android:android-maps-utils:1.3.3

Steps to reproduce

seems kinda random.thats why i cant debug it

Code example

  mLayerListener = new GeoJsonLayer.GeoJsonOnFeatureClickListener() {
            @Override
            public void onFeatureClick(Feature feature) {
               Log.e(TAG,feature.getProperty("description");
            }
 }
 mLayer = new KmlLayer(getMap(), *a file stream*, baseActivity);
 mLayer.addLayerToMap();
 mLayer.setOnFeatureClickListener(mLayerListener);

[arriolac]

Are you able to share the .kmz file to help us repro this?

[dkati]

https://drive.google.com/file/d/1Yiyn0U2ztmUt0BAm-jN-Qph6ysqWskDn/view?usp=drivesdk

[dkati]

In order to reproduce, load it, check the feature, clear the map, remount kml, recheck feature.

Repeat

[dkati]

i also implemented an asynctask for rendering (constructor) and it has the same result...

randomly i get no property
(Caching issue?)

[arriolac]

Confirmed that I'm able to reproduce this issue. Digging into it 🔍

[arriolac]

Seems like the issue is that the KMLLayer does not deterministically add KMLFeatures in the same order. Since your KMZ file contains overlapping polygons, this presents as an issue wherein tapping on the same region clicks different polygons (depending on which polygon was added last in an overlapping region). You can validate this by checking out the KML demo in the demo app on my branch chris/fix/742.

[dkati]

Any ideas? Imma also build library from scratch in order to find something

[arriolac]

Do you have control over the KMZ file? Easiest workaround is to make sure there are no overlapping layers. Otherwise, the solution would be to ensure that KML parsing and adding layers to the map should be deterministic in order for the same file.

[dkati]

good evening and sorry for the delayed answer.

No i do not have control over the kml. Sorry