Bug Description
1. Summary
Video component fails to play videos with Apple M4V container format despite correct configuration.
App Name: RaiPlay
App Link on Amazon Appstore: N/A
Bug Severity
Select one that applies
-
Impacts operation of app
-
Blocks current development
-
Improvement suggestion
-
Issue with documentation (If selected, please share the doc link and describe the issue)
-
Other
2. Steps to Reproduce
-
Use Video component with autoplay=true and controls=false -
Set src to a video file with Apple M4V container format -
Render the component on screen -
Observe that video playback does not start
3. Observed Behavior
The Video component renders but the video content does not play. No error messages are displayed, but the video remains static without starting playback despite autoplay being enabled.
Video component is visible but playback does not initiate.
No visual feedback or error indication is provided to the user.
The component appears to load but content remains frozen.
4. Expected Behavior
The video should start playing automatically when the component mounts, given that autoplay is set to true.
Expected: Video should begin playback immediately upon component mounting
Expected: Content should be visible and playing within the 960x540 dimension container
Expected: Seamless playback experience similar to standard MP4 files
4.a Possible Root Cause & Temporary Workaround
The issue appears to be related to incompatibility between the Video component and Apple M4V container format. The player may not recognize or properly handle M4V containers.
Root Cause: Video component may lack support for Apple M4V container format
Root Cause: Codec incompatibility within M4V container
Root Cause: MIME type detection issues due to .mp4 extension vs M4V container mismatch
Temporary Workaround: Convert M4V files to standard MP4 container format
6. Environment
Please fill out the fields related to your bug below:
-
SDK Version: 0.21.4726
-
App State:
Foreground -
OS Information
NAME="OS"
OE_VERSION="4.0.0"
OS_MAJOR_VERSION="1"
OS_MINOR_VERSION="1"
RELEASE_ID="10"
OS_VERSION="1.1"
BRANCH_CODE="TV Ship"
BUILD_DESC="OS 1.1 (TV Ship/4434)"
BUILD_FINGERPRINT="4.0.163721.0(3072cab629675a74)/4434N:user-external/release-keys"
BUILD_VARIANT="user-external"
BUILD_TAGS="release-keys"
BUILD_DATE="Thu Sep 25 15:30:34 UTC 2025"
BUILD_TIMESTAMP="1758814234"
VERSION_NUMBER="1001010443450"
7. Example Code Snippet / Screenshots / Screengrabs
Video component configuration that reproduces the issue:
<Video
autoplay={true}
controls={false}
width={960}
height={540}
src={'https://creativemedia4-rai-it.akamaized.net/podcastcdn/Rai/trailer_raiplay_onlymp4/test.mp4'}
ref={ref => {
video.current = ref;
}}
/>
Playback Issues
Video playback fails specifically with Apple M4V container format. The content URL uses Akamai CDN delivery but the actual container format is M4V despite the .mp4 file extension.
Video with Apple M4V container format does not play through the Video component.
File is served via Akamai CDN with .mp4 extension but actual container is M4V.
Component renders correctly but content playback does not initiate.
Issue is specific to M4V container format - standard MP4 files work correctly.
Please share the following details in addition:
-
Player SDK:
N/A -
Player SDK Version:
N/A -
Audio Codecs:
[AAC - typical for M4V] -
Video Codecs:
[H.264 - typical for M4V] -
Manifest Types:
[Direct video file - no manifest]
Q: If applicable, please provide your media/content url
https://creativemedia4-rai-it.akamaized.net/podcastcdn/Rai/trailer_raiplay_onlymp4/test.mp4
Note: URL has .mp4 extension but actual container format is Apple M4V
Q: Are there any special headers required to reproduce the issue you are facing?
N/A - Standard HTTP delivery via Akamai CDN
Additionally please provide the following if possible
Container Format: Apple M4V (despite .mp4 URL extension)
Video Codec: H.264 (typical for M4V containers)
Audio Codec: AAC (typical for M4V containers)
File Source: Akamai CDN
Browser/Player Compatibility: Issue specific to Kepler TV Video component
Additional Context
Any Additional Context you would like to provide?
The discrepancy between the file extension (.mp4) and actual container format (M4V) may be causing format detection issues.
This could lead to the player attempting to handle the file as standard MP4 when it actually requires M4V-specific processing.
Apple M4V containers, while similar to MP4, have specific characteristics that may require different handling.
Consider implementing format detection based on actual file headers rather than file extensions.
Testing with converted MP4 files may help confirm if the issue is format-specific.