feat(expo): update for 1.2.0#247
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
superwall-docs | b0ad551 | Commit Preview URL Branch Preview URL |
Jul 14 2026, 07:56 PM |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4d0fedf3d2
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ```typescript | ||
| const options = SuperwallOptions() | ||
| options.isExternalDataCollectionEnabled = false | ||
| options.eventTrackingBehavior = EventTrackingBehavior.None |
There was a problem hiding this comment.
For the Expo Provider/hook API, eventTrackingBehavior is a string union ("all" | "superwallOnly" | "none") and the package re-exports EventTrackingBehavior only as a type, not a runtime enum value. Copying this snippet therefore fails to compile with the normal expo-superwall import, and the same bad enum value is repeated for the runtime setter below; use string literals such as "none", or explicitly document a supported compat import if that is the intended API.
Useful? React with 👍 / 👎.
Use the Expo v2 object-parameter API (Superwall.configure({ apiKey, options }))
and new SuperwallOptions() in the eventTrackingBehavior example.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
EventTrackingBehavior is exported only as a type from expo-superwall (and is
not re-exported from the compat entry), so the enum member access does not
exist at runtime. Use the string-union values ("all"/"superwallOnly"/"none").
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4e167693ed
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| const options = new SuperwallOptions() | ||
| options.eventTrackingBehavior = "none" |
There was a problem hiding this comment.
Fresh evidence is that the updated example now uses string literals while still instantiating new SuperwallOptions(). For the non-compat Expo SDK, eventTrackingBehavior is a string-union field on PartialSuperwallOptions, but SuperwallOptions is exported only as a type, so this block cannot compile when copied from the Expo guide; use an options object literal such as { eventTrackingBehavior: "none" } with <SuperwallProvider>/useSuperwall, or make the whole snippet explicitly compat with the compat import/API.
Useful? React with 👍 / 👎.
…larDeviceId docs - Rewrite the Expo eventTrackingBehavior examples to the hooks/provider API (SuperwallProvider options + useSuperwall selectors), since the compat EventTrackingBehavior enum is not exported from expo-superwall/compat. - Document the new singularDeviceId integration attribute for Expo using the hooks API, whose IntegrationAttributes type includes the key (the compat union does not). - Note the compat-entry limitation for eventTrackingBehavior. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1 participant
Summary
Updates the Superwall Expo SDK docs from
1.1.6->1.2.0.Upstream: superwall/expo-superwall@v1.1.6...v1.2.0
Changelog source:
reference/expo/CHANGELOG.md(## 1.2.0entry)Release highlights (from upstream changelog / diff):
4.16.1, Android2.7.20.eventTrackingBehavioroption (all/superwallOnly/none) onSuperwallOptions, deprecatingisExternalDataCollectionEnabled.setEventTrackingBehavior(...)method.singularDeviceIdas a supported integration attribute.getStoreFrontCountryCode()to retrieve the App Store / Play Store storefront country code.Checklist of doc updates performed
content/docs/expo/index.mdx— bumped<SdkLatestVersion>fromv1.1.6tov1.2.0.content/docs/expo/sdk-reference/index.mdx— bumped<SdkLatestVersion>fromv1.1.6tov1.2.0.content/docs/expo/changelog.mdx— added the1.2.0entry verbatim from upstream, above the existing1.1.6entry (history preserved, nothing replaced).content/docs/expo/sdk-reference/hooks/useSuperwall.mdx— documented the newsetEventTrackingBehaviorandgetStoreFrontCountryCodeactions in the returned-valuesTypeTable.content/shared/configuring/using-superwalloptions.mdx— updated the:::expoblock in the "Event Tracking Behavior" section to documenteventTrackingBehavior(mirroring the existing iOS/Android sections), including the runtime setter and theisExternalDataCollectionEnableddeprecation note.Follow-up / known gaps
singularDeviceIdwas intentionally not added to any exhaustive integration-attribute list in the Expo docs, because no such list exists today (the existing docs only referenceappstackIdas an example and otherwise say "etc."). No other SDK version markers, install snippets, or pinned native-SDK version strings were found elsewhere in the Expo docs.bun testpasses (64/64).bun run build:cf(vite build) could not be completed in this sandbox — the process is OOM-killed by the environment (2 vCPU / ~3.8GB RAM) during the chunk-rendering phase, reproducibly, after cleanly transforming all 7354 modules with no MDX/content errors. This appears to be a pre-existing sandbox resource limitation unrelated to this change; recommend re-runningbun run build:cfin CI/a larger environment before merge.🤖 Generated with Claude Code
Note
Low Risk
Documentation-only changes with no runtime, auth, or data-handling code modifications.
Overview
Updates Superwall Expo documentation from v1.1.6 to v1.2.0, including changelog entry,
<SdkLatestVersion>on the Expo welcome and SDK reference pages, and release notes for native iOS 4.16.1 / Android 2.7.20.The shared Event Tracking Behavior Expo section now documents
eventTrackingBehavior("all"/"superwallOnly"/"none") onSuperwallProvider, runtimesetEventTrackingBehaviorviauseSuperwall, and deprecation ofisExternalDataCollectionEnabled(with mapping to"superwallOnly").useSuperwallreference addssetEventTrackingBehaviorandgetStoreFrontCountryCode.Singular integration docs add an Expo snippet for typed
singularDeviceIdthroughsetIntegrationAttributes.Reviewed by Cursor Bugbot for commit b0ad551. Bugbot is set up for automated code reviews on this repo. Configure here.