- Home
- Forum
- Xamarin.iOS
- SfCalendar missing constructor for xamarin designer
SfCalendar missing constructor for xamarin designer
This causes a view with a SfCalendar in it to not work anymore when editing in the designer, after removing the SfCalendar it works again.
Custom components not being rendered because problems were detected
The log in console:
ObjCRuntime.RuntimeException: Failed to marshal the Objective-C object 0x7fce2c939b10 (type: Syncfusion_SfCalendar_iOS_SFCalendarMonthDayView). Could not find an existing managed instance for this object, nor was it possible to create a new managed instance (because the type ‘Syncfusion.SfCalendar.iOS.SFCalendarMonthDayView’ does not have a constructor that takes one IntPtr argument).
SIGN IN To post a reply.
6 Replies
MS
Muniappan Subramanian
Syncfusion Team
April 27, 2020 09:39 AM UTC
Hi Ravi,
Thank you for contacting Syncfusion support.
Currently, we are analyzing the mentioned issue “SfCalendar missing constructor for Xamarin designer”. We will validate and update you the further details in two business days (April 29, 2020). We appreciate your patience until then.
Regards,
Muniappan S.
SS
SaiGanesh Sakthivel
Syncfusion Team
April 29, 2020 03:14 PM UTC
Hi Ravi,
Thank you for the patience.
We have checked and able to replicate the mentioned issue “SfCalendar missing constructor for Xamarin designer” and we have logged a bug report for the same. We will fix and provide you the issue fix on or before May 19,2020. We appreciate your patience until then.
You can track the status of this report through the following feedback link,
Note: The provided feedback link is private, you need to login to view this feedback.
Regards,
SaiGanesh Sakthivel
SS
SaiGanesh Sakthivel
Syncfusion Team
May 19, 2020 03:32 PM UTC
Hi Ravi,
Sorry for the Inconvenience caused.
Currently we are fixing the reported issue “SfCalendar missing constructor for Xamarin designer” from our end and we regret that we need some more time to fix this issue. We will provide patch for this issue on or before June 2, 2020 and We will include this fix in our upcoming 2020 Volume 2 release which is planned to roll out in the month of July, 2020. We appreciate your patience until then.
Regards,
SaiGanesh Sakthivel
SS
SaiGanesh Sakthivel
Syncfusion Team
June 2, 2020 03:33 PM UTC
Hi Ravi,
We have fixed the mentioned issue “SfCalendar missing constructor for Xamarin designer” and the patch for the issue fix is following by. Before installing the patch, kindly remove bin and obj folders from all the projects of solution and clear NuGet cache.
Custom Assemblies: http://syncfusion.com/Installs/support/patch/18.1.0.52/1114074/F153627/SyncfusionPatch_18.1.0.52_1114074_6022020095946296_F153627.zip
Kindly find the below link to clear NuGet cache,
Installation Direction:
{Syncfusion Installed location} \Essential Studio\18.1.0.52\Xamarin\lib\ios\Syncfusion. SfCalendar.XForms.iOS.dll
Disclaimer:
Please note that we have created this patch for version 18.1.0.52 specifically to include the issue. We will include the issue fix in our upcoming Weekly NuGet release. We appreciate your patience until then. We appreciate your patience until then.
Regards,
SaiGanesh Sakthivel
SS
SaiGanesh Sakthivel
Syncfusion Team
July 7, 2020 03:45 PM UTC
Hi Ravi,
We are glad to announce that our Essential Studio 2020 Volume 2 Release v18.2.0.44 is rolled out and the issue “SfCalendar missing constructor for Xamarin designer" is available for download under the following link.
Feedback Link: https://www.syncfusion.com/feedback/13954/sfcalendar-missing-constructor-for-xamarin-designer
We thank you for your support and appreciate your patience in waiting for this release. Please get in touch with us if you would require any further assistance.
Regards,
SaiGanesh Sakthivel
PA
paulwings
April 5, 2022 05:04 AM UTC
When you provided a constructor for your class that takes arguments, the compiler no longer creates an empty constructor. Therefore, you cannot call an empty constructor because it does not exist. You would need to explicitly write the constructor that takes 0 arguments in your class's code. The constructor of the inheritance class needs to construct the base class first. since the base class does not have a default constructor (taking 0 arguments) and you are not using the non-default constructor you have now, this won't work. so either
- Add a default constructor to your base class, in which case the code of the descending class needs no change; or
- Call the non-default constructor of the base class from the constructor of the descending class, in which case the base class needs no change.
SIGN IN To post a reply.
- 6 Replies
- 4 Participants
-
RA Ravi
- Apr 24, 2020 11:33 AM UTC
- Apr 5, 2022 05:04 AM UTC