HSBBrowserAppStore-tvOS-review-public(中文版)
Improving tvOS Review Consistency: A Neutral Static-Analysis Example Involving WebKit Linking
Date: 2026-01-14
Purpose
This post shares a neutral, reproducible static‑analysis workflow to evaluate whether a tvOS app appears to use non‑public APIs—without decryption, runtime injection, or any attempt to bypass review systems.
The goal is not to accuse or shame, but to encourage better review consistency so that the same rules are applied reliably.
Scope & Principles
- Scope: Static inspection only (binary dependencies, metadata).
- Principles: Conclusions are based solely on reproducible facts, with explicit limitations.
High‑Level Method (Non‑Invasive)
- Verify bundle structure and architecture
- Read Info.plist (platform + versioning)
- Check App Store encryption markers
- List dynamic framework dependencies (key step)
- Cross‑check public tvOS SDK framework list
- Light Objective‑C class‑name scan (high‑level only)
- State limitations clearly
Key Findings (Condensed)
1) The app and its internal framework link against WebKit.framework
- Both the main executable and
HSBBrowser.framework dynamically link /System/Library/Frameworks/WebKit.framework/WebKit.