Your device isn't compatible with this version

Solar2D Android
#21

RESOLVED:

The problem of my app not displaying in the cheap Android I had was because it was a rooted device. I finally did check on a Google Nexus and it appears in their store. It does not appear in rooted Android devices because I selected to use Google’s copy protection (deprecated soon).

Is there any features in Corona sdk Android to help set up Google’s newer Application Licensing within an app?

Thanks to everyone that replied - I learned from this experience. [import]uid: 156018 topic_id: 28920 reply_id: 118732[/import]

#22

lessmsios,

Unfortunately no. Corona does not currently support Google LVL (License Verification Library). It’s on our wish-list, but not scheduled. There has been very little demand for that feature. [import]uid: 32256 topic_id: 28920 reply_id: 118747[/import]

#23

Hi, i have exactly this same issue,

Was the fix as simple as selecting ‘Off’ on google ‘Copy protection’?

Thanks, [import]uid: 125592 topic_id: 28920 reply_id: 119375[/import]

#24

@neil6:

You can turn copy protection off but anyone with a rooted device can move YOUR app to their SD drive and spread it around freely.

Perhaps Corona will support protecting their users apps made with Corona via Google’s LVL someday. Seems logical for a company to help protect their customer’s investment. [import]uid: 156018 topic_id: 28920 reply_id: 119459[/import]

#25

lessmsios,

Like I said earlier, LVL support is on our wish-list, but there hasn’t been enough demand for it to be a priority. That’s why it’s not on our current road map. But we do note every time a feature is requested on our forums, so thanks for showing interest in it. [import]uid: 32256 topic_id: 28920 reply_id: 119536[/import]

#26

lessmsios,

Like I said earlier, LVL support is on our wish-list, but there hasn’t been enough demand for it to be a priority. That’s why it’s not on our current road map. But we do note every time a feature is requested on our forums, so thanks for showing interest in it. [import]uid: 32256 topic_id: 28920 reply_id: 119536[/import]

#27

Joshua,
I hope that removing the 3 Android permissions is very high on your to do list… We would really, really needed this. Our apps do not need these permissions and there are some customers for which having these permissions is the reason for not buying our apps…

[import]uid: 7038 topic_id: 28920 reply_id: 120990[/import]

#28

+1 [import]uid: 160496 topic_id: 28920 reply_id: 121037[/import]

#29

Joshua,
I hope that removing the 3 Android permissions is very high on your to do list… We would really, really needed this. Our apps do not need these permissions and there are some customers for which having these permissions is the reason for not buying our apps…

[import]uid: 7038 topic_id: 28920 reply_id: 120990[/import]

#30

+1 [import]uid: 160496 topic_id: 28920 reply_id: 121037[/import]

#31

Joshua,
I must agree with Bohumil; we really, really need a solution to this issue (Also mentioned by Noami in #10)
Well, these 3 warnings do stop sales. Especially, for educational apps for kids and games not requiring the internet. We have showed 3 kiddies apps to parents, which I have made with CORONA, and we have asked if they would buy them. Most anwers were: NO. Why? Mostly because of the warnings. The other anwers; well, you can`t get everything right

But to me, it is not just the removal of these three “unwanted” adroid permissions that needs to be solved. To me, as developer, it is most cruicial to have control of the android manifest!!
Which I don`t have, if I use CORONA. Sorry, but that is the way it looks.
It looks like a “default” android manifest is included in the apps build by CORONA. What are the permissions in this “default” android manifest? What happens is this “default” android manifest is changed", or deleted altogether, or whatnot? Can you please publish the answers?

To me, the developer and only the deleloper, following the Android Guidelines, should have control of the android manifest. I cannot responsibly publish an app, which android manifest contains entries which I don`t know, which were made by “who knows” and which could be changed by “who knows”.

To change the APK manually, as discussed, is not the best alternative.
Permit me to make the following suggestion:
As we are putting “additonal” permissions to the android manifest via build.lua, we could put ALL required permissions in the build.lua. It should then be possible for CORONA to create the android manifest based exclusively on the enties in build.lua. After all, it`t just an XML which needs to be included in the app building, which CORONA might be doing anyway.

Benefits: The developer has control and resposibility of the android manifest as only the permissions in build.lua would be in the android manifest. No workaround, no dodgeing. Nice for CORONA :slight_smile:

Can we please, please have a workaround to get rid of the unwanted permissions quickly?
And can you please provide the anwers to my questions above and hopefully take up my suggestion, or find a better alternative.
Thank you very much for your help - we really need it here, too.

Dieter [import]uid: 185880 topic_id: 28920 reply_id: 132641[/import]

#32

Dieter,

If you need a solution to this “now”, then you can use the Enterprise version of Corona. With that version, you have complete control of your app because you would be developing with the Android SDK and Corona is just a library (ie: a JAR file you include in your Android project).

For Corona Simulator builds, you’ll have to wait. It’s in our queue to remove these permissions, but we have other commitments that must be completed first. Tasks that other customers have been waiting much longer for. As I have stated in other threads, there is more to this than simply removing these default permissions because they will cause crashes when using certain features and the logged error message comes across as an OpenGL exception instead of permission error. This causes confusion and would make it a tech-support nightmare for both the Corona developer and our tech-support staff. What we need to do is spend a week putting all of the permission checks in our code, log more meaningful/helpful permission errors, update our API documentation to indicate which APIs require INTERNET, READ_PHONE_STATE, and NETWORK_STATE permissions, and update our sample projects to include these permissions as well. That’s the proper way for us to handle it and we’re unmoving on doing it any other way. [import]uid: 32256 topic_id: 28920 reply_id: 132777[/import]

#33

Joshua,
I must agree with Bohumil; we really, really need a solution to this issue (Also mentioned by Noami in #10)
Well, these 3 warnings do stop sales. Especially, for educational apps for kids and games not requiring the internet. We have showed 3 kiddies apps to parents, which I have made with CORONA, and we have asked if they would buy them. Most anwers were: NO. Why? Mostly because of the warnings. The other anwers; well, you can`t get everything right

But to me, it is not just the removal of these three “unwanted” adroid permissions that needs to be solved. To me, as developer, it is most cruicial to have control of the android manifest!!
Which I don`t have, if I use CORONA. Sorry, but that is the way it looks.
It looks like a “default” android manifest is included in the apps build by CORONA. What are the permissions in this “default” android manifest? What happens is this “default” android manifest is changed", or deleted altogether, or whatnot? Can you please publish the answers?

To me, the developer and only the deleloper, following the Android Guidelines, should have control of the android manifest. I cannot responsibly publish an app, which android manifest contains entries which I don`t know, which were made by “who knows” and which could be changed by “who knows”.

To change the APK manually, as discussed, is not the best alternative.
Permit me to make the following suggestion:
As we are putting “additonal” permissions to the android manifest via build.lua, we could put ALL required permissions in the build.lua. It should then be possible for CORONA to create the android manifest based exclusively on the enties in build.lua. After all, it`t just an XML which needs to be included in the app building, which CORONA might be doing anyway.

Benefits: The developer has control and resposibility of the android manifest as only the permissions in build.lua would be in the android manifest. No workaround, no dodgeing. Nice for CORONA :slight_smile:

Can we please, please have a workaround to get rid of the unwanted permissions quickly?
And can you please provide the anwers to my questions above and hopefully take up my suggestion, or find a better alternative.
Thank you very much for your help - we really need it here, too.

Dieter [import]uid: 185880 topic_id: 28920 reply_id: 132641[/import]

#34

Joshua,
thanks for the quick answer and for having the issue in the pipeline. Sorry, with NOW I didnt mean "drop everthing" else. Its on your desk and I`m quite happy with that:-)
Dieter [import]uid: 185880 topic_id: 28920 reply_id: 132916[/import]

#35

Dieter,

If you need a solution to this “now”, then you can use the Enterprise version of Corona. With that version, you have complete control of your app because you would be developing with the Android SDK and Corona is just a library (ie: a JAR file you include in your Android project).

For Corona Simulator builds, you’ll have to wait. It’s in our queue to remove these permissions, but we have other commitments that must be completed first. Tasks that other customers have been waiting much longer for. As I have stated in other threads, there is more to this than simply removing these default permissions because they will cause crashes when using certain features and the logged error message comes across as an OpenGL exception instead of permission error. This causes confusion and would make it a tech-support nightmare for both the Corona developer and our tech-support staff. What we need to do is spend a week putting all of the permission checks in our code, log more meaningful/helpful permission errors, update our API documentation to indicate which APIs require INTERNET, READ_PHONE_STATE, and NETWORK_STATE permissions, and update our sample projects to include these permissions as well. That’s the proper way for us to handle it and we’re unmoving on doing it any other way. [import]uid: 32256 topic_id: 28920 reply_id: 132777[/import]

#36

Thanks for understanding. We’re always super busy on Android and our large list of changes on our release notes is proof of that. Notice that there are more changes for Android than any other platform.
http://developer.coronalabs.com/content/corona-sdk-release-notes-build-2012-971

We’re trying our best to keep up with the many requests/demands sent to us, and now that we’re able to grow the Corona team as noted in recent blog articles, we should hopefully be able to fulfill these requests faster. [import]uid: 32256 topic_id: 28920 reply_id: 132963[/import]

#37

Joshua,
thanks for the quick answer and for having the issue in the pipeline. Sorry, with NOW I didnt mean "drop everthing" else. Its on your desk and I`m quite happy with that:-)
Dieter [import]uid: 185880 topic_id: 28920 reply_id: 132916[/import]

#38

Thanks for understanding. We’re always super busy on Android and our large list of changes on our release notes is proof of that. Notice that there are more changes for Android than any other platform.
http://developer.coronalabs.com/content/corona-sdk-release-notes-build-2012-971

We’re trying our best to keep up with the many requests/demands sent to us, and now that we’re able to grow the Corona team as noted in recent blog articles, we should hopefully be able to fulfill these requests faster. [import]uid: 32256 topic_id: 28920 reply_id: 132963[/import]