Repository navigation
Allow configure() on an idle SDK instance - #63
Merged
Merged
Conversation
The assert was inverted: it rejected the empty (idle) status its message says is required, so any debug app calling configure() on a fresh instance crashed at startup. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QZi3f27gbhPqhG91ngbdVe
rayliverified
added a commit
that referenced
this pull request
Oct 15, 2026
The assert was inverted: it rejected the empty (idle) status its message says is required, so any debug app calling configure() on a fresh instance crashed at startup.
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.
Before: in a debug build, calling
Codelessly.instance.configure()on a fresh instance failed an assert and the app crashed at startup. The CodelesslyEditor prod flavor run withflutter runnever rendered because of this.After:
configure()works on an idle instance, as the assert message already says it should. It still asserts when the SDK is loading, loaded or errored.How: the assert checked
status is! CEmpty, which is the opposite of its message. It now acceptsCEmptyorCConfigured. Release builds were not affected because asserts are stripped there.🤖 Generated with Claude Code
https://claude.ai/code/session_01QZi3f27gbhPqhG91ngbdVe
Generated by Claude Code