Closed mastermobin closed 3 years ago
We have not seen any reports like this before. Any idea how to reproduce the issue? The log definitely points to CARTO SDK but the parts it refers have not changed in years.
It may be related to the NDK version that I used to build CartoDB Mobile SDK. Is there any preferences about NDK version? I don't remember the NDK version that I used, all I know is that it was higher than minimum requirement.
I used NDK 20.1.5948944 in order to build CartoDB Mobile SDK (using Gradle 6.7.1), is there any problems with it?
Our latest releases use NDK 21, but I do not think that the issue is caused by an older NDK. If you build your own version of the SDK, remember to re-generate proxies/wrappers using 'swigpp-java' after updating the code and before running 'build-android' script. If the wrappers and SDK native parts are out of sync, then strange errors like the one above may happen.
Tracing the crash, I found the reason in SwigDirector_TileDataSource::swig_connect_director
. There is a race condition in SWIG code, so my app which is using multiple threads for initializing the tile data sources leads to a native crash because of this race condition.
Afterwards, I found a related issue to my problem in Swig repository, which is solved and closed. Updating some of swig files may be helpful.
Thank you :D
I've fixed this issue in swig by changing java.cxx
and director.swg
which is embedded in CartoDB::mobile-sdk based on suggested changes by main swig repository.
I will submit a PR about it.
Thanks for tracking this down! No need for PR, I have fixed it locally already, will push the changes tomorrow.
Thanks a lot :D
Hi
Recently, I see many crashes with the title of "abort" on Google Play Console just on android 10. you can see a part of backtrace below:
How should I overcome this spreading issue?
Thank you