Android Baidu map java. Lang. unsatisfiedlinkerror

The current apps are all like the popular ones. As long as they are added, the last small app has the chat function, the sharing function, and the camera function, with the voice function ......, If it is powerful enough (or there is a ready-to-use code on the Internet), his mother almost made an operating system.

Some of these functions need to be used by third parties. This involves a third-party choice. I generally do not like the products of small companies, rather than look down on small companies, the product quality of small companies is indeed not guaranteed, and the continuity of products is not guaranteed.

Today, we added the map function to our app. It is unrealistic to use the system map (considering that there are no map applications on some machines). Finally, we decided to use Baidu map. To be honest, I have used many Baidu APIs, And the integration is relatively simple and reliable. The map API makes me miserable. I did this in full accordance with the instructions and Demos, but I always reported the following errors:

Caused by: Java. Lang. unsatisfiedlinkerror: Couldn't load vi_voslib: findlibrary returned null

I checked some instructions on the Internet and did not solve the problem. Then I went to the official website and said that it may be a confusion problem. I added obfuscation filtering and it didn't work either, is not loaded into vi_voslib, rather than obfuscation), all helpless, battle gaode map, found that the form of gaode map and Baidu map is too fucking the same, many categories of names are the same, it seems that it migrant workers' walls are dug again. However, the key of AMAP is only valid for 30 days. It seems to charge fees later. There is no way to do it. I turned to Baidu map again. The code is not dynamic and can run normally on my colleagues' mobile phones, but my cell phone won't work. I still keep the above error. I don't understand it. Later, based on the previous ndk experience, we found that. so files in libs \ armeabi and libs \ armeabi-v7a should have a copy, the specific reason seems to be to deal with different CPU models, so I put. so file in libs \ armeabi-v7a also put a copy, Nima, solved ......

If you encounter the same problem later, I want to thank you for reading this article. I still don't know why.