Repository navigation
|
My app was flagged or rejected on App Store and Google Play for this. Sensitive tokens or credentials stored in insecure unencrypted formats. 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. Sensitive session credentials or tokens are saved directly to unencrypted plist, UserDefaults, or SharedPreferences instead of Keychain or Android Keystore / EncryptedSharedPreferences. What to search your code for. How to fix it. Store all sensitive data and access tokens in iOS Keychain or Android EncryptedSharedPreferences. 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. Sensitive session credentials or tokens are saved directly to unencrypted plist, UserDefaults, or SharedPreferences instead of Keychain or Android Keystore / EncryptedSharedPreferences.
What to search your code for.
UserDefaults.standard.set,getSharedPreferencesHow to fix it. Store all sensitive data and access tokens in iOS Keychain or Android EncryptedSharedPreferences.
The guard reports this as
BOTH-SECURE-STORAGE. 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…