问题
We have application which depends on ndk library packaged as aar. Also this app builds it's own NDK code using cmake.
We upload symbols using crashlyticsUploadSymbols<Flavor> task. And when I check build/fabric/<flavor>/release/csyms there is csym files for both libraries and all our supported architectures.
Everything seems ok, but native crashes symbolicated like this. Lots info about system lines and no info about contents of libglmapview which is most interesting part of every crash.
What is our next steps? How to find why it won't unwind native stack trace?
来源：https://stackoverflow.com/questions/43474262/one-line-ndk-crashlogs-on-android