You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue with specflow 3.9.22 in visual studio Mac. System.Reflection.TargetInvocationException : Exception has been thrown by the target of an invocation.
#56
I am facing below issue while run the test case with specflow 3.9.22 plugin in visual studio Mac
Seems like Xamarin.UITest wasn't adjusted to SpecFlow 3.9 yet as Specflow team feedback. can i know the release version that will support specflow 3.9? or
when will be available to use?
or how can i resolve this issue?
Specification
Specflow - 3.9.22
Xamarin.UITest - 3.0.19
Visual Studio : Visual Studio Community 2019 for Mac
Version 8.10.4 (build 11)
Note: I have also tried with latest Xamarin.UITest version 3.1.0
System.Reflection.TargetInvocationException : Exception has been thrown by the target of an invocation.
----> System.TypeLoadException : VTable setup of type Xamarin.UITest.SpecFlow.Shared.TestTracerDecorator failed
at System.Reflection.RuntimeMethodInfo.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x0007e] in /Users/builder/jenkins/workspace/build-package-osx-mono/2020-02/external/bockbuild/builds/mono-x64/mcs/class/corlib/System.Reflection/RuntimeMethodInfo.cs:409
at System.Reflection.MethodBase.Invoke (System.Object obj, System.Object[] parameters) [0x00000] in /Users/builder/jenkins/workspace/build-package-osx-mono/2020-02/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/Reflection/MethodBase.cs:53
at Xamarin.UITest.Events.EventManager.TriggerAfterAppStarted (Xamarin.UITest.IApp app) [0x00066] in <17bc64ecb1ef48f9b44fb25c0bb4158c>:0
at Xamarin.UITest.Events.EventManager.AfterAppStarted (Xamarin.UITest.IApp app) [0x00000] in <17bc64ecb1ef48f9b44fb25c0bb4158c>:0
at Xamarin.UITest.Configuration.iOSAppConfigurator.StartApp (Xamarin.UITest.Configuration.AppDataMode appDataMode) [0x0001c] in <17bc64ecb1ef48f9b44fb25c0bb4158c>:0
The text was updated successfully, but these errors were encountered:
I am facing below issue while run the test case with specflow 3.9.22 plugin in visual studio Mac
Seems like Xamarin.UITest wasn't adjusted to SpecFlow 3.9 yet as Specflow team feedback. can i know the release version that will support specflow 3.9? or
when will be available to use?
or how can i resolve this issue?
Specification
Specflow - 3.9.22
Xamarin.UITest - 3.0.19
Visual Studio : Visual Studio Community 2019 for Mac
Version 8.10.4 (build 11)
Note: I have also tried with latest Xamarin.UITest version 3.1.0
System.Reflection.TargetInvocationException : Exception has been thrown by the target of an invocation.
----> System.TypeLoadException : VTable setup of type Xamarin.UITest.SpecFlow.Shared.TestTracerDecorator failed
at System.Reflection.RuntimeMethodInfo.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x0007e] in /Users/builder/jenkins/workspace/build-package-osx-mono/2020-02/external/bockbuild/builds/mono-x64/mcs/class/corlib/System.Reflection/RuntimeMethodInfo.cs:409
at System.Reflection.MethodBase.Invoke (System.Object obj, System.Object[] parameters) [0x00000] in /Users/builder/jenkins/workspace/build-package-osx-mono/2020-02/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/Reflection/MethodBase.cs:53
at Xamarin.UITest.Events.EventManager.TriggerAfterAppStarted (Xamarin.UITest.IApp app) [0x00066] in <17bc64ecb1ef48f9b44fb25c0bb4158c>:0
at Xamarin.UITest.Events.EventManager.AfterAppStarted (Xamarin.UITest.IApp app) [0x00000] in <17bc64ecb1ef48f9b44fb25c0bb4158c>:0
at Xamarin.UITest.Configuration.iOSAppConfigurator.StartApp (Xamarin.UITest.Configuration.AppDataMode appDataMode) [0x0001c] in <17bc64ecb1ef48f9b44fb25c0bb4158c>:0
The text was updated successfully, but these errors were encountered: