Menu
Sites
Language
Cannot deploy web service app to emulator

Hi guys,

I'm new to Tizen so apologies if this should be obvious.

I'm not able to deploy a web service app to a gear emulator (works fine with commercial gear device though).  Should this be possible?  

When I run and deploy the app from the IDE to the emulator VM I get the following message in the console:

start process (install)
.....
error : 42

end process (fail)
processing result : Unknown Error [42] failed
spend time for pkgcmd is [570]ms
cmd_ret:42
    An exception occurred
(Installing the package... > Fail)
An exception occurred
Unexpected stop progress...
(2.512 sec)

Installing from CLI using sdb tool yields little more information but does refer to a settings level violation so I'm wondering if the emulator supports service apps??

__return_cb req_id[40560002] pkg_type[wgt] pkgid[UdbkWv1n41] key[error] val[42] error message: setting level violate
__return_cb req_id[40560002] pkg_type[wgt] pkgid[UdbkWv1n41] key[end] val[fail]
processing result : Unknown Error [42] failed

I've provided my config.xml file below. Note that when I comment out the tizen:service element, the app deploys just fine (but obviously the service cannot be run - only the web app is functional).  I've tried setting on-boot and auto-restart to false to no avail.

Hoping you can point me in the right direction.

config.xml:

<?xml version="1.0" encoding="UTF-8"?>
<widget xmlns="http://www.w3.org/ns/widgets" xmlns:tizen="http://tizen.org/ns/widgets" id="http://yourdomain/RadarTest2" version="1.0.0" viewmodes="maximized">
    <tizen:application id="UdbkWv1n41.AppTest" package="UdbkWv1n41" required_version="2.3.2"/>
    <content src="index.html"/>
    <feature name="http://tizen.org/feature/screen.size.normal"/>
    <feature name="http://tizen.org/feature/network.internet"/>
    <feature name="http://tizen.org/feature/location.gps"/>
    <feature name="http://tizen.org/feature/web.service"/>
    <icon src="icon.png"/>
    <name>AppTest</name>
    <tizen:privilege name="http://tizen.org/privilege/download"/>
    <tizen:privilege name="http://tizen.org/privilege/location"/>
    <tizen:privilege name="http://tizen.org/privilege/internet"/>
    <tizen:privilege name="http://tizen.org/privilege/application.launch"/>
    <tizen:profile name="wearable"/>
    <tizen:service id="UdbkWv1n41.Service" on-boot="true" auto-restart="true">
        <tizen:content src="service.js"/>
        <tizen:name>Radar Service</tizen:name>
        <tizen:icon src="icon.png"/>
        <tizen:description>Service Test</tizen:description>
    </tizen:service>
    <tizen:setting background-support="disable" encryption="disable" hwkey-event="enable"/>
</widget>

~dennyp

List

Responses

6 Replies
Iqbal Hossain

What is your emulator api version ?

As your app uses 2.3.2, you should use emulator with api version 2.3.2 

-Thanks

Dennis Perisa

Hi Iqbal,

Thanks for your reply.  In my emulator manager, I only have the option to create a 2.3.2 emulator as shown below:

Confirming within the shell that emulator is running 2.3.2:

sh-3.2# cat /etc/info.ini
[Version]
Model=Wearable-Emulator;
Build=Tizen-2.3.2_Wearable-Emulator_20161216.2057;
Operator=;
[Build]
Date=2016.12.16;
Time=20:57:46;

 

Iqbal Hossain

You may miss one step. Please follow this guide carefully

http://developer.samsung.com/z/develop/getting-certificates/create

Dennis Perisa

Hi Iqbal

I have followed this guide, including the "Permit Device to Install" step but the issue persists.  When I remove the service config below, the app deploys just fine to the emulator but when I add it back in, I continue to get error 42.   I don't have this problem when deploying the app to a Gear S3.

    <tizen:service id="UdbkWv1n41.Service" on-boot="true" auto-restart="true">
        <tizen:content src="service.js"/>
        <tizen:name>TestService</tizen:name>
        <tizen:icon src="icon.png"/>
        <tizen:description>Test</tizen:description>
    </tizen:service>

 

Iqbal Hossain

Delete your previous emulator and create new one. 

Dennis Perisa

Hi Iqbal, I'm afraid this did not work either.  Are there any logs or debug methods I can use to obtain more information about error 42?  All we know so far is that it is a "setting level violation" from the sdb log.

__return_cb req_id[40560002] pkg_type[wgt] pkgid[UdbkWv1n41] key[error] val[42] error message: setting level violate
__return_cb req_id[40560002] pkg_type[wgt] pkgid[UdbkWv1n41] key[end] val[fail]
processing result : Unknown Error [42] failed