Our Xamarin.Kinds iOS software is experiencing crashes with a particular exception: Deadly Exception: NSInternalInconsistencyException
Modifications to the format engine should not be carried out from a background thread after it has been accessed from the primary thread. The crashes happen when customers try and scroll the timepicker. Notably, this subject has emerged after customers up to date their iOS gadgets to variations 17.1.1 and 17.1.2.

Regardless of my efforts, I have never been in a position to replicate the issue on my bodily system or simulator. Nearly all of affected customers are positioned within the USA. We depend on Firebase Crashlytics to log these incidents. The connected screenshots are sourced from Crashlytics.

Steps Taken:

I’ve reviewed the threading in my code and ensured that UI updates are executed on the primary thread.
I’ve tried utilizing Machine.BeginInvokeOnMainThread, however the subject persists.

        {
            Machine.BeginInvokeOnMainThread(() =>
            {
                DateTime TodayDate = DateTime.Now;
                var dateSelect = calender.SelectedDate;
                //  DateTime MyDateTime = new DateTime(2000, 1, 1).Add(dtPicker.Time);
                DateTime MyDateTime = new DateTime(dateSelect.Yr, dateSelect.Month, dateSelect.Day).Add(dtPicker.Time);

                if (TodayDate > MyDateTime)
                {
                    string FormatedTime = string.Format("{0: hh:mm tt}", MyDateTime);

                    ObservationTime.Textual content = FormatedTime + " ";

                }
                else
                {
                    DisplayAlert(GlobalVariables.FoodAllergyFix, "DateTime can't be greater than present DateTime.", "OK");
                    dtPicker.Time = TodayDate.TimeOfDay;
                    string FormatedTime = string.Format("{0: hh:mm tt}", TodayDate);

                    ObservationTime.Textual content = FormatedTime + " ";

                }
            });
            

        }```

Has anybody else encountered an analogous downside with Xamarin.Kinds and iOS 17.1.1/17.1.2? Any insights into resolving this subject or ideas for additional troubleshooting can be tremendously appreciated.

Thanks!