Program Resource

Resource libraries for programmers and developers

Pitfall for using uses-permission, writing manifest to increase supported devices

When creating Android app, uses-feature and uses-permission are used inside manifest, but this might cause unwanted filter-outs. In my app, I first had manifest as but since app was usable without camera, I’ve changed to as follows for request from user who wanted to use app with device  without camera. However, this didn’t list up app in Google Play. I had to write like this: Write uses-feature for camera, and add android:required=”false” parameter to clarify camera is not required. Android device with front-only camera device was also filtered in first 2 manifest code. Not only camera, location and bluetooth, which was part of function but not mandatory to app, was …