[Issue] The Accept-Language request HTTP header cannot be set on webOS TV 5.0.
Currently, on webOS TV 5.0, the Accept-Language request HTTP header cannot be set by your app. Even if your app sets the Accept-Language request header to a certain language tag, the actual header that is sent will be the language tag of the system language setting. Thus, we recommend that you do not use the Accept-Language request header on webOS TV 5.0 and handle the language and locale in an alternative way.
[Simulator] Simulator is not launched with the CLI command on Linux.
If an error occurs when you try to launch your app on the Simulator with the CLI command, ares-launch -s, on Linux, uncapitalize the last part of the file name of the Simulator's AppImage file (AppImage to appimage) and try again.
How to solve the problem if CORS (Cross-Origin Resource Sharing) occurs when App uses Ajax XmlHttpRequest?
webOS TV follows the CORS (Cross-Origin Resource Sharing) standard. We only provide the method to control the access in the server. Find out more about CORS on the http://enable-cors.org/ You can refer to the following sites or other Google sites. https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS http://software.dzhuvinov.com/cors-filter.html http://stackoverflow.com/questions/4952838/servers-that-supports-cors In case of JSP Add the following at the JSP code of the service part. Access-Control-Allow-Origin: allow domain Access-Control-Allow-Methods: POST, GET, OPTIONS Access-Control-Allow-Headers: Content-Type, Accept, x-requested-with Access-Control-Max-Age: 1728000 As a result, jsp code should look like this: response.setHeader("Access-Control-Allow-Origin", "*"); response.setHeader("Access-Control-Allow-Methods", "POST, GET, OPTIONS"); response.setHeader("Access-Control-Allow-Headers", "Content-Type, Accept, x-requested-with"); response.setHeader("Access-Control-Max-Age", "1728000"); Apache Server Open httpd.conf file under the conf folder at Apache server. Modify "#LoadModule headers_module modules/mod_headers.so" into "LoadModule headers_module modules/mod_headers.so". Add the following at the end. Header set Access-Control-Allow-Origin "*" “*” means that access from any website is allowed. To allow a specific website only, use the form like "www.anysite.com". To avoid cross domain issue, try using JSONP.
Deletion of all member information and posts
If you cancel your membership, all your member information other than listed below will be deleted. Records of complaints and dispute resolutions: Will be kept for 3 years. However, all the posts you’ve made in the Forums will not be automatically deleted by cancelling your membership. If you’d like your Forum posts to be removed, please delete them before you cancel your membership.
I cannot launch the emulator on my Mac. How can I resolve this issue?
The emulator is not available on ARM-based Macs because VirtualBox is not supported.
[webOS Service] Do I need any library when calling webOS services?
Yes, you need webOSTV.js that is needed to be included in your app when calling webOS services. You can download the webOS library file from this website. Refer to the following article. JS Service Usage
[App Submission] Where can I download the updated self checklist template for App QA?
Go to the App Self Checklist page and download the app self checklist file, which is used for app submission. Required Documents for Application Submission to LG Seller Lounge has been updated. Self-Checklist UX-Scenario Apps submitted for app QA accompanied by the previous version of the self-checklist will NOT be approved. Please make sure to download and use the updated version to avoid delays. The file is also provided at LG Seller Lounge site.
[debugging] Web Inspector not working on Chrome v80
You will encounter the following issue while using the Web Inspector to debug your app on Chrome v80. ISSUE A blank page opens instead of Web Inspector, and the following message appears. "Uncaught TypeError: document.registerElement is not a function" CAUSE The document.registerElement property has been deprecated on Chrome. SOLUTION Install the IDE to use the bundle browser on the webOS TV SDK. On the webOS TV SDK 5.0, you can use Chromium v68 as the bundle browser. Web Inspector using CLI Web Inspector using IDE TEMPORARY SOLUTION Use Chrome v68 listed below. Chrome v68 (Windows) Chrome v68 (macOS) Chrome v68 (Linux 32bit) Chrome v68 (Linux 64bit)
[Audio] I hear no sound when I play content on webOS TV 5.0
webOS TV 5.0 supports the AudioTrack API that mutes and unmutes an audio track. If your app does not play a sound while your content is playing, you should check whether to set the AudioTrack API correctly. If you set the enabled property of the API to false, the audio is muted. To play the selected audio track, you MUST set the enabled property to true. The following example shows how to set the property to true. var video = document.getElementById("video"); video.audioTracks.enabled = true; You can check the value of the enabled property on the browser console as below. > video.audioTracks.enabled < true For more information and examples about the AudioTrack API, refer to the MDN documentation below. https://developer.mozilla.org/en-US/docs/Web/API/AudioTrack
[Security] Termination of GlobalSigns R1 certificate.
There has been an announcement from GlobalSign certificate authority regarding R1 deprecation and migration scheme to R3 and R5. https://support.globalsign.com/customer/portal/articles/2970034-globalsign-ssl-products-intermediate-and-root-changes This means that the R1 certificate will be no longer issued when it comes to be renewed after 27th. May 2019 instead it will be replaced with R3 and R5. We had compatibility concern with old legacy smart TVs when R1 has been replaced by R3 or R5 therefore deduced simulation test with the following results. Case 1. R1 replaced with R3 We had the best result and no compatibility issues in this case Case 2. R1 replaced with R5 Some old legacy Netcast models have compatibility issues but okay with entire webOS TVs. Alternatively, some partners configure their server by combining between R3 and R5 certificate as below and we have no compatibility issue in this scenario. Case 3. R3 combine with R5 Server configuration – When the device supports ECDSA cipher suite, it refers to R5 otherwise R3. In summary, if your server has the R1 certificate from GlobalSign and about to renew then please consider LG’s stance. We prefer Case 1 and alternative Case 3 rather than Case 2. We appreciate your cooperation in advance and directly contact firstname.lastname@example.org if you have any other technical inquiries.