Repository navigation
|
How can a team catch Thin WebView wrapper with insufficient native functionality automatically before a build goes to review? |
Replies: 1 comment
|
The quick check. Run this from the project root and read what it prints. grep -rlE 'WKWebView|loadRequest|Capacitor|Cordova' --include='*.ts' --include='*.js' --include='*.swift' . 2>/dev/null | wc -l # then count distinct @capacitor/(status-bar|splash-screen|push-notifications|haptics) markers, fewer than 2 is a thin wrapperRead the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as What the hit means. A Capacitor/Cordova/WKWebView marker is present alongside fewer than 2 distinct native-feel plugins (status bar, splash screen, push notifications, haptics, share, camera, local notifications). This is a heuristic proxy for the real Apple 4.2 test (features/content/UI beyond a repackaged website), reviewed manually before treating as a blocker. The fix. Apple 4.2 Minimum Functionality is the single most common Ionic rejection. Add native Capacitor/Cordova plugins for status bar, splash transition, push, and haptics, or ship as an installable PWA to skip App Review. Recipe source. data/detection-recipes.json This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
The quick check. Run this from the project root and read what it prints.
Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as
IONIC-4.2-THIN-WRAPPERwith a coverage line and a proper exit code.What the hit means. A Capacitor/Cordova/WKWebView marker is present…