Repository navigation
CI: the onLayout case waits for the size the card settles at - #426
Merged
Merged
Conversation
The manual run's iOS device run failed one case of the Platform screen: "view props: onLayout fires with the component's size: expected laid out, got "laid out at 370×0"". It passed the night before. The case took the first onLayout the card reported, and a component's first layout may come before its height: an intrinsic size waits for the JavaScript thread to apply it (limitations.md, "zero at mount, until then"). The case polls until the card reports a size, 10 s at most, and still says what it got last. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KaXTpjxQL34i1B21Jt4UMB
Fausto95
added
the
no-changeset
Claude
|
Deployment failed for project lucent with the following error: Learn More: https://vercel.com/faustino-kialungilas-projects?upgradeToPro=build-rate-limit |
|
Deployment failed for project website with the following error: Learn More: https://vercel.com/faustino-kialungilas-projects?upgradeToPro=build-rate-limit |
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
2 participants
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.
The manual run's iOS device run failed one case of the Platform screen:
"view props: onLayout fires with the component's size: expected laid
out, got "laid out at 370×0"". It passed the night before. The case
took the first onLayout the card reported, and a component's first
layout may come before its height: an intrinsic size waits for the
JavaScript thread to apply it (limitations.md, "zero at mount, until
then"). The case polls until the card reports a size, 10 s at most, and
still says what it got last.
Tested locally:
node scripts/sync-examples.tsandsync-examples.test.ts;pnpm -s check. The case runs on the simulator, nightly and in manual runs.Generated by Claude Code