Welcome to the Xamarin.iOS feedback portal. We’re happy you’re here! If you have feedback on how to improve the Xamarin.iOS, we’d love to hear it!

  • Check out the features or bugs others have reported and vote on your favorites. Feedback will be prioritized based on popularity.
  • If you have feedback that’s not listed yet, submit your own.

Thanks for joining our community and helping improve Syncfusion products!

3
Votes

Hi, 

The crash is reproducible on official Syncfusion Xamarin examples (Schedule project), v19.4.0.38. I manually upgraded SfSchedule NuGet up to the latest v19.4.0.42 and the issue still exists.

Steps to reproduce:

  1. Open the demo app and go to Drag and Drop screen
  2. Tap to any existing appointment to activate the Drag and Drop feature
  3. Drag the appointment to the previous week, then one more week back
  4. Still hold the appointment and drag it to the top of the calendar
  5. Autoscroll should be activated and the scheduler should scroll the time slots to the earlier hours
  6. The crash happens. 

The Day, Week, and Work Week views are affected. I also attached the short screen recording with the steps above.


The stack trace is here:

Syncfusion.SfSchedule.iOS.DragAndDropController.SetScrollPosition (Syncfusion.SfSchedule.iOS.SFDayView dayView)
Syncfusion.SfSchedule.iOS.DragAndDropController.EnableAutoScroll ()
Syncfusion.SfSchedule.iOS.DragAndDropController.NavigateScrollTimer_Elapsed ()
Syncfusion.SfSchedule.iOS.DragAndDropController.b__26_1 (Foundation.NSTimer )
NSTimerActionDispatcher.Fire (Foundation.NSTimer timer)
(wrapper managed-to-native) UIKit.UIApplication.UIApplicationMain(int,string[],intptr,intptr)
UIApplication.Main (System.String[] args, System.IntPtr principal, System.IntPtr delegate)
UIApplication.Main (System.String[] args, System.String principalClassName, System.String delegateClassName)
Application.Main (System.String[] args)


It is possible to avoid the crash for iOS by disabling auto-scroll.

SfScheduleView.DragDropSettings.AllowScroll = false;
Looking forward to the fix in the nearest NuGet releases :)