Hi!
I'm having some customers complaining about the maps not loading after updating to the latest version of our app. (It's an Expo react-native app with a custom implementation for Android and iOS)
The only changes we've done is updating
com.esri.arcgisruntime:arcgis-android:100.15.6to
com.esri.arcgisruntime:arcgis-android:100.15.7
This only happens on the customers maps, which have a lot of data and moving stuff, but works great on my smaller test map.
In development I see this error:
ArcGIS Map Error: Unable to create instance of class com.esri.arcgisruntime.internal.io.b.
Registering an InstanceCreator or a TypeAdapter for this type, or adding a no-args constructor may fix this problem
I can't find anything related to this issue, maybe anyone of you have some idea on whats going on?
Solved! Go to Solution.
We have released a fix with 100.15.8.
@ChristopheVan_Baalen - can you check the gson dependency your app is using. The ArcGIS Runtime SDK for Android 100.15.7 depends on gson 2.9.0. If your application depends on a newer version of gson, this might be the cause of this issue.
I tested adding a specific implementation dependency for gson (implementation 'com.google.code.gson:gson:2.9.0') to our custom ArcGIS wrapper for our expo/react-native app, but with no success. Still the same issue.
Some more information:
The error pops up twice: Once in Portal.addDoneLoadingListener when it’s LoadStatus.FAILED_TO_LOAD, but also for the ArcGISMap.addDoneLoadingListener with the same load status.
I created a simple test app for reproducing this issue:
https://github.com/chichoch/arcgis-bug
Thank you! We are investigating and will get back asap...
@ChristopheVan_Baalen We have identified the issue as a bug in 100.15.7. We are working on a fix and will release another patch soon. Thank you for providing the repro case and apologies for any inconvenience.
Thank you!
Please keep me updated on the release.
@ChristopheVan_Baalen - we have a fix which is currently going through certification. We are targeting a patch release on December 10th.
We have released a fix with 100.15.8.