Google Play says that my apk uses two native platforms (my libraries) and therefore supports 0 devices

Question

When I publish .apk on Google Play, it says: 0 devices are supported. And at the bottom of the apk description it says: Native Platforms: actionbarsherlock, SherlockNavigatorDrawer. These are the libraries that I used for my project. They are not .jars, they are folders that I insert into the libs folder of the application. The problem is this: Google Play treats these two libraries as “Native Platforms” (I'm not sure what this exactly means or is), and this causes filtering in device support. I think about what might be causing this. My project is a collaboration with a friend, and the project was launched and built several times using eclipse and exported to Aide (Aide is an application that allows you to develop applications with your tablet). Maybe this is just a "path" problem or ...? I have libraries in my Aide lib folder, and I built apk there, but maybe some path or something else about libraries remained that eclipse (maybe in eclipse we did not put the libraries in the libs folder).

Answer 1

I managed to find a solution, and I would like to help all the developers who use Aide. When a library depends on another, for example, SherlockNavigationDrawer and actionbarsherlock, do not put it in the libs folder of another, but refer to it from an external folder. The same with projects and libraries: do not put the library (for example, ABS, for example) in the libs folder of the project, but leave it in an external folder and write a link to it, write the project.properties file of the project. Currently, more than 3900 devices are supported. Hope this helps :-)