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
What stays out of reach. Cross Platform Frameworks
#1325
These are limits, not bugs waiting for a fix. Plan around them.
Anything that runs on a CI server.gh workflow run, a release started from a CI dashboard, and a fastlane lane run by a runner are never seen by a hook on your machine.
Uploads from an app window. Xcode Organizer, the Transporter app, the Unity Editor build window and Android Studio's Generate Signed Bundle do not run a shell command.
A Unity build whose target is chosen in code.-executeMethod with no -buildTarget iOS or Android on the command line is not treated as a submit.
Unity and .NET MAUI build settings. Info.plist keys and Gradle settings that the tool generates at build time are not read. For .NET MAUI the linker and target API settings in the .csproj are not checked, and dotnet build -t:Publish is not matched. A Mac Catalyst publish is not treated as a submit.
Tauri before init. With no src-tauri/gen/apple or src-tauri/gen/android folder there is nothing native to scan. The report names the command to run.
A Tauri app beside a native app. In a monorepo a Tauri folder with no gen/apple or gen/android is treated as a desktop app, so it does not stop a CLEAR for the native app next to it.
Rust naming. The sign-in and account-deletion patterns look for camelCase names such as signIn. A Rust function named sign_in does not trigger them.
Frameworks not detected. NativeScript and legacy Xamarin.Forms projects.
More than one Xcode target. Targets are read as one body of source, so an app extension can satisfy, or trigger, a finding for the main app. A watchOS-only or visionOS-only workspace is treated as iOS.
Pooled or split layouts that remain coarse (inherited from 1.0). A single nested managed Expo app is read through the root's config only, shared packages and a brownfield host's source outside the scanned root are not followed, every native target in one root is pooled, and two .NET MAUI or Unity apps in one repo are scanned as one.
Workspace runners. A package script is followed one level deep, so a root script that runs turbo run build, which in turn runs a mobile package's submit, is not seen. A pnpm graph selector (web..., ...web, {apps/web}) is reduced to its package name, without following that package's dependencies or dependents, and a change-set selector such as "[origin/main]" cannot be resolved, so it reads every package, which can block a web-only build in a repo that also holds a mobile app. Run the web build without the wrapper, or set APP_STORE_GUARD_OK=1 once.
Cross-platform purchase plugins. 1.0.0 checked the restore flow only for native StoreKit apps. 2.0.0 also checks a react-native-iap, RevenueCat or Flutter purchase plugin app, where a purchase list query (getAvailablePurchases, queryPastPurchases) or the plugin's restore call counts as the restore flow. Check by hand that a visible Restore Purchases control calls it.
Monitor source verification. The regulatory and privacy monitors mark a claim as corroborated when an official source shares its keywords, not when that source states the same claim. Read the official source before acting on a monitor item.
Store console state. The guard cannot see App Store Connect or Play Console, so the age rating, social media declaration, and closed testing items are reminders, not proof of a problem.
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.
These are limits, not bugs waiting for a fix. Plan around them.
gh workflow run, a release started from a CI dashboard, and a fastlane lane run by a runner are never seen by a hook on your machine.-executeMethodwith no-buildTarget iOSorAndroidon the command line is not treated as a submit..csprojare not checked, anddotnet build -t:Publishis not matched. A Mac Catalyst publish is not treated as a submit.src-tauri/gen/appleorsrc-tauri/gen/androidfolder there is nothing native to scan. The report names the command to run.gen/appleorgen/androidis treated as a desktop app, so it does not stop aCLEARfor the native app next to it.signIn. A Rust function namedsign_indoes not trigger them.turbo run build, which in turn runs a mobile package's submit, is not seen. A pnpm graph selector (web...,...web,{apps/web}) is reduced to its package name, without following that package's dependencies or dependents, and a change-set selector such as"[origin/main]"cannot be resolved, so it reads every package, which can block a web-only build in a repo that also holds a mobile app. Run the web build without the wrapper, or setAPP_STORE_GUARD_OK=1once.getAvailablePurchases,queryPastPurchases) or the plugin's restore call counts as the restore flow. Check by hand that a visible Restore Purchases control calls it.Source section. CROSS-PLATFORM-FRAMEWORKS.md, What stays out of reach.
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