דילוג לתוכן
מרכז התיעוד
לאתר LinkNodes Energy
LinkNodesENERGYתיעוד

טוענים את החיפוש…

    חיפוש גם בתוך המאמרים ↑ ↓ לניווט Esc לסגירה

    לאתר החברה

    מובייל ופלטפורמות

    מוכנות הפצה למובייל — P7

    תיעוד הכנת גרסאות לחנויות ודרישות הקבלה החיצוניות.

    בעמוד הזה

    Locked scope#

    P1–P6 approved screens, app appearance, assets, icons, map behavior, tenant isolation, authorization, financial workflows and provider integrations are immutable. P7 changes only native build configuration, explicit EAS environment identifiers, release preflight scripts/tests and this documentation. No image was replaced, regenerated or differently cropped.

    Implementation shipped in this PR#

    • apps/mobile/app.config.ts preserves the approved identity and existing app.json configuration. It adds react-native-maps Android native key configuration only when GOOGLE_MAPS_ANDROID_API_KEY is provided as an environment variable at build time; no key is committed, and it has no effect on existing running builds.
    • Optionally attaches a registered EAS_PROJECT_ID to the dynamic Expo configuration without changing project identity in source.
    • Existing development, preview and production EAS build profiles now explicitly identify their respective EXPO_PUBLIC_APP_ENV. Other build options are unchanged.
    • Dependency-free pnpm --filter @linknodes/mobile run release:preflight checks the approved app IDs, Expo/EAS project, public runtime configuration, HTTPS endpoints, expected Production API origin, signed-Android Google Maps key presence, opaque 1024×1024 RGB store icon path, and opt-in telemetry prerequisites. It never prints secrets or signs/uploads a build.
    • pnpm --filter @linknodes/mobile run test:release checks expected pass and fail-closed cases with synthetic fixtures.

    Verified QA#

    • P7 release preflight regression tests: 9/9 PASS.
    • Running Production preflight without release credentials: exits 1 with missing-gate list (correct fail closed).
    • Mobile TypeScript check: PASS.
    • Expo Doctor: 20/20 checks PASS.
    • Metro iOS Hermes JS bundle export: PASS.
    • Metro Android Hermes JS bundle export: PASS.
    • Expo Android prebuild: PASS using a synthetic key. Inspected generated AndroidManifest.xml: com.google.android.geo.API_KEY entry appeared with the synthetic value. No credential was stored or committed.
    • Expo iOS prebuild: PASS, with Sign in with Apple entitlement. It is not a signed IPA.
    • Expo config evaluation with key absent: PASS; no Maps config plugin injected and approved app identity preserved.

    External store-release gates — not yet verified#

    1. Register/link com.linknodesenergy.app to a real Expo EAS project ID, configure Apple Developer Team and App ID Prefix, provisioning certificates, Android keystore/Play App Signing and required Expo/Clerk native settings.
    2. Create the restricted Google Maps SDK for Android key in the authorized Google Cloud project; bind package name plus signing SHA-1. Inject the key privately into the native EAS build environment.
    3. Supply a faithful, approved opaque 1024×1024 RGB PNG of the locked apps/mobile/assets/linknodes-icon.svg; do not silently replace or reinterpret artwork. Set expo.icon to this approved derivative only after visual approval. Prepare required screenshots and disclosures separately.
    4. Supply production publishable Clerk/Supabase values and the approved HTTPS API URL to the EAS environment. Never insert service-role credentials or HYPE keys into an Expo client.
    5. Build signed iOS and Android development/test artifacts, verify on real devices (Clerk auth, login/logout, tenant isolation, map tiles, foreground location, API errors and offline states), then submit to TestFlight/Play Internal Testing and confirm store processing.
    6. Activate native Grafana crash reporting only after the Mobile preview entitlement, dedicated collector and signed-device crash tests pass. PostHog remains opt-in until ingestion/privacy are verified.
    7. Store approval, privacy disclosures, support URL, legal documents, rollback and signed build hash verification remain release gates.

    Result: P7 code/build configuration is ready for review and safe to merge with all external secrets absent. This does not constitute completed signed Store releases, certified maps key, or store approvals.