Repository navigation
|
How can a team catch Unsafe or unvalidated custom deep link URL schemes used for sensitive operations 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 -rn 'CFBundleURLSchemes\|android:scheme' . && ! grep -rn 'apple-app-site-association\|assetlinks.json' .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 What the hit means. Relying on custom URL schemes for sensitive routing, navigation, or passing tokens, without strict input validation. The fix. Use Universal Links (iOS) and App Links (Android) for secure domain-validated link routing, and sanitize all deep link parameters. 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
BOTH-UNSAFE-DEEPLINKwith a coverage line and a proper exit code.What the hit means. Relying on custom URL schemes for sensitive routing, navigation, or passing tokens, without strict input validation.
The fix. Use Universal Links (iOS) and App Links (Android) for secure domain-va…