-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Xamarin: iOS NotImplementedException during query #7158
Comments
@rowanmiller - any way to determine if this is something that is scheduled to be addressed in the near future or that will take a while to get to? |
We don't have a schedule for this yet. We need to work with the Xamarin team to work out the best course of action. |
Perhaps this is related: https://bugzilla.xamarin.com/show_bug.cgi?id=32180#c3 |
Hello @rowanmiller Faced the same issue on iOS platform. Do you have any resolution here or at least plan when it can be fixed? Thanks, |
This fix will be included in a future version of Mono... there aren't any specific dates around when the fix will ship yet. |
Hi @rowanmiller |
Hey Rowan, Diego, Just wondering if there's any update on this re: Roadmap/Time-to-fix. The original bug over on the the xamarin bugzilla hasn't had any update in months. And the only mention of Xamarin on the EFCore Road map (https://github.com/aspnet/EntityFramework/wiki/Roadmap) is an acknowledgement that it doesn't work in all scenarios. Just wondering if you can provide the community with a formal update, or simply acknowledge that this is far enough down the priority list, that anyone trying to build xamarin apps targetting IOS should consider using something else in the short term. Cheers for all the efforts. Aside from this one bugbear, it looks great 👍 |
Hello everyone, I just wanted to let you know, my application used to get that error but after updating Xamarin with the beta version, I can migrate, add and query data successfully. It seems like Mono 5.0 resolves the NotImplementedException issue but I didn't test all the EF features. Tested with: |
Thanks @dominicboutin. That is consistent with what we have heard from the Xamarin team. I am glad to hear that you were able to test the fix. Do you know which exact version of Xamarin iOS you are using? |
@divega Xamarin.IOS 10.10.0.19 |
Thanks for the info @dominicboutin. I've yet to test this. Are you using a Mac? I'm not sure how to update to the latest mono. I don't see an update on my Visual Studio 2017 yet. |
@abdu292 according to these Xamarin release notes, Xamarin iOS 10.10 should be included in Visual Studio 2017 15.2 Preview 2. |
Thank you @divega. I'll try that out. On vacation right now but I'll post an update as soon as I have access to my computer. |
Currently this works for Android only and not for iOS. See dotnet/efcore#7158 for details
We are closing this issue as we believe the root cause has been removed in newer versions of Xamarin iOS. That said, support for Xamarin is still considered a work in progress. Please refer to the call for help at #4269 (comment), and create new issues for any problems you find. |
Here's a tip for anybody else trying to get EF Core working on the latest Xamarin.iOS bits (10.10+): While the blocker issue ( To fix, you need to tell the Xamarin linker not to exclude such things used by EF Core. In a sample I updated, the following did the trick to get it to run successfully on-device. I'll note that more complex usage of EF Core is likely to require a few more types and methods added to this:
|
@cwrea any idea what these other types are? I'm experiencing this and the file didn't seem to stop it. How do i determine which types are throwing the errors.
|
@Kilowhisky Looking at your exception stack trace, the exception indirectly originates in Next, look at the source for that class here. Search for the word "static" and you will see all of the different static fields declared, with their initialization code inline. Notice that many of those call I presume that you need to tell the linker about additional types referenced by those |
I know this thread is pretty old, but I'm trying to implement this code into my Xamarin.Forms iOS project in order to solve the issues with the deprecated
In this case, the code wouldn't compile: it yielded the error:
So instead I tried changing the -mtouch argument to say
In this case, my code compiles but doesn't seem to execute the linkskip arguments; it continues to throw |
Reported by @econner20 - see #4269 (comment)
I am having an issue with iOS. I used the example models and context from the example @polkduran provided and was successful in getting EF to work with Android, UWP and a Winforms target. However when I run the same Xamarin project/NETStandard assembly the iOS target is throwing the following exception:
Unhandled Exception:
System.NotImplementedException: Interpreter of ref types
when trying to execute the following:
The text was updated successfully, but these errors were encountered: