fix(android): extend SCVH pre-check to API 30..36 + v0.1.10

[amillez]

Summary

v0.1.10 — extends the SCVH INTERNAL_SYSTEM_WINDOW pre-check from API 30..32 (v0.1.9) to API 30..36, after the user reported the Invalid window token crash recurring on Android 13 (API 33) production devices.

Empirical SCVH behaviour across the suspect API range

Tested host.setView() on stock Google APIs system images for every API:

API	Android	Stock SCVH attach	Stock crash
30	11	❌ SecurityException: Requires INTERNAL_SYSTEM_WINDOW	yes (without safety net)
31	12	❌ SecurityException	yes (without safety net)
32	12L	❌ (inferred)	yes
33	13	❌ RuntimeException: Adding window failed	no on stock; yes on OEM (user reports)
34	14	❌ RuntimeException	no on stock; OEM unknown
35	15	❌ RuntimeException	no on stock; OEM unknown
36	15 QPR	❌ RuntimeException	no on stock; OEM unknown
37	16	✅ attached size=… sc=ok	n/a

The exception type differs but the underlying SCVH behaviour is the same: ViewRootImpl.setView calls requestLayout() before the throwing addToDisplay, leaving a TraversalRunnable queued in the SCVH Choreographer. On Android 14+, hidden-API enforcement blocks the reflective unscheduleScvhTraversals safety net (the SCVH mViewRoot field is @hide), so we cannot cancel the runnable; at the next vsync it fires against an unregistered WWM token and the process dies from Looper.loop.

Stock emulator images happened not to queue a problematic runnable on the RuntimeException path (no observed crash on Pixel 6 / 33..36), but OEM-customised WMS builds (Samsung One UI on Android 13 specifically) do — confirmed by the user's production crash reports.

Fix

-if (Build.VERSION.SDK_INT in Build.VERSION_CODES.R..Build.VERSION_CODES.S_V2 &&
+if (Build.VERSION.SDK_INT in Build.VERSION_CODES.R..36 &&
   activity.checkSelfPermission("android.permission.INTERNAL_SYSTEM_WINDOW")
     != PackageManager.PERMISSION_GRANTED
 ) {
   scvhDisabled = true
   return false
 }

API 37+ keeps SCVH active (Pixel_9 emulator confirmed) — the SurfaceFlinger-direct alpha toggle continues to win the Home-press snapshot race (broadcast: fast scvh=true dt=0ms).

Trade-off

API 30..36 devices use the legacy view.alpha path instead of the SF-direct alpha. On Android 14+ the reflection-based SC capture used by the legacy fast path is also blocked, so the actual SF-direct benefit loss is concentrated on Android 11..13 — where the pre-check is non-negotiable to prevent crashes.

Verified

Device	API	Result
Pixel 6 emulator	31	✅ Pre-check fires, legacy attach, no crash, 5x home/app-switcher + 10x toggle stress clean
Pixel 6 emulator	33	✅ Pre-check fires, legacy attach, no crash
Pixel 6 emulator	34	✅ Pre-check fires, legacy attach, no crash
Pixel 6 emulator	35	✅ Pre-check fires, legacy attach, no crash
Pixel 6 emulator	36	✅ Pre-check fires, legacy attach, no crash
Pixel_9 emulator	37	✅ Pre-check skipped (out of range), SCVH attaches, broadcast: fast scvh=true

Files changed

• android/src/main/java/com/margelo/nitro/cover/HybridCover.kt — range expanded from R..S_V2 to R..36, comments updated.
• package.json — 0.1.9 → 0.1.10.
• CHANGELOG.md — new 0.1.10 - 2026-06-02 entry.