Hi @Krishna
Welcome to Amazon Developer community!
Please fill out the bug report (below) so that we can address your issue better.
Before you continue
Before submitting a bug report, please review our troubleshooting documentation at Troubleshoot Issues | Vega Troubleshooting
If you still want to file a bug report, please make sure to fill in all the details below and provide the necessary information.
NOTE: PLEASE ONLY REPORT A SINGLE BUG USING THIS TEMPLATE.
If you’re experiencing multiple issues, please file a separate report for each.
Bug Description
1. Summary
Provide a brief description of the bug in the SDK and its impact on app functionality.
App Name:
App Link on Amazon Appstore (found through Developer Console → Actions column in App List → View on Amazon.com):
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
[List the steps for reproducing the bug]
[Any specific component or method call in React Native triggering the issue]
- …
3. Observed Behavior
Explain what actually happened, noting any discrepancies or malfunctions.
<!-- Answer here -->
4. Expected Behavior
Describe what you expected the SDK to do under normal operation.
<!-- Answer here -->
4.a Possible Root Cause & Temporary Workaround
Fill out anything you have tried. If you don’t know, N/A is acceptable
<!-- Answer here -->
5. Logs or crash report
(Please make sure to provide relevant logs as attachment)
For crash issues, please refer this guide for faster troubleshooting: Detect Where the App Crash Originates | Design and Develop Vega Apps
- App/Device Logs
- Crash Logs
- Crash Report
- For issues with Kepler Studio Extension, please share log files from below folders:
~/.vscode/extensions/amazon.kepler-extension-<version>/ExtensionLogs ~/.vscode/extensions/amazon.kepler-ui-extension-<version>/ExtensionLogs
6. Environment
Please fill out the fields related to your bug below:
- SDK Version: Output of
kepler --version
- App State:
[Foreground/Background]
- OS Information
Please ssh into the device viakepler exec vda shell
and copy the output fromcat /etc/os-release
into the answer section below. Note, if you don’t have a simulator running or device attachedkepler exec vda shell
will respond withvda: no devices/emulators found
<!-- Answer here if applicable -->
7. Example Code Snippet / Screenshots / Screengrabs
Include any relevant code or component setup in React Native that can help reproduce the bug.
import { ExampleComponent } from 'custom-sdk';
<ExampleComponent config={{ key: 'value' }} />
Playback Issues
If this is a playback issue, please provide your content URL, any pre-conditions (like geo-location), and let us know if it’s x86 or arm7.
<!-- Describe your playback issue if applicable -->
Please share the following details in addition:_
- Player SDK:
[Bitmovin, Shaka, ...]
- Player SDK Version:
[e.g. 1.23]
- Audio Codecs:
[AAC, ...]
- Video Codecs:
[h.264, mp4]
- Manifest Types:
[m3u8, dash, etc ..]
- Audio Codecs:
Q: If applicable, please provide your media/content url
If this is created dynamically, tokenized, etc please provide a way for us to access it
[N/A or Content / Media Url for testing]
Q: Are there any special headers required to reproduce the issue you are facing?
[N/A or Insert Headers]
Additionally please provide the following if possible
Provide Screenshots / Screengrabs / Logs. Please include as much information as you can that will help debug.
<!-- Answer here if applicable -->
Additional Context
Any Additional Context you would like to provide?
Add any other relevant information, such as recent updates to the SDK, dependencies, or device OS that may affect the bug.
<!-- Answer here if applicable -->
If you are getting any errors, please share those reports as well.
Warm regards,
Ivy
Hi @Krishna ,
We have not hear back from you on this post for more than a week.
We are closing this post for now.
You can respond to this post within 14 days of closure to reopen the post.
After 14 days you can create new post if you still have questions or issues.
Thanks,
Rohit