Languages

Menu
Sites
Language
Launch on Device/Emulator fails after update

Hi,

I've recently updated my Gear s2 with the latest firmware and I've also upgraded my dev machine to the 2.4 sdk rev 4. Now I've the problem that I cannot launch my apps anymore, not on the device, not on the emulator. But intrestingly if I use the emulator of the old 2.3.1 sdk it still works, also with the new emulator if I create a new app.

The error message I get is:

~error : 42

end process (fail)
processing result : Unknown Error [42] failed

 

Error Code: PRIVILEGE_LEVEL_VIOLATION

Installation failure. Some deviceCap was not accepted by ACE.

 

BTW: I've checked that all privileges are ok (well, the code and and the privilege have not even changed) and that all certificates are ok.

So what's happening and how can I resolve that issue?

 

Edited by: Philippe Wechsler on 01 Apr, 2016

Responses

8 Replies
Marco Buettner
Yeah, I have the same problem with TizenSDK 2.4 and Wearable... Maybe we should start a Issue on bugs.tizen.org ;)
Joaquim Puyo Garrido

Hello,

I think that the problem is related with the application launch privilege:

http://codedragon.tistory.com/3631

But I don't know how to solve it.

arup sarker

Hi,

Can you share the privilege list ?

AVSukhov

Hello,

Try to copy your device-profile.xml to /home/developer directory manual.

daniel kim

Hi,

I could observe such issue while launching application to emulator and could solve it by removing  <tizen:privilege name="http://tizen.org/privilege/application.launch"/> from config.xml.

Regards

 

arup sarker

Right, I am agree with kim.

Remove all un-necessary privilege. If you need  application.launch privilege, then you can use appmanager.launch instead.

 

Joaquim Puyo Garrido

Hello. Thanks for your suggestions, but the error persist.

My privilege list is:

 <tizen:privilege name="http://tizen.org/privilege/application.launch"/>

 <tizen:privilege name="http://tizen.org/privilege/filesystem.read"/>

I have opened a issue in bugs.tizen.org

 

https://bugs.tizen.org/jira/browse/TW-28

 

Joaquim Puyo Garrido

Hello, 

This problem is solved.

I have updated the SDK and I have recreated the emulator instance.

You can see here: https://bugs.tizen.org/jira/browse/TW-28