Bug 16686 - TaskyAndroid:System.TypeInitializationException
Summary: TaskyAndroid:System.TypeInitializationException
Status: RESOLVED NORESPONSE
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: 4.2.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Jonathan Pryor
URL:
Depends on:
Blocks:
 
Reported: 2013-12-09 22:39 UTC by Ivan, Chung
Modified: 2017-08-07 20:42 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED NORESPONSE

Description Ivan, Chung 2013-12-09 22:39:52 UTC
/Downloads/Tasky/Android_Starter/TaskyAndroid: Error XA0000: Unexpected error - Please file a bug report at http://bugzilla.xamarin.com. Reason: System.TypeInitializationException: An exception was thrown by the type initializer for Ionic.Zip.ZipFile ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.StackOverflowException: The requested operation caused a stack overflow. (XA0000) (TaskyAndroid)
Comment 2 Jon Douglas [MSFT] 2017-08-07 20:42:27 UTC
Because we have not received a reply to our request for more information we are closing this issue. If you are still encountering this issue, please reopen the ticket with the requested information. Thanks!