Repository navigation
fix(ios): don't surface RiveUIView's transient missing-drawable draw log as a LogBox error - #348
Merged
mfazekas merged 1 commit intoJul 17, 2026
Conversation
…log as a LogBox error
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.
Opening any Rive page in the Debug example app pops a LogBox red screen reading
[RiveUIView] [RiveUIView] Draw failed: missing drawable. The SDK'sRiveUIViewforce-draws its MTKView before Auto Layout has sized it, socurrentDrawableis nil for the first frame(s); it logs that transient condition at error level and rendering recovers on the next tick. rive-ios 6.21.1 is the latest release and upstreammainhas no change here, soRiveRuntimeLoggernow forwards this specific.viewmessage at debug instead of error.Also strips the tag prefix the SDK hardcodes into its message strings (it already passes the same tag separately), which caused the doubled
[RiveUIView] [RiveUIView]above.Verified on an iPhone 17 / iOS 26.5 simulator: unfixed build shows the red screen on Quick Start; with the fix the same
CAMetalLayer nextDrawable returning nilstill occurs in the device log but nothing is forwarded at error level, no LogBox appears, and the animation renders.