Our problem what we have is CORS problem on videos. We can not play video from some address and from some address we can play them. Concrete in Welt app now. We plane to create for this app our first VegaOS version. but the big problem is that we can not play most of the content videos.
For testing: Live stream video on home is geoblocked only only to Germany.
For playing videos we are using Video.js player.
We are testing it on FireTV stick and VegaOS 0.22.
Our App.tsx:
import { WebView } from “@amazon-devices/webview”;
import * as React from “react”;
import { useRef } from “react”;
import { View, StyleSheet } from “react-native”;
I prepared reduced app version which only get data and try to play video. App is on this link:
How I see the error:
Stream is from different domain then the app → in stream responce header have to be property "Access-Control-Allow-Origin: * ". It is missing and app runs in WebView → CORS Error.
Stream runs on customer server and we can not change it.
In normal WebView in React nativ exist possibility to disable it by setting “originWhitelist={[‘*’]}”, but this does not exist in KeplerWebView.
Is there any other possibility to set trusted domains?
Other solution is to use native player and do not play videos in WebView, because native player does not take care about CORS.
I checked log files by documentation, but htere was lot of files and nothing about CORS or Network error. I copied here header from one file, to help you understand which device i have.
Hi @Aishwarya,
what your environment means? For test you can run this link in WebView: WELT - 2 Step Video Chain Test We have SDK 0.22.6759 and OS 1.1 (14010110010220). And we have still CORS Issue.
Just following up - we’ve confirmed that native HLS playback in WebView is fixed in the latest build. Both your VOD URLs now work. Could you please update and let us know if this resolves the issue on your end?
Thank you for the update. To clarify - could you confirm which OS build/release you are currently testing on?
Also, when you say “remove CORS from server” - do you mean the server stops sending Access-Control-Allow-Origin headers, or that you’re disabling CORS enforcement entirely? Could you share the exact response headers from the stream server when CORS is enabled?
This will help us determine if this is a remaining WebView CORS handling issue separate from the original HLS playback fix.