Widget Errors
This guide helps you diagnose and resolve common errors that may occur when integrating widgets.
Most errors can be resolved by:
- Reviewing the Getting Started Guide
- Checking browser developer tools (Chrome, Firefox)
- Contacting our Support Team if issues persist
#Common Issues
#Widget Not Visible
If the widget doesn't appear on the page at all, check for these common causes:
Widgetloader Script Missing
The widget framework script isn't loaded on the page.
Solution: Ensure the widgetloader script is included before any widget initialization code. See the Getting Started Guide for proper script setup.
Incorrect Client ID
The Client ID in your configuration doesn't match your license.
Solution: Verify your Client ID is correct, or contact Support.
Wrong Widget Container
The DOM element selector doesn't exist or is incorrect.
Solution: Ensure the container element exists in your HTML before the widget initialization script runs.
Unrecognized Widget Name
The widget name is misspelled or doesn't exist.
Solution: Check the widget name against the documentation.
#Error Handling
#Silent Mode
The silent property suppresses error displays, preventing end users from seeing error messages.
Use silent: false during development and testing to see error details. Only enable silent: true in production after thorough testing.
View Silent Mode Example
SIR('addWidget', '<widget-container>', '<widget-name>', {
...widgetProps,
silent: true
});#Custom Error Handling
For advanced scenarios like conditional tab display, use the onTrack property to monitor widget events and handle errors programmatically.
The onTrack callback receives a data_change event when errors occur. See the onTrack documentation.
See these code examples:
#Visual Error Types
When a widget encounters an issue after loading, it displays an error icon with a message:
No Config
Error: "Something went wrong..."
Cause: Missing or incorrect required parameters like matchId, seasonId, or tournamentId.
Solution: Check browser console for specific details and verify all required widget parameters are provided correctly.
No Statistics
Error: "No statistics available" or "No data available"
Cause: Match hasn't started yet or data is temporarily unavailable.
Solution: This is expected for pre-match widgets. Data will appear once the match begins or when data becomes available.
No License
Error: License-related message
Cause: Widget, tournament, sport, or domain not covered by your license.
Solution: Review the Licensing Guide for detailed troubleshooting steps.
Error
Error: Unexpected error
Cause: Internal widget or API error.
Solution: Contact Support with details about the error, including widget name, configuration, and browser console output.