Demo the 1.0.1 lifecycle events

[yosriady]

SDK 1.0.1 ships the Segment lifecycle set (getformo/sdk-react-native#69, #70, #71), so the example can finally exercise it. Bumped to ^1.0.1 and added a Lifecycle Events card.

What's demoed

Application Installed / Opened / Backgrounded / Foregrounded and Deep Link Opened are autocaptured — nothing to add. The card covers the two that cannot be:

• Push Notification Received / Tapped / Bounced — push delivery is invisible to JavaScript without a native module, so these are explicit calls. Noted inline that in a real app they live inside the push handler rather than behind a button.
• Trigger Crash — behind a confirmation, throwing asynchronously so the SDK's global handler reports Application Crashed. In development the redbox still appears afterwards; that's the handler chain working, not a failure.

Both opt-in autocapture flags (foregrounded, crashes) are enabled in config/formo.ts, documented inline with why they're opt-in in the first place.

pnpm

Excluded our own package from minimumReleaseAge. That guard exists to blunt supply-chain attacks on third-party deps; applying a 7-day delay to our own SDK stops the example from demonstrating a fresh release — which is the entire point of it.

End-to-end verification

Ran against the published 1.0.1 on all three targets, confirming events in Tinybird each time.

	Web	iOS sim	Android emu
app://com.formo.analytics.demo/<Screen>	✓	✓	✓
Application Installed / Opened	✓	✓	✓
Deep Link Opened (after Application Opened)	✓	✓	✓
Application Backgrounded → Foregrounded	—	✓	—
Push Received / Tapped / Bounced	✓	—	—
Application Crashed	✓	—	—

Application Foregrounded fired on iOS only where I could drive a real background→foreground transition (simctl launch com.apple.springboard, then relaunch). The sequence was exactly as designed: Opened → Backgrounded → Opened (from_background: true) → Foregrounded.

For the crash I invoked the installed handler directly rather than tapping the button — no tap driver was available for the iOS simulator, and on web a real throw risks a blocking dialog. ErrorUtils.getGlobalHandler()(new TypeError(...), true) exercises the identical code path. The error re-raised to the previous handler (proving the chain is intact) and the event landed in Tinybird with the full payload:

event=Application Crashed  message="e2e synthetic crash"  name=TypeError
fatal=true  stack_truncated=false  stack_len=54

Not verified end-to-end: the crash and push buttons via actual taps on a device. Both are covered by unit tests in the SDK (12 for the crash handler alone, including the chain invariant).

14 tests pass, typecheck and lint clean.

🤖 Generated with Claude Code

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[socket-security]

Dependency limit exceeded — report not shown.

This pull request scan exceeded the 10,000-dependency limit applied to this scan, so the results are incomplete and may be inaccurate. To avoid reporting false positives, Socket has not posted a report.

Upgrade your plan to raise the dependency limit and get complete reports, or view the partial scan in the dashboard.

Socket is always free for open source. If this is a non-commercial open source project, contact us to request a free Team account.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9f8ec4676a

ℹ️ 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".

[chatgpt-codex-connector]

Handle crash confirmation outside Alert on web

When this example is run through the web script, React Native Web's Alert.alert displays the browser alert but does not support the custom button callbacks, so the Throw handler is never invoked and the new Trigger Crash demo cannot emit Application Crashed. Use a web-specific confirmation path such as window.confirm, or a cross-platform modal whose buttons invoke the callback.

Useful? React with 👍 / 👎.