GoogleChromeLabs
Incorrect name and description of "chromeosonly" option
Why is chromeosonly option called exactly that? Why does its name contain the word "only"?
The current description of chromeosonly option is "This flag specifies that the build will be used for Chrome OS only and prevents non-Chrome OS devices from installing the app".
I've just checked, and that is not true. I've built an APK with chromeosonly option and successfully installed it on my Android non-Chrome OS device. And it works!
Does adding the following string to AndroidManifest just marks the app as incompatible with non-Chrome OS devices only in Google Play Store?
<uses-feature android:name="org.chromium.arc" android:required="true" />
If so, what about clarifying the description that we are talking about Google Play Store?
It's more related to the Play Store than to being able to install into Android devices - when the feature is added, the Play Store will only offer to install on devices that have the org.chromium.arc feature.
@andreban I would love to create a pull request to clarify the description. 😉
@andreban @ibrahimkarahan
What about using
<uses-feature android:name="org.chromium.arc" android:required="false" />
instead of
<uses-feature android:name="org.chromium.arc" android:required="true" />
?
Is it valid (make any sense) at all? Will APK work in ChromeOS in this case? Will the Google Play Store offer to install the app on regular Android devices, not just ChromeOS devices, in this case?
<uses-feature android:name="org.chromium.arc" android:required="false" /> is redundant.
org.chromium.arc feature only exists on Chromebook devices. By declaring it as required, you're instructing Play Store to make this APK/AAB only available to devices that have org.chromium.arc feature: Chromebooks. This is exactly what --chromeosonly flag does.
If it's the required bit is false, then the package would be available to all devices.
