Tizen Web Application for B2B models-automatic update through URL Laun

Hello!

I am developing a web application for B2B model displays for retail purposes.
The devices are currently downloading the application through URL Launcher.

However, there is a problem concerning the update of the application in the devices.

Is there a way to upload the updated .wgt package to the url server and force the device to download it and install it(replace the previous .wgt). For example, lets say the new .wgt package is uploaded. Will rebooting the device(s) force it to talk to the server, see a new updated .wgt somehow and force replacement of the currently installed package application?

Furthermore, if that is possible without the need for source code implementation, is it also possible to reopen the updated now application to the state it was before updating and device rebooting occured? Such functionality would be extremelly crucial for my application.

Hello

Please login to Seller Office TV (Seller2.0) and Ask Question in the 1:1 Q&A section.

Hello
I have same question @ M.Citizen did you get anything related to this?

Hello!

Yes. The solution is to create a folder/directory on a remote server that would host the .wgt of the app as well as the sssp_config file. The latter must be a .xml file that just has the form of

<widget>
  <ver>application_version</ver>
  <size>application_size</size>
  <widgetname>application_name</widgetname>
</widget>
  • application_version must be in major.minor.patch format (for example 1.0.3)

  • widgetname must be the same as the .wgt

How this works is that lets say your currently installed version on the device has a version that is lower than the one currently on the server. Then, next time the device reboots, it will automatically update the application.

Make sure you have signed the app package with a certificate that allows installation to devices publicly. For testing reasons, you can create your own certificate through Tizen Certificate manager and add a list of Device DUIDs on which application package installation is permitted.

For general deployment, contact Samsung.

I hope this helps

@ M.Citizen
Hope you are doing well.

can you please explain in detail as of now on server i have already config file and wgt file where i replace only new .wgt file of new version
i have below config file i.e config.xml:

<?xml version="1.0" encoding="UTF-8"?> 1.32.28 32 application_name

and along with .wgt file
I have author certificate as well as samsung distribution certificate
could you please explain in brief so it will be helpful.

Hi

Along with your .wgt file, there should be an .xml file on the same directory that should be called sssp_config.xml. This file should have the exact format I provided above.

When you want to update the application on a device, then upload the new package .wgt on the server and also change the new version in the sssp_config.xml file. Version in the config.xml of the project and the attribute of the sssp_config.xml should be the same.

For example, devices have version 1.0.0 installed and you have developed version 1.0.1 of your project(the version of the project can be changed in the config.xml of the project). Then, also put 1.0.1 on of the sssp_config.xml located on the server. Now you are ready to update your devices. Updates take place automatically when a device reboots.

Hope this helps

Hi @ M.Citizen
In the xml file

<?xml version="1.0" encoding="UTF-8"?> 1.32.28 32 app name

could you please explain which version i have to changed when i upload a new .wgt file with new version
can you please provide steps for same and is this works have you tried

Hello,

In the config.xml file, you need to change the property called version, which should match the value of the ver element in the sssp_config.xml file.

This is the property you should change:
image

Once you change this version, build the package and then upload the newly generated .wgt to your server, together with the corresponding sssp_config.xml file.

Hello,
if i am not wrong the below changes i need to be done:
1 upload the new .wgt file with new version on server suppose version is 1.59
2 then in config i need to change below:

<?xml version="1.59" encoding="UTF-8"?> 1.32.28 can you please what is this ver 32 app name

could you please verify this and did you tried this ?
thanks for your support

Hi,

Do not change this
image

This is what you should change:
image
located next to the id property.

Application version is always noted as
major.minor.patch, which means it must always consist of 3 numbers separated by two . so
x.xx.xx

Hi
thanks for details
so i need to change the application version

<?xml version="1.0" encoding="UTF-8"?> 1.32.28 this one i have to change 32 app name

and the updated version of .wgt file
means we should keep ver same and same version of app
or anything else is needed?
Have you tried this does works or any other changes needed?

Just update the version I mentioned above with a new number inside the source tab of the config.xml file of the project and then make sure to change the value property inside the sssp_config.xml file also, so that those version numbers are exactly the same.

Put the newly built and generated .wgt file in the same remote(server) directory together with the sssp_config.xml file.

Of course, on the client devices then, in the App management tab, put the correct URL link representing your remote directory, so that the device knows where to download the application from(and also where to search for updated versions).

Remember! This section and topic is referring to B2B models and not Home devices. URL Launcher I mention above is a feature only found in Samsung Business models.

Best regards

hi @ M.Citizen
okay as i am using samsung professional digital signage display tizen tv.
and basically on my server there is sssp folder and in that there is config file

<?xml version="1.0" encoding="UTF-8"?> 1.32.28 so this i want to change 32 app name and .wgt file means this two things in that folder initially what i did is only i update the new version .wgt build on server so only i need to change version which is same as in .wgt build

And after doing this i need to only reboot the device not to write url in url laucher tab by myself
what my purpose is if i upload a updated build on server so it should auto download on reboot without human interfare

Please read the instructions I provided thoroughly, everything is included.

Yes, the application should update automatically if you just reboot the device.

Best regards

Hi
Thanks for the guidance

Hi @ M.Citizen
I tried this but not working i tried below changes

  1. change the version of build to 1.0.0 and also in the configuration file changed the application version to 1.0.0 in config file
<?xml version="1.0" encoding="UTF-8"?> 1.0.0 32 app name But when i reboot device it does not works? please advise what changes is needed and explain about this (Make sure you have signed the app package with a certificate that allows installation to devices publicly) but in my project i have both author and distribution certificate which i have used.

Hello @ [M.Citizen

Thank you so much for providing such a detailed solution! This is incredibly helpful and addresses exactly what I was looking for. I’ll go ahead with setting up the .wgt and sssp_config.xml file on the server as you’ve described, and I appreciate the clarification on versioning and certification requirements.

Thanks again for your support and guidance!

Hello! Sorry for disturbing, but maybe you can help me to figure out :slight_smile:
So I am using samsung hospitality tv and I have hosted both wgt and sssp_config.xml files on the remote server, and I entered a link to a wgt file in TEP Custom App’s Server url field. But i get an error that states that the application could not be installed.
What could be the reason?

Hello,

  1. There could be a variety of reasons.
    First one that comes to mind is that the application defines privileges in the config.xml file that might not be supported by the target device or the defined application’srequired_version is larger than the Tizen version of the target device.
    Make sure those two are not the case.

  2. Another possible reason is that the application is digitally signed with a distributor certificate that does not allow public distribution of the application to devices. In this case, you will need to contact samsung support.

Best regards