Fix: iOS null exception occurs on Toolkit SfButton when text is null#386
Merged
Merged
Conversation
PaulAndersonS
approved these changes
Jun 1, 2026
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.
Root Cause of the Issue
This issue occurs when the SfButton text is set to null, causing a null exception during iOS text measurement.
The existing implementation directly creates an NSString using:
new NSString(text);On iOS, NSString does not accept null values, which leads to a null exception at runtime.
This scenario can happen when SfButton or its internal text measurement logic triggers measurement before the text is initialized or when text is explicitly null.
Description of Change
Added a null-coalescing safeguard:
text ??= string.Empty;Ensures that:
This change guarantees: