You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Known gaps (found by Codex and Qwen adversarial review, not yet fixed). Cross Platform Frameworks
#1329
Newline-containing file paths. The package.json/config.xml scan loops
are safe against spaces and shell metacharacters (quoted IFS= read -r), but
not against a literal newline inside a path, which find's newline-delimited
output cannot represent. Extremely unlikely in practice, and not proven safe.
config.xml widget-marker check is spoofable by a comment. A commented-out <!-- <widget ...> --> or a look-alike tag like <widgetConfig> still counts
as Cordova evidence. Low severity, no realistic false negative on a real
Cordova project, though not a hard proof either.
Android-side framework checks are thin. Apart from the Android
permissions array a managed Expo app config declares, every check in this doc is
Apple-side. Flutter/RN/Ionic apps also ship to Google Play, where Data Safety
disclosure for bundled SDKs, WebView-controlled data collection, cleartext
traffic, and mixed-content/debug flags are real, framework-relevant risks this
guard does not yet check.
The PrivacyInfo.xcprivacy check reads the app's own manifest only.
A manifest under Pods, Carthage, node_modules, SwiftPM .build or
checkouts, SourcePackages or Flutter .symlinks does not count. A managed
Expo app passes with expo.ios.privacyManifests in its app config, since EAS
generates the native project at build time.
Expo Continuous Native Generation (CNG) is modeled for config only. A
managed Expo project with no committed ios/ or android/ folder has its app.json or app.config read for camera and location purpose strings, ios.privacyManifests and the sensitive android.permissions entries. Its
native code is still NOT CHECKED until npx expo prebuild runs.
Two frameworks have no coverage. NativeScript and legacy Xamarin.Forms
are not detected. Unity, .NET MAUI, Tauri mobile, and Kotlin Multiplatform
are, see the section above for what each one still cannot see.
The submission regex errs toward firing.SUBMIT_RE in agent-os/hooks/app-store-compliance-guard.sh matches eas build with or
without a --platform flag, also when global flags come before the
subcommand. It also matches every cap run and cap open, so a local dev
run with no release intent still triggers the guard.
These are logged, not hidden. Track them before treating this guard as complete
coverage for a cross-platform team; the checks that exist are a real
improvement over native-only, not a finished answer.
This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run bash scripts/install.sh install, then run the guard on your project before you submit. Questions or a correction? Reply below.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
package.json/config.xmlscan loopsare safe against spaces and shell metacharacters (quoted
IFS= read -r), butnot against a literal newline inside a path, which
find's newline-delimitedoutput cannot represent. Extremely unlikely in practice, and not proven safe.
config.xmlwidget-marker check is spoofable by a comment. A commented-out<!-- <widget ...> -->or a look-alike tag like<widgetConfig>still countsas Cordova evidence. Low severity, no realistic false negative on a real
Cordova project, though not a hard proof either.
permissions array a managed Expo app config declares, every check in this doc is
Apple-side. Flutter/RN/Ionic apps also ship to Google Play, where Data Safety
disclosure for bundled SDKs, WebView-controlled data collection, cleartext
traffic, and mixed-content/debug flags are real, framework-relevant risks this
guard does not yet check.
A manifest under
Pods,Carthage,node_modules, SwiftPM.buildorcheckouts,
SourcePackagesor Flutter.symlinksdoes not count. A managedExpo app passes with
expo.ios.privacyManifestsin its app config, since EASgenerates the native project at build time.
managed Expo project with no committed
ios/orandroid/folder has itsapp.jsonorapp.configread for camera and location purpose strings,ios.privacyManifestsand the sensitiveandroid.permissionsentries. Itsnative code is still NOT CHECKED until
npx expo prebuildruns.are not detected. Unity, .NET MAUI, Tauri mobile, and Kotlin Multiplatform
are, see the section above for what each one still cannot see.
SUBMIT_REinagent-os/hooks/app-store-compliance-guard.shmatcheseas buildwith orwithout a
--platformflag, also when global flags come before thesubcommand. It also matches every
cap runandcap open, so a local devrun with no release intent still triggers the guard.
These are logged, not hidden. Track them before treating this guard as complete
coverage for a cross-platform team; the checks that exist are a real
improvement over native-only, not a finished answer.
Source section. CROSS-PLATFORM-FRAMEWORKS.md, Known gaps (found by Codex and Qwen adversarial review, not yet fixed).
This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run
bash scripts/install.sh install, then run the guard on your project before you submit. Questions or a correction? Reply below.All reactions