chahine/rebreak-monorepo
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

chore(rebreak-native): expose familyControlsEnabled flag to the JS bundle

Browse Source 
extra.familyControlsEnabled mirrors the eas.json REBREAK_ENABLE_FAMILY_CONTROLS
build flag — true for development builds (Apple granted the Development Family
Controls entitlement), false for TestFlight/production (Distribution entitlement
still pending). The Blocker page uses it to show "App-Lock — coming soon" instead
of a toggle that throws NSCocoaError 4099, while keeping the protection banner
positive (the URL filter carries it).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
chahinebrini 2026-05-12 21:39:37 +02:00
parent 7ad523f8ba
commit e48a3187a6
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
apps/rebreak-native/app.config.ts
View File

@ -123,6 +123,12 @@ export default ({ config }: ConfigContext): ExpoConfig => ({
},
},
},
// Spiegelt das Build-Flag aus eas.json (development.env.REBREAK_ENABLE_FAMILY_CONTROLS)
// in den JS-Bundle, damit die Blocker-Page weiß ob die App-Lock (denyAppRemoval via
// FamilyControls) verfügbar ist. In TestFlight/production-Builds ist das (noch) false
// → dort UI: "Family Controls — coming soon" statt eines kaputten Toggles, der
// Schutz-Banner bleibt trotzdem positiv ("Schutz komplett", der URL-Filter trägt).
familyControlsEnabled: process.env.REBREAK_ENABLE_FAMILY_CONTROLS === "1",
apiUrl:
process.env.EXPO_PUBLIC_API_URL ||
process.env.API_URL ||