Repository navigation
fix(sdk): keep React Native tracking usable on Expo 55 - #565
Conversation
Accept Expo 55 peers and omit the optional User-Agent when the native helper is absent or fails. Preserve namespace/default module interop and the existing supported peer ranges.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
Keep React Native version/build metadata usable when the optional install-referrer service rejects, including foreground refresh. Preserve previously known attribution on lookup failure and cover initialization, recovery, Android success and iOS behavior.
Declare Bun test types and a package test command so the Expo compatibility tests typecheck in isolation. Assert native referrer calls to prevent false-positive foreground and iOS controls.
…npanel-dev#639) The squash merge of Openpanel-dev#565 added `bun-types` as a devDependency of `@openpanel/react-native`, but the merged `bun.lock` lacked the matching entry. Every `bun install --frozen-lockfile` on main failed with "lockfile had changes, but lockfile is frozen", so no Docker image or SDK could be built from the last four commits. Fixed - The lockfile has the missing `bun-types` entry for the React Native SDK, so installs and CI builds on main work again. No dependency versions change.
Expo 55 consumers can fail peer validation or SDK construction because the User-Agent helper is not always available as a namespace export. Android initialization can also reject when the optional Play Store install-referrer service is unavailable.
Accept the Expo 55 peer major while retaining the existing supported ranges. Resolve the User-Agent helper from the default export or namespace, preserve its receiver, and omit the custom header when the helper is unavailable or fails. Contain Android referrer failures so version/build metadata remains available and previously known attribution is retained.
The follow-up also fixes the test setup: declare Bun test types in the manifest and tsconfig, add a package test command, and assert native referrer calls so foreground/iOS controls cannot silently pass without exercising the mocked dependency. No workflow changes are included.
Validation:
--force,--legacy-peer-depsor monorepo overrides. Expo 55.0.32, React Native 0.83.10, expo-application 55.0.19, expo-constants 55.0.17;expo install --checkpassed.Limits: the app consumed locally packed build artifacts with workspace specs resolved to local versions; the npm release pipeline was not exercised. Native validation is Android emulator only: no iOS runtime, physical device, release build, production ingestion/ClickHouse pipeline, or full monorepo test/typecheck run is claimed. The receiver was a local HTTP capture endpoint. No package release or deployment was performed.
Fixes #358.
Summary by CodeRabbit