Repository navigation
|
My app was flagged or rejected on App Store and Google Play for this. Unsafe or unvalidated custom deep link URL schemes used for sensitive operations. Which guideline is this, how do I find it in my project, and how do I fix it before I resubmit? |
Replies: 1 comment
|
Guideline. Data Security (App Store and Google Play) Severity in the playbook. high What triggers it. Relying on custom URL schemes for sensitive routing, navigation, or passing tokens, without strict input validation. What to search your code for. How to fix it. Use Universal Links (iOS) and App Links (Android) for secure domain-validated link routing, and sanitize all deep link parameters. The guard reports this as This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
Guideline. Data Security (App Store and Google Play)
Severity in the playbook. high
What triggers it. Relying on custom URL schemes for sensitive routing, navigation, or passing tokens, without strict input validation.
What to search your code for.
CFBundleURLSchemes,android:schemeHow to fix it. Use Universal Links (iOS) and App Links (Android) for secure domain-validated link routing, and sanitize all deep link parameters.
The guard reports this as
BOTH-UNSAFE-DEEPLINK. The full pattern is in data/rejection-patterns.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
bash scripts/install.sh install,…