fix: iOS startup crash from FOLLY_NO_CONFIG on RN 0.80+ - #4
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Essentials Run ID: 📒 Files selected for processing (1)
Included review availability: 4 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 5 reviews per hour. 📝 SummarySummary by CodeRabbit
WalkthroughNitroPay now resolves the installed React Native version with ChangesReact Native Folly configuration
Priority: ➖ Normal Estimated code review effort: 2 (Simple) | ~10 minutes Change: Bug fix · Severity of issue fixed: Medium Merge Risk: ⚪ Minimal · up to The podspec avoids shell interpolation, fails on invalid React Native metadata, and applies the Folly flags only for older supported versions; no concrete merge-blocking risk remains. 🚥 Pre-merge checks | ✅ 6✅ Passed checks (6 passed)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@package/NitroPay.podspec`:
- Around line 26-39: Update the react_native_below_80 detection block to raise a
CocoaPods error when resolving or reading React Native’s package metadata fails
or returns an unusable version, rather than rescuing to false. Preserve the
existing version check and apply the Folly definitions only after successful
detection.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 19e432fd-d50d-4e30-857f-4bf22768a669
📒 Files selected for processing (3)
CHANGELOG.mddocs/docs/troubleshooting.mdpackage/NitroPay.podspec
Silent rescue-to-false could skip Folly flags on RN < 0.80 or hide a broken install. Raise during pod install instead, and compare versions with Gem::Version. Co-authored-by: Cursor <cursoragent@cursor.com>
865310c to
88f2ab5
Compare
Use Open3.capture3 with chdir so installation_root is not interpolated into a shell command during pod install. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Follow-up for CodeRabbit Security Check: replaced the backtick |
|
@coderabbitai review |
|
fix: iOS startup crash from FOLLY_NO_CONFIG on RN 0.80+
Summary
FOLLY_NO_CONFIGinNitroPay.podspecwhen React Native ≥ 0.80, where it mismatches the generatedfolly-config.hand aborts at launch (folly dynamic.cpp Check failed: 0).pod installif React Native cannot be resolved or its version cannot be parsed (no silent wrong-config fallback).Test plan
cd package && bun run typecheckcd package && bun run lintcd example && bunx expo prebuild --clean && bunx expo run:ios(confirm app launches on RN 0.80+)bun run docs:buildRisk
pod install, the install aborts with an explicit error instead of guessing Folly flags.Notes