You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
mobile: possible white flash and skipped dismiss between native splash and PixelDismiss overlay #1794
While recording the splash variants from Release builds of main (#1763) on an iOS 27 simulator (iPhone 18 Pro), many cold starts showed a fully white screen for about 0.3–0.6 s between the native purple splash and the purple overlay. In some takes the app then appeared with no dismiss animation at all. Evidence: scratchpad/splash-x-post/raw/1-dissolve-take2.mov (about 4.9 s) and raw/ripple-half-2.mov. The host's load average was 480–610 during recording, so it may be simulator-only.
Expected
The native splash hands off to the overlay's matching first frame with no white frame, and the dismiss always plays on a cold start, except under Reduce Motion or the 300 ms fallback.
To check
Reproduce on a real device with TestFlight build 16, which ships this splash.
If it reproduces, look for a gap between SplashScreen.hide and the overlay's first onDisplay, and for the fallback firing before the overlay mounts under load.
Current-source triage at 6083332: the PixelDismiss overlay and its 300 ms display fallback still exist. Normal splash hiding remains in SplashOverlay after image onDisplay or that fallback; the root layout hides it separately only for the error boundary. The recent Home navigation fix (#4738) removes app-wide splash scaling but does not establish that this cold-start handoff issue is fixed. No source workaround or extra delay is justified by the existing evidence. The remaining reproduction requirement is a cold-launch recording of the affected released/TestFlight app on an approved physical phone, including app build/version, Reduce Motion setting and whether the white interval or skipped dismiss occurs. A development-simulator pass would not satisfy the original physical-release check; preserve this issue until that evidence is available.
Closing the historical splash flash report. The recorded behavior was tied to an earlier build and has no current physical release-build reproduction. Reopen with the affected build, device, Reduce Motion state and a cold-launch recording if it returns.
Activity
janicduplessis commentedon Nov 1, 2026
Current-source triage at 6083332: the PixelDismiss overlay and its 300 ms display fallback still exist. Normal splash hiding remains in SplashOverlay after image onDisplay or that fallback; the root layout hides it separately only for the error boundary. The recent Home navigation fix (#4738) removes app-wide splash scaling but does not establish that this cold-start handoff issue is fixed. No source workaround or extra delay is justified by the existing evidence. The remaining reproduction requirement is a cold-launch recording of the affected released/TestFlight app on an approved physical phone, including app build/version, Reduce Motion setting and whether the white interval or skipped dismiss occurs. A development-simulator pass would not satisfy the original physical-release check; preserve this issue until that evidence is available.
janicduplessis commentedon Nov 14, 2026
Closing the historical splash flash report. The recorded behavior was tied to an earlier build and has no current physical release-build reproduction. Reopen with the affected build, device, Reduce Motion state and a cold-launch recording if it returns.