Fix Crashlytics crash: "Null check operator used on a null value" in MessageInputWidget #1362
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.
Fixes a crash where
setStatewas being called after theMessageInputWidgetwas disposed, causing the error "Null check operator used on a null value" originating fromState.setStatein framework.dart.Root Cause
The crash occurred when:
getSharedText().then(_handleSharedData)resolved after the widget was disposedSystemChannels.lifecyclehandler triggeredonDataReceivedcallback on a disposed state objectBoth scenarios resulted in
_handleSharedDatacallingsetState()on a disposed widget, where_element!is null post-dispose.Changes Made
lib/components/message_input.dart
!mountedin_handleSharedData()before callingsetState()lib/share_channel.dart
onDataReceivedmay be null if listener is disposedResult
The fix is minimal and surgical, addressing only the disposal race condition without affecting normal operation.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.