Content Scope Scripts Debugging

Overview

When developing or debugging Content Scope Scripts, validate script integrity, build outputs, and injection across all platforms.

When a feature is not working, check these in order:

Feature enabled in config — is the feature present and enabled in the privacy config for this site?
Feature bundled on the platform — is it included in the platform's entry point (entry-points/<platform>.js)?
Sub-feature or setting enabled — are the specific settings/sub-features turned on?
Messaging wired and listened to — are message handlers registered and the bridge initialized?
Script integrity — does the injected script match what you expect? (see below)

Verification Steps — Validate injected script integrity across build directory, native app, and web inspector
Config and Platform Parameters Validation — Using processConfig breakpoint to validate config state and platform parameters
Build Branch Hash Validation — For native engineers using build branches
Quick Validation Test — Test page for verifying C-S-S injection
Platform-specific setup and troubleshooting (iOS/macOS, Android, Windows, Extensions)
Source maps configuration
Local dependency linking