We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy. Image for the cookie policy date
close icon

SIGILL ExecutionEngineException

Hi,

When i run my application, and the specific line is executed ExcelEngine excelEngine = new ExcelEngine() i get the following exception:




Thanks


6 Replies

RC Ricardo Carvalho February 19, 2017 01:32 AM UTC

Forgot to say that everything works well in iphone 6, but in iphone 5 i get the exception.


SS Sridhar Sukumar Syncfusion Team February 20, 2017 12:38 PM UTC

Hi Ricardo, 
 
Thank you for contacting Syncfusion support. 
 
Unfortunately, the image link you have updated in the forum is broken. So we request you to share us the exception details once again, which will be helpful for us to investigate further on this and provide a prompt solution at the earliest. 
 
Regards, 
Sridhar S. 



RC Ricardo Carvalho February 21, 2017 12:54 AM UTC

Sry about the images. Below are two links to them. Thanks for the support.

https://drive.google.com/open?id=0BzzQcKMeRRWlQXZSV2RwLWJlUVk 

https://drive.google.com/open?id=0BzzQcKMeRRWlRWswazFiRlFzdHM 






VS Vikas Sekar Syncfusion Team February 21, 2017 12:48 PM UTC

Hi Ricardo,  
  
Thanks for your updates. 
 
We are unable to reproduce the reported issue at our end. We request you to check any of the following options to resolve this issue. 
 
 
1 
Run the project in the “Release” mode. 
 
2 
When using Syncfusion.XlsIO.Portable library in iOS application, the following settings must be done to execute in iOS devices.

Visual Studio: 
In Visual Studio, we can only execute in release mode for iOS device
by setting the link behavior field to Link SDK assemblies only.

Xamarin Studio (Recommended):   
 
Link behavior: Link SDK assemblies only (otherwise classes you need in Syncfusion.XlsIO.Portable.dll are linked away).   
     
Enable debugging: Unchecked (this is to create a smaller binary, since adding debug information makes it somewhat bigger).   
     
Applying these settings will execute the application properly in iOS device.    
You might face the following issues, if the above mentioned build options are missed out.    
You might get "Native linking error" while compiling.    
You might face runtime Exception ("System.TypeInitializationException").    
 
You can also refer to the ReadMe file for older Xamarin Studio version in the following link. 
 
3 
There is a solution to skip this issue by setting one of the following registrar options to the additional mtouch arguments in the project's iOS Build options: 
 
·         --registrar:static : default for device builds 
·         --registrar:dynamic : default for simulator builds 
·         --registrar:legacystatic : default for device builds until Xamarin.iOS 7.2.1 
·         --registrar:legacydynamic : default for simulator builds until Xamarin.iOS 7.2.1  
 
Please let us know that whether the above option resolve the issue. If you still experience the issue, we request you to share the following details which will help us to validate on this and provide a prompt solution at the earliest. 
 
1 
Xamarin version? 
iPhone 5 iOS version? 
iPhone 6 iOS version? 
2 
Code snippet used in the program. 
3 
Confirm us if you can run Syncfusion’s sample browser (Xamarin). If the sample browser runs proper and deploy the samples in devices, then there is no issue with the library. You may need to revisit your project to resolve this. 
 
Please let us know if you need any clarification. 
  
Regards,  
Vikas 



RC Ricardo Carvalho February 25, 2017 04:00 PM UTC

Once again thx for responding. The solution for me is to run in release mode or uncheck the enable debugging, this for the iphone 5 because when running in iphone 6 everything works fine. The problem with this, is that, it becomes hard to detect problems.


SS Sridhar Sukumar Syncfusion Team February 27, 2017 11:21 AM UTC

Hi Ricardo, 
 
Thank you for updating us. 
 
This issue has been raised in iPhone 5 due to larger assembly size. We have reported the issue to Xamarin team and they have given the workaround solution which we have shared in the last update. This issue has been rectified in sixth-generation devices. 
 
Regards, 
Sridhar S. 


Loader.
Live Chat Icon For mobile
Up arrow icon