SfExpander problem after update to 17.3.0.30

[Radoslaw Kubas]

Hello,

After nuggets updated to 17.3.0.30 my iOS app not starts anymore and I can see exception:

 System.ArgumentException: Could not create provider from the specified file

  at CoreGraphics.CGDataProvider..ctor (System.String file) [0x00032] in /Library/Frameworks/Xamarin.iOS.framework/Versions/13.6.0.12/src/Xamarin.iOS/CoreGraphics/CGDataProvider.cs:105 

  at Syncfusion.XForms.iOS.Expander.ExpanderHeader.CreateIndicatorView () [0x0000b] in <bd8a9138e9834c0c85b97e69e035897b>:0 

  at Syncfusion.XForms.iOS.Expander.ExpanderHeader.UpdateIconView () [0x00022] in <bd8a9138e9834c0c85b97e69e035897b>:0 

  at Syncfusion.XForms.iOS.Expander.SfExpander.InitializeExpanderViewContent () [0x00047] in <bd8a9138e9834c0c85b97e69e035897b>:0 

  at Syncfusion.XForms.iOS.Expander.SfExpander.InitializeViewLoaded () [0x00014] in <bd8a9138e9834c0c85b97e69e035897b>:0 

  at Syncfusion.XForms.iOS.Expander.SfExpander.SizeThatFits (CoreGraphics.CGSize size) [0x00020] in <bd8a9138e9834c0c85b97e69e035897b>:0 

  at Xamarin.Forms.Platform.iOS.ViewRenderer`2[TView,TNativeVi

ew].SizeThatFits (CoreGraphics.CGSize size) [0x00015] in D:\a\1\s\Xamarin.Forms.Platform.iOS\ViewRenderer.cs:85 

  at Xamarin.Forms.Platform.iOS.UIViewExtensions.GetSizeRequest (UIKit.UIView self, System.Double widthConstraint, System.Double heightConstraint, System.Double minimumWidth, System.Double minimumHeight) [0x00000] in D:\a\1\s\Xamarin.Forms.Platform.iOS\Extensions\UIViewExtensions.cs:30 

  at Xamarin.Forms.Platform.iOS.VisualElementRenderer`1[TElement].GetDesiredSize (System.Double widthConstraint, System.Double heightConstraint) [0x00000] in D:\a\1\s\Xamarin.Forms.Platform.iOS\VisualElementRenderer.cs:134 

Downgrade to 17.3.29 solved the problem.

Best regards,

Radek

[Gnana Priya Namasivayam]

Hi Radoslaw, 

 

Due to technical glitches, the nuget version 17.3.0.30 was published wrongly with mismatch assemblies hence it is crashing on your side. We will publish another nuget version for this week by December 5, 2019 and you can update to that version to resolve this issue. 

 

Regards, 

Gnana Priya N