First, some naming clarifications:
cca
is the name of the command line tool you can use to port Chrome Packaged Apps to Hybrid Mobile Apps for Android and iOS, leveraging Apache Cordova.Chrome Apps Developer Tool
is a desktop Chrome App which manages installed Chrome Packaged Apps. It is also the tool you use to load Chrome Apps for development. (alternatively, you can use thechrome://extension
url, which was the old way to do this).- There is also a
Chrome Apps Developer Tool for Mobile
which is very different than the desktop version, but is also a tool to load Chrome Apps for development.
I believe your question is: "I have a Chrome App which runs on Desktop Chrome, and it uses the "background" and "fullscreen" permissions. When I use cca
to create a port for Mobile, cca
complains that the permissions are not recognized."
Well, the good news is that all cca
apps are always "fullscreen" and "background". The warning message is just because v2 Chrome Packaged Apps don't require those permissions, and so we missed adding them to our whitelist of accepted permissions.
The warnings, in this case, are safe to ignore (though I'm not sure if there exists a fullscreen API, that likely won't work). Those warnings are useful when you require a permission we really do not support yet, say, like "bluetooth".
So I guess my question is: did you try moving on to the next step to see if it worked?
Edit: With the latest release of cca
to npm
(v 0.0.11) we should not show warnings if your app requests these permissions.