We’ve been providing a signage app since 2016, using the same distribution certificates. Can those old certificates still be used with the Tizen 6.5 and 7 signage displays? I see there’s auite some new APIs in those displays. Do they also support the old APIs, or do we need to provide separate versions of our app depending on the tizen version, utilizing available APIs in each version?
The Author Certificate tells the Samsung Store who you are so no one can try to modify your app in the store.
The Distributor Certificate tells the end device that it is safe to install your app. (It is changed to a Samsung Distributor when it is downloaded from the store)
Thanks. Should our existing SSSP certificates continue to work with Tizen 6.5 and 7 without change?
It seems the app packaging (WGT) with its sssp_config XML file remains the same, even though it’s now referred to as “App URL” rather than “URL Launcher”. Correct?
And does the Tizen 6.5 and 7 signage displays still support the older APIs, or only the newer ones? I noticed in the docs that quite a number of APIs now have new names and functions, albeit performing similar functions.
BTW, is this by any chance the same Ron L that, in an earlier life, went under the handle of MWRon? If so, congratulations to Samsung!
In Samsung signage 2023 run Tizen 7.0 need partner level certificate to run API in WEBAPIS/webapis/webapis.js. So how do get a partner level certificate to run on all Samsung signage old and new model? Current have a public certificate call is ''Samsung Enterpirse Distributor Public Signer expire day 2027/01/01
I know a little bit about Smart TV issues but very little about the Signage and Hospitality side of things. All I know is the what is in the Signage Documentation and you probably understand it better than I do. All I see is for 2022 and 2023 Models.
Thanks. It says, under question “Q2. Can I use the SSSP APIs at Tizen 6.5 devices?”:
The SSSP is supported at Tizen 6.5 but will be deprecated since Tizen 8.0. We strongly recommend to use Samsung Product APIs instead.
Does this mean that the older SSSP APIs work on Tizen 6.5? What about Tizen 7? In Tizen 8, you say they’re “deprecated”, but do they still work also in Tizen 8? If so, are those expected to go away soonish (“Tizen 9”)?
Is it possible to create a single app that will work both on older Tizen SSSP displays and modern signage displays, or do we need to develop and maintain two separate versions here?
If you don’t have the answers, where should I turn for answers here? Is there a more appropriate signage-focused forum?
Thanks for your clarificartions about “deprecated” in this context (although usually I would take it to mean “no longer recommended bus till working”).
I’ll make some tests on a recent Tizen signage display, and will ask again here if I can’t figure things out on my own. I guess there’s no specific signage display forum any more (at least not come January).
Meanwhile, perhaps you could forward this question and try to get an answer; Is it possible to create a single app that will work both on older Tizen SSSP displays and modern signage displays, or do we need to develop and maintain two separate versions?
I am faced with the same problem. Our app that have been working fine for 2-3 years on Tizen 4.0/5.0, installs but doesn’t play on Tizen 7.0 devices. Anyone know where the distribution certificate that used to be downloadable on News - Guideline to replace a new distributor certificate can be downloaded?
I got it working when I created a new certificate profile with the “Samsung” type instead of “Tizen”. I added our screen to the list of DUIDs. Then the app worked as expected. But that’s not how we have used certificates in the past for the URL Launcher. Our Tizen 4.0 certificate was created using the “Tizen” type.
However, my understanding is that DUIDs are only for internal testing, and can’t be used for distribution of apps that should work for customers regardless of display model.
Perhaps Ron or someone else can clarify this, as well as what kind of certificate we need now for normal app distribution to work with old and new signage displays alike.
Yes, exactly. I used DUIDs to rule out the possibility of something being wrong with the app itself. The fact that the app ran, leads me to believe that the problem lies with the certificates.
There are two types of certificates. Author which tells Samsung who you are and allows you to update your app. The other is the Distributor certificate and that allows you to install your app as a developer on a Samsung Device. Your distributor certificate is replaced by Samsung as distributor when it is published.
All Samsung Devices now require a Samsung (Tizen) Distributor certificate for installation. I don’t think that was the case for older TV models.
In any case the certificate is not installed it is just the key to allow the app to be installed.
Yes, after being in contact with Samsung and creating a ticket on partnerhub.samsung.com, Samsung reached out with instructions as well as a new distribution certificate which got the app running for Tizen 7.0.
However, the new certificate does not work for older Samsung models so until we find a solution, we’ll be running two apps. If anyone gets an answer on how to package the app for both new and old models, I would love to know how.
i am not able to install my tizen app on tizen 7.0 is there any changes needed for installation as i am getting unable to install please try again later i getting this message again and again
Hii
I have replaced the old distribution certificate with new one which was able to install app on tizen 7.0 and same app is working on tizen 4.0.will the app install on tizen 6.5? OR what changes should be needed