Repository navigation
test: wait for hydrated workspace before Android screenshots - #8
Draft
buttercode101 wants to merge 1 commit into
Draft
buttercode101 wants to merge 1 commit into
buttercode101 wants to merge 1 commit into
Conversation
|
Deployment failed for project invoiceflow-za with the following error: Learn More: https://vercel.com/butters-projects-ad226a08?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
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 tablet acceptance artifact showed an initial 'Opening your workspace…' frame in the theme screenshot even though the later app-menu screenshot showed the workspace loaded. The current readiness helper accepts any heading and body length, which can pass before the local workspace has hydrated.
This tightens the emulator readiness gate to wait for the actual Overview hero heading and fail if the workspace error state is visible. The offline, theme, large-text and app-menu screenshots will therefore only be captured after the workspace content is rendered.
Test-only change; no app runtime code or user data changes.