Hybrid app install fails with "Check spelling or remove the privilege." error

Hi,

I built a Hybrid application consisting from a Native Service and a Web Application. I’m packaging the applications together with tizen build-app CLI command.

The Web config.xml file targets the Tizen 3.0 version: required_version=“3.0”.
The Native tizen-manifest.xml file also targets the Tizen 3.0 version: api-version=“3.0”.

I specified some Native related privileges in tizen-manifest.xml file, for example:


http://tizen.org/privilege/alarm.get
http://tizen.org/privilege/alarm.set

During Hybrid packaging both Web and Native privileges are merged and the result .wgt archive contains these privileges in Web’s config.xml as follow:

<tizen:privilege name=“http://tizen.org/privilege/alarm.get”/>
<tizen:privilege name=“http://tizen.org/privilege/alarm.set”/>

The package is installed fine on Real devices and Emulators with Tizen 4.0 or above, however, it fails to install to an Emulator with Tizen 3.0 and a real device with Tizen 3.0 version with following error:
…key[error] val[-14] error message: :Check config.xml|

What I found is that these privileges are only supported by Native, and I specified them to Native manifest file, however, during the Hybrid packaging, the privileges are added to the Web manifest file. I didn’t find any solution to fix this issue and I can’t remove those privileges as I will need them on Native side.

Any help is greatly appreciated!
Thanks in advance!

Hello,
Did you check this on real devices?

Hi,

The Remote Test Lab uses a real device.
I found out that the problem is with Tizen CLI that adds these privileges incorrectly to the Web config.xml manifest.
The Tizen Studio packaging doesn’t add these lines.
The hybrid packaging is broken in Tizen CLI, reached out to Techincal Support and waiting for a response from them, they said that the development team is looking into this issue.
This issue is not that hard to fix, when the manifest files are merged, those privileges from native should not be added to config.xml, but hopefully, they will fix it as soon as possible.

Thank you for reaching out!