语言

Menu
Sites
Language
Cannot deploy Tizen application over the Tizen RD-PQ test device

Hi,

I am trying to deploy he notification sample from the tizen official website on the Tizen RD-PQ test device, but unfortunately i got the following error:

 

I search for an answer and I found that I shoudl remove the privileges from my config.xml, but I wander is it logic to delete the privileges from the config.xml file when it were included on the sample?

PS: the version of my device is 2.2.1

列表

响应

4 回复
daniel kim

Hi,

Actually you need to resolve this issue if you need the privilege instead of removing it.

I think that the removal of privilege is a kind of workaround to run the sample application simply.

 

In my case, I got the Privilege level violation error while HRM application is running in the Gear2 after I've added these privileges.

    <tizen:privilege name="http://developer.samsung.com/privilege/healthinfo"/>
     <tizen:privilege name="http://developer.samsung.com/privilege/medicalinfo"/>
 

This problem was solved by creating a new device-profile.xml which has Partner level in Wearable SDK 1.0.0.

I wish this will help you.

karray gargouri

Hi,

Thank you for your reply, but I am not using the wearable SDK, and I have created a new security profile (because I didn't figure out how to create a new device-profile.xml.... I guess it is only for the Tizen wearable IDE).

Thanks
 

Alex Dem

Hi,
It is not clear what Web example and what sdk version do you use...
Here you could check what privilege level  is required for appropriate web api (Tizen  mobile).
https://developer.tizen.org/dev-guide/2.3.0/org.tizen.mobile.web.device.apireference/tizen/privlevel.html or the same for 2.2.1 sdk:
https://developer.tizen.org/dev-guide/2.2.1/org.tizen.web.device.apireference/tizen/privlevel.html
Alexey.

Alex Dem

Hi,
just fyi: I was able to deploy Web Notifications example from 2.3.0 Win 64 (and 2.2.1 Win 32) SDKs onto 2.3.0  (Kiran) device and onto 2.2.0 RD-PQ (M0) device. On (2.2.1) M1 device I have observed some issues (unable to deploy due config.xml, app-control section).
Alexey.