960628 - Application crashes when setting ItemSpacing and ExpandMode using Global Styling

[SanjaySF4372]

Bug Description
Application crashes when setting ItemSpacing and ExpandMode using Global Styling in Accordion control.

Root Cause
When setting the API in global styling ,while loading it calls the its API property changed methods first so in that items were not loaded .So items become null then the exception occurs.

Ticket ID
https://support.syncfusion.com/agent/tickets/731608

Task ID
https://dev.azure.com/EssentialStudio/Mobile%20and%20Desktop/_workitems/edit/960628

Is Breaking issue?
No

Solution description
Added the condition if the IsViewLoaded is false then it should return in the propertychanged methods.

Output screenshots

Windows:

AccordionHeader.2025-06-17.10-18-21.mp4

Android:

Android.Emulator.-.pixel_7_-_api_33_5554.2025-06-17.10-17-12.mp4

Mac:

SYNCMACN-46802.local.and.18.more.pages.-.Work.-.Microsoft.Edge.2025-06-16.19-05-52.mp4

iOS:

SYNCMACN-46802.local.and.18.more.pages.-.Work.-.Microsoft.Edge.2025-06-16.19-05-08.mp4

Areas affected and ensured
No areas were affected.

Test cases
Tested all the API in Global Styles,Explicit Styles,Implicit Styles,Constructor ,OnAppearing,App.Xaml and Loaded Event.

Does it have any known issues?
No

MR CheckList

• Have you ensured in iOS, Android, WinUI, and macOS(if supported)? Yes
• If there is any API change, did you get approval from PLO through JIRA Tasks? No
• Is there any existing behavior change of other features due to this code change? No
• Did you perform the automation / manual testing against your fix?
• Did you record this case in the unit test or UI test? Yes
• Have you suppressed any warning or binding errors? No
• Is there any existing behavior change of other features due to this code change? No
• Does it need localization? If so did you ensure the cases mentioned in this link? No
• Whether the new APIs and its comments are added as per standard? No
• Did you ensure the cases mentioned in this link? Not Applicable
• Did you ensure the fix (if applicable) met accessibility requirements? Not Applicable
• If you added any interaction related code, have you used touch and gesture APIs from core project? Not Applicable
• Does it contain code that reflects any internal framework API? Not Applicable
• Did you ensure the cases mentioned in this link? Not Applicable
• Did you ensure RTL? Not Applicable
• Did you test the memory leak with the fix? Not Applicable
• Did you ensure the ? Check this link to know more about performance optimization and how to automate? Not Applicable
• If you use a third-party package, did you get approval to use it? If not, please get approval before merging. Not Applicable

[bricefriha]

I struggle understanding why we are removing this 🙂

[FarjanaParveen]

@bricefriha - This part of the code was not relevant to the current issue and has been removed, as it was unnecessary.