Hi Elena,
Could you please share your Appery.io project with a href="mailto:support@appery.io" rel="nofollow"support@appery.io/a?
Are you able to install this app on devices with Android 2.3.6 (or 2.2.х) directly from Appery.io?
Hi Elena,
Could you please share your Appery.io project with a href="mailto:support@appery.io" rel="nofollow"support@appery.io/a?
Are you able to install this app on devices with Android 2.3.6 (or 2.2.х) directly from Appery.io?
Project shared.
Yes, we have installed the app on 2.3.6 Android devices directly from Appery.
Thank you!
Could you tell the project name please?
Hello, any news on this issue?
Hello!
Could you tell us your project name?
Sorry, I see project name is Fundeu. I'll update.
We reproduced this problem and were checking your manifest.xml file, but still haven't found what might cause this behavior. We'll check it more and update. Sorry for delay.
Hello!
Please check these links:
http://developer.android.com/google/p...
http://developer.android.com/guide/to...
http://developer.android.com/guide/to...
Quotation from http://developer.android.com/:
"In some cases, the permissions that you request through can affect how your application is filtered by Google Play.
If you request a hardware-related permission — CAMERA, for example — Google Play assumes that your application requires the underlying hardware feature and filters the application from devices that do not offer it.
To control filtering, always explicitly declare hardware features in elements, rather than relying on Google Play to "discover" the requirements in elements. Then, if you want to disable filtering for a particular feature, you can add a android:required="false" attribute to the declaration.
For a list of permissions that imply hardware features, see the documentation for the element" http://developer.android.com/guide/to..."