Repository navigation
[CI] (714adde) react-native/expo-react-native-hacker-news - #5180
Closed
wizard-ci-bot[bot] wants to merge 3 commits into
Closed
wizard-ci-bot[bot] wants to merge 3 commits into
wizard-ci-bot[bot] wants to merge 3 commits into
Conversation
Author
|
Now I have all the context needed. The SDK's PR Evaluation ReportSummaryThis PR integrates PostHog into an Expo React Native Hacker News reader app. It adds the
Confidence score: 5/5 🧙
File changes
App sanity check
|
| Criteria | Result | Description |
|---|---|---|
| App builds and runs | Yes | No syntax errors, valid TypeScript, all imports resolve |
| Preserves existing env vars & configs | Yes | Existing app.json preserved, app.config.js extends it |
| No syntax or type errors | Yes | All PostHog API usage matches verified SDK types |
| Correct imports/exports | Yes | posthog-react-native and expo-constants imports are correct |
| Minimal, focused changes | Yes | All changes are PostHog-related; endpoint refactor is minor |
| Pre-existing issues | None | Base app appears clean |
Issues
- Endpoint refactoring: The
api/endpoints.tsfile consolidates 4 separate fetch functions into one parameterizedgetStories()helper. While it makes the logging addition cleaner, the refactoring itself is not strictly required for PostHog. [LOW]
Other completed criteria
- Environment variables documented in
.env.example .envadded to.gitignoreapp.config.jscorrectly passes env vars through Expo'sextraconfig- Build configuration valid — peer dependencies (
expo-device,expo-file-system,expo-localization) included
PostHog implementation ⚠️
| Criteria | Result | Description |
|---|---|---|
| PostHog SDKs installed | Yes | posthog-react-native v4.44.0 with required peer deps |
| PostHog client initialized | Yes | new PostHog(projectToken, { host, ... }) with graceful null fallback |
| capture() | Yes | 8+ meaningful capture calls across story, comment, and navigation flows |
| identify() | N/A | App is a read-only HN client with no authentication system |
| Error tracking | Yes | errorTracking: { autocapture: { uncaughtExceptions: true, unhandledRejections: true } } |
| Reverse proxy | N/A | Mobile SDK — reverse proxy only benefits browser-based posthog-js |
| Screen views | No | captureScreens: false explicitly disables screen view tracking |
| All targets initialized | Yes | posthog-react-native handles iOS, Android, and Expo Web from a single init |
Issues
- Screen views disabled: The
PostHogProviderautocapture config setscaptureScreens: false, which means no screen view events will be sent. For a multi-screen navigation app (home → story details → user profiles → comments), screen views are essential for understanding user navigation patterns and building screen-based funnels. SetcaptureScreens: trueor remove the property to use the default. [CRITICAL]
Other completed criteria
- API key loaded from environment variable via
expo-constants→app.config.js→POSTHOG_PROJECT_TOKEN - Host correctly configured via
POSTHOG_HOSTenv var captureAppLifecycleEvents: trueenabled for mobile lifecycle tracking- Logging configured with
serviceNameandserviceVersion - PostHog client is properly null-guarded with
posthog?optional chaining throughout - Dev-mode warnings for missing configuration
PostHog insights and events ✅
| Filename | PostHog events | Description |
|---|---|---|
app/index.tsx |
story_feed_selected |
Tracks which feed type (top/best/ask/show) the user selects |
app/[itemId].tsx |
user_profile_opened, external_story_opened, discussion_opened |
Tracks user navigation from story detail page |
components/posts/Post.tsx |
external_story_opened, discussion_opened |
Tracks story list interactions — opening external links vs discussions |
components/comments/comment.tsx |
user_profile_opened, discussion_opened |
Tracks comment-level interactions — viewing authors and reply threads |
api/endpoints.ts |
Log events via posthogLog.info() |
Logs API requests for feed, item, and user data |
lib/posthog.ts |
captureException (autocapture) |
Automatic exception and unhandled rejection tracking |
Issues
- No issues with event quality. Events are well-structured with consistent naming and meaningful properties.
Other completed criteria
- Events represent real user actions (browsing stories, opening links, viewing profiles)
- Events enable product insights — can build funnels: feed selection → story open → external link / discussion
- Events include contextual properties (
source,content_type,story_type) - No PII in event properties
- Consistent snake_case naming convention
Reviewed by wizard workbench PR evaluator
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated wizard CI run
Source: context-mill-pr
Trigger ID:
714addeApp:
react-native/expo-react-native-hacker-newsApp directory:
apps/react-native/expo-react-native-hacker-newsWorkbench branch:
wizard-ci-714adde-react-native-expo-react-native-hacker-newsWizard branch:
mainContext Mill branch:
fix/skills-project-get-tokenPostHog (MCP) branch:
masterTimestamp: 2026-11-16T15:37:42.604Z
Duration: 569.7s
YARA Scanner