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
MAUI is calling the setters of the properties unnecessarily when CollectionView/ListView is shown to screen. Even though they call the setter with the same value, this is a problem if it’s done on a RealmObject for which the current user doesn’t have permissions (compensating writes errors coming through). On iOS this also causes an error loop in some cases, probably due to cell recycling.
We need to modify WovenSetterMethodInfo to avoid calling the setter in case the new value is equal to the current value.
The code is ready for review, but there is a strange behaviour with sync
due to realm/realm-dotnet#3128. This can cause
some error loops on iOS in some specific situations
Co-authored-by: Ferdinando Papale <>
Co-authored-by: Chris Bush <chris.bush@10gen.com>
Co-authored-by: MongoCaleb <32645888+MongoCaleb@users.noreply.github.com>
MAUI is calling the setters of the properties unnecessarily when CollectionView/ListView is shown to screen. Even though they call the setter with the same value, this is a problem if it’s done on a RealmObject for which the current user doesn’t have permissions (compensating writes errors coming through). On iOS this also causes an error loop in some cases, probably due to cell recycling.
We need to modify
WovenSetterMethodInfo
to avoid calling the setter in case the new value is equal to the current value.Reported in dotnet/maui#12001
The text was updated successfully, but these errors were encountered: