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
pubspec.yaml present within 12 levels of the project root
React Native / Expo
package.json within 12 levels with a dependency on react-native or expo
Ionic / Capacitor / Cordova
package.json within 12 levels with a dependency on @capacitor/*, @ionic/*, or cordova-*, OR a capacitor.config.* / config.xml file within 12 levels
These depths come from the find_app calls in agent-os/hooks/app-store-compliance-guard.sh. Unity, .NET MAUI, Tauri mobile,
and Kotlin Multiplatform are searched within 6 levels.
A project can match more than one framework flag (a Capacitor app that also
imports expo polyfills, for example); every matching check runs. Detection scans
EVERY package.json/config.xml within depth, not only the first, so a monorepo
whose root package.json is tooling-only still finds the real app deeper in the
tree. A config.xml only counts as Cordova evidence when it carries a <widget>
or xmlns:cdv marker, since that filename collides with unrelated tooling configs.
Every framework-specific finding below is gated on IOS_TARGET_ACTIVE, not raw
file-tree presence. A committed ios/ folder is common in a real cross-platform
repo even when the current build is Android-only, so file presence alone cannot
tell flutter build apk apart from an iOS build. When the invoking command is
known (hook mode) and clearly targets Android only (build apk/appbundle, assembleRelease, bundleRelease, run-android, run:android, --platform android, capacitor android, with no ios/ipa/xcodebuild
token present), the command overrides the file-tree signal and these Apple-only
checks stay silent. 2.0.0 also requires every other command in the line to be a
known harmless one, so it never silences more than 1.0.0 did. Standalone mode (no command context) falls back to plain
file-tree detection.
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.
pubspec.yamlpresent within 12 levels of the project rootpackage.jsonwithin 12 levels with a dependency onreact-nativeorexpopackage.jsonwithin 12 levels with a dependency on@capacitor/*,@ionic/*, orcordova-*, OR acapacitor.config.*/config.xmlfile within 12 levelsThese depths come from the
find_appcalls inagent-os/hooks/app-store-compliance-guard.sh. Unity, .NET MAUI, Tauri mobile,and Kotlin Multiplatform are searched within 6 levels.
A project can match more than one framework flag (a Capacitor app that also
imports
expopolyfills, for example); every matching check runs. Detection scansEVERY
package.json/config.xmlwithin depth, not only the first, so a monorepowhose root
package.jsonis tooling-only still finds the real app deeper in thetree. A
config.xmlonly counts as Cordova evidence when it carries a<widget>or
xmlns:cdvmarker, since that filename collides with unrelated tooling configs.Every framework-specific finding below is gated on
IOS_TARGET_ACTIVE, not rawfile-tree presence. A committed
ios/folder is common in a real cross-platformrepo even when the current build is Android-only, so file presence alone cannot
tell
flutter build apkapart from an iOS build. When the invoking command isknown (hook mode) and clearly targets Android only (
build apk/appbundle,assembleRelease,bundleRelease,run-android,run:android,--platform android,capacitor android, with noios/ipa/xcodebuildtoken present), the command overrides the file-tree signal and these Apple-only
checks stay silent. 2.0.0 also requires every other command in the line to be a
known harmless one, so it never silences more than 1.0.0 did. Standalone mode (no command context) falls back to plain
file-tree detection.
Source section. CROSS-PLATFORM-FRAMEWORKS.md, Detection.
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