feat(privacy+dist): telemetry consent gate + app store distribution prep (#4)
* fix(security): fail closed on biometric init error H-03: setting isAuthenticated: true on initialization failure was a security bypass — any crash during biometric setup granted full access. Fail closed instead; user sees auth prompt on next open. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * fix(security): use Crypto.randomUUID for connection IDs H-04: Math.random() is not cryptographically random. Connection IDs are used as SecureStore key suffixes; switch to expo-crypto randomUUID for a secure source. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * fix(deps): pin expo-crypto to ~15.0.9 15.0.10 does not exist on npm; ~15.0.9 is the latest stable in the 15.x series compatible with Expo SDK 54. * feat: add OpenCode Connect coming-soon waitlist card Adds a discoverable 'OpenCode Connect — Coming Soon' card to the add-connection quick-connect screen. Users can enter their email and tap 'Join Waitlist' to send a pre-filled mailto. No backend required. * fix(cua): detect actual screen dimensions and fix JSON parsing - Get real screen size via `wm size` instead of hardcoding 1080x2400; emulator is 1080x1920 so y-coordinates were systematically off - Extract first JSON object via regex when model returns multiple objects - Use AZURE_OPENAI_MODEL env var for deployment name (defaults gpt-5.4) - Add AZURE_DEV_AI_* path for Azure AI Foundry endpoints Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * fix(security): SHA-pin upload-google-play and sanitize notification bodies M-02: Pin r0adkll/upload-google-play to commit SHA e738b9d (v1.1.5) to prevent supply-chain hijack via tag mutation. M-03: Sanitize all push notification bodies — strip control chars, truncate to 200 chars. Prevents server-supplied strings (error messages, file paths from permission patterns, session titles) from leaking unbounded text into the OS notification drawer. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * feat(privacy): add telemetry consent gate for Sentry crash reporting Sentry was always-on, violating F-Droid anti-feature policy and user trust norms. Now gated behind explicit opt-in: - First-launch consent modal (TelemetryConsentModal) shows once on fresh install; user can Allow or Decline. - Consent state persisted in expo-secure-store (survives restarts). - Settings > Privacy section: crash reporting toggle + privacy policy link. - initSentry() called only after consent granted — not on app start. Closes #3 (partial) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * feat(config): add real icons and complete iOS/Android app.json config - Add 1024×1024 app icon, 432×432 adaptive icon foreground, 200×200 splash - iOS: push notification entitlement (aps-environment: production), speech/ microphone/camera/photo usage descriptions for future features, disable ITSAppUsesNonExemptEncryption - Android: adaptive icon with dark background (#0F172A), versionCode: 1 - expo-notifications plugin wired in app.json Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * feat(dist): add iOS CI workflow, README rewrite, CONTRIBUTING, and LICENSE - publish-app-store.yml: EAS Build + TestFlight submission; runs on tag/release/ workflow_dispatch; bumps ios.buildNumber from github.run_number - README: full rewrite — features, install badges, connection guide, contributing - CONTRIBUTING.md: contribution guide for OSS contributors - LICENSE: MIT Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * docs(dist): add store listings, strategy, privacy policy, F-Droid/IzzyOnDroid templates - distribution/strategy.md: monetization strategy (free client + opencode Cloud) - distribution/play-listing.md: Google Play store copy (name, description, tags) - distribution/app-store-listing.md: App Store listing copy - distribution/privacy-policy.{md,html}: GDPR-compliant privacy policy - distribution/PLAY_CONSOLE_SETUP.md: Play Console setup runbook - distribution/ios-enrollment-runbook.md: Apple Developer Program enrollment steps - distribution/SIGNING-KEY-FINGERPRINTS.md: keystore fingerprint for reproducible builds - distribution/fdroid-submission/: F-Droid metadata template - distribution/izzyondroid-submission/: IzzyOnDroid submission template - distribution/whatsnew/: Play Store release notes (en-US) - distribution/whatsnew-ios/: TestFlight release notes - distribution/play-graphics/: Play Store screenshot placeholders - distribution/app-store-graphics/: App Store screenshot placeholders Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * fix(telemetry): handle SecureStore failure + Android back button - add .catch() on loadTelemetryConsent() so SecureStore rejection shows the consent modal instead of blocking startup forever - add onRequestClose={onDecline} to Modal so Android back button records the decline rather than silently dismissing - fix catch block in telemetry.ts to not clobber _resolved when SecureStore read fails mid-session Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * fix(ci): run gradlew clean to prevent stale modules.json duplicate Sentry Gradle plugin writes modules.json to src/main/assets; cached build intermediates contain an old copy → mergeReleaseAssets fails with 'Duplicate resources'. Running clean before assembleRelease clears the intermediate state. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * fix(ci): remove android build output cache causing duplicate modules.json Caching android/app/build/intermediates and android/app/.cxx causes two issues: 1. Stale modules.json in intermediates → Duplicate resources error 2. .cxx CMake artifacts reference absolute paths → ninja clean fails Keeping only Gradle distribution cache (~/.gradle) which is safe. Expo prebuild regenerates android sources fresh each run anyway. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Den
80
src/lib/telemetry.ts
Normal file
80
src/lib/telemetry.ts
Normal file
@@ -0,0 +1,80 @@
|
||||
/**
|
||||
* Telemetry consent + initialisation gate.
|
||||
*
|
||||
* Wraps sentry.ts so that initSentry() is only called when the user has
|
||||
* explicitly opted in. Consent state is persisted in expo-secure-store so
|
||||
* it survives app restarts.
|
||||
*
|
||||
* Usage:
|
||||
* import { loadTelemetryConsent, setTelemetryConsent, hasTelemetryConsent } from './telemetry'
|
||||
*
|
||||
* // On app start — call BEFORE trying to initialise Sentry.
|
||||
* const state = await loadTelemetryConsent() // 'granted' | 'denied' | 'unknown'
|
||||
* if (state === 'granted') initSentry()
|
||||
*
|
||||
* // After the user taps "Allow" in the consent modal:
|
||||
* await setTelemetryConsent(true) // persists + calls initSentry() if not already done
|
||||
*
|
||||
* // Check in Settings screen:
|
||||
* const current = hasTelemetryConsent() // boolean | null (null = not yet decided)
|
||||
*/
|
||||
|
||||
import * as SecureStore from "expo-secure-store"
|
||||
import { initSentry, sentryEnabled } from "./sentry"
|
||||
|
||||
const CONSENT_KEY = "opencode_telemetry_consent"
|
||||
|
||||
export type ConsentState = "granted" | "denied" | "unknown"
|
||||
|
||||
let _resolved: boolean | null = null // null = unknown, true = granted, false = denied
|
||||
|
||||
/**
|
||||
* Load persisted consent from SecureStore.
|
||||
* Returns 'unknown' if the user has never been asked.
|
||||
*/
|
||||
export async function loadTelemetryConsent(): Promise<ConsentState> {
|
||||
try {
|
||||
const stored = await SecureStore.getItemAsync(CONSENT_KEY)
|
||||
if (stored === "granted") {
|
||||
_resolved = true
|
||||
return "granted"
|
||||
}
|
||||
if (stored === "denied") {
|
||||
_resolved = false
|
||||
return "denied"
|
||||
}
|
||||
// No stored value — first launch
|
||||
_resolved = null
|
||||
return "unknown"
|
||||
} catch {
|
||||
// SecureStore unavailable — don't clobber a previously resolved in-memory state.
|
||||
// Return unknown so the caller can surface the modal.
|
||||
return "unknown"
|
||||
}
|
||||
}
|
||||
|
||||
/**
|
||||
* Returns the in-memory resolved state (set by loadTelemetryConsent or setTelemetryConsent).
|
||||
* null = consent decision not yet loaded.
|
||||
* true = granted.
|
||||
* false = denied.
|
||||
*/
|
||||
export function hasTelemetryConsent(): boolean | null {
|
||||
return _resolved
|
||||
}
|
||||
|
||||
/**
|
||||
* Persist the user's consent decision and, if granted and Sentry is not yet
|
||||
* running, initialise it immediately.
|
||||
*/
|
||||
export async function setTelemetryConsent(granted: boolean): Promise<void> {
|
||||
_resolved = granted
|
||||
try {
|
||||
await SecureStore.setItemAsync(CONSENT_KEY, granted ? "granted" : "denied")
|
||||
} catch {
|
||||
// Best-effort persist — in-memory state is still correct for this session.
|
||||
}
|
||||
if (granted && !sentryEnabled()) {
|
||||
initSentry()
|
||||
}
|
||||
}
|
||||
Reference in New Issue
Block a user