Repository navigation
Conversation
Pin bugsee/spm and feedback-spm to 7.0.1 and update Package.resolved (revision 15553bd). No API changes needed. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: true
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. CodeRabbit Verify
|
This branch has not been deployed
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.
Pins
bugsee/spmandbugsee/feedback-spmto 7.0.1 (native-versions.json, bothPackage.swiftfiles,Package.resolvedat revision15553bd), plus the tests and docs that name the pin. No source changes were needed.Verified on the iPhone 17 Pro simulator (CocoaPods delivery, fresh build, 7.0.1 confirmed by the harness version guard)
yarn install --immutableOKBugseeRNSupportXCTests: 351, 0 failuressecure-perfandsecure-componentfail the same way as on 7.0.0 (Debug timing budgets;secure-componentalso fails on beta7).Open item: possible 7.0.1 regression, why this is a draft
app-state›[N-10][FLOW-33] 300 s in the background, then foregroundfails on 7.0.1 (reproduced twice, once in the full run and once alone) and passes on 7.0.0 on the same simulator and harness (A/B run, 7/7). The failing assertion isapp-state.test.ts:310: the video has no dark frame before the first bright one, so after the 300 s gap the recording starts at the white stage instead of containing the earlier dark app frames. Everything else in the suite passes, including the 5 s background cases. I haven't established whether this is an intended 7.0.1 change to background video handling or a regression; it needs the iOS SDK team's answer.Not run: physical device (KRSFT), Android, SwiftPM delivery path, Release
secure-perf.🤖 Generated with Claude Code