After this lesson you will
- Classify values by trust boundary: authority, client configuration, local input, shipped, flag
- Trace the build route from local.properties (BuildConfig) and Config.xcconfig (Info.plist) to AppBuildConfig and SecretManager
- Explain why the Supabase publishable key is allowed in the app and RLS is what protects the data
Duration5 min
DifficultyIntermediate
Protect Secrets In The Build (Android + iOS)
Learn a practical way to handle mobile secrets, on both Android and iOS.
- 01Lesson Goal
- 02Specific Objectives
- 03Part 1: Classify By Trust Boundary Instead Of Filename
- 04Part 2: The Path On Android
- 05Part 3: The Path On iOS
- 06Part 4: Two Paths, One Meeting Point
- 07Part 5: The Publishable Key May Be Exposed Because RLS Protects The Data
- 08Part 6: The Gate For The iOS Build
- 09Code Reading Path
- 10Code Smells
- 11References
- 12Key Points
Topics: mobile-action-pro, release-readiness
12 sections left in this lessonUnlock all of Mobile Action ProLesson Goal, Specific Objectives, … — plus 114 lessons in this course, source code and checklists.
Unlock Mobile Action ProOne-time payment — lifetime access — 7-day money-back. Already purchased? Sign in