You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the Syncfusion SfShimmer control in a .NET MAUI application to indicate the loading state within a CollectionView, the shimmer effect fails to display during a pull-to-refresh operation on Android. Instead of showing the shimmer wave or placeholder effect, the CollectionView remains blank until the items are loaded. However, the SfShimmer control works as expected on iOS and Windows platforms, where the shimmer effect displays correctly during the loading process. This issue appears to be platform-specific and affects the user experience on Android.
Steps to Reproduce
Clone the repository from the provided link: [https://github.com/malsabi/ShimmerIssue].
Open the project in Visual Studio.
Build and run the application on an Android emulator or physical device.
Trigger the pull-to-refresh action on the CollectionView.
Note: Version with bug is only showing 1.1 and 1.2 but I'm using 1.3
Version with bug
1.0.2
Is this a regression from previous behavior?
No, this is a new issue
Last Known Working Version
1.0.2
Affected platforms
Android
Affected Platform Versions
No response
Have you found a workaround?
No workaround.
Relevant log output
The text was updated successfully, but these errors were encountered:
Description
When using the Syncfusion SfShimmer control in a .NET MAUI application to indicate the loading state within a CollectionView, the shimmer effect fails to display during a pull-to-refresh operation on Android. Instead of showing the shimmer wave or placeholder effect, the CollectionView remains blank until the items are loaded. However, the SfShimmer control works as expected on iOS and Windows platforms, where the shimmer effect displays correctly during the loading process. This issue appears to be platform-specific and affects the user experience on Android.
Steps to Reproduce
Note: Version with bug is only showing 1.1 and 1.2 but I'm using 1.3
Version with bug
1.0.2
Is this a regression from previous behavior?
No, this is a new issue
Last Known Working Version
1.0.2
Affected platforms
Android
Affected Platform Versions
No response
Have you found a workaround?
No workaround.
Relevant log output
The text was updated successfully, but these errors were encountered: