EFCore SQLite - Android - Error constructor call failed

[Reshiru]

SQLite database not useable in Xamarin.Forms with Android.
On try to initialize new DbContext error will be thrown.
Expected:
-> Generate database and resolve connection / object to the linked configurations

Exception message:
System.InvalidOperationException: A suitable constructor for type 'Microsoft.EntityFrameworkCore.Internal.DiagnosticsLogger`1[Microsoft.EntityFrameworkCore.DbLoggerCategory+Infrastructure]' could not be located. Ensure the type is concrete and services are registered for all parameters of a public constructor.

Steps to reproduce

Run the given solution

Issue_Droid.zip

Edit:
Constructor call inside MainPage.xaml.cs

Further technical details

EF Core version: (found in project.csproj or packages.config)
Operating system: Windows 10
IDE: Visual Studio 2017 15.5.6

[cwrea]

@Reshiru Your Android app project has its AndroidLinkMode set to Full, and so the linker has removed types from EF Core that appear not to be used from a static analysis perspective, but are actually required at run-time, accessed via reflection. Try changing your AndroidLinkMode to SdkOnly.

I have an adapted Xamarin app sample available here that demonstrates EF Core 2.0.1 working in a Xamarin.Forms Android app. The Android sample app uses SdkOnly linking.

FWIW, setting AndroidLinkMode to Full with EF Core is only likely to work when issue #10963 has been addressed.

[bipindalsaniya]

Hello Chris,

I have same issues. couldn't resolved it. i have tried to change AndroidLinkMode also.

[cwrea]

@bipindalsaniya I suggest you look at the sample I linked to previously. Compare your project settings to those in the sample. When I got the sample working with EF Core 2.0.1, I also posted about it in the Xamarin Forums.

[divega]

@cwrea based on your understanding, is there anything pending in this issue besides what is covered in #10963 (e.g. the fact that we don't have linker hints and that the developer may need to add their own)?

[divega]

Also @cwrea, I knew this class of issues affected Xamarin.iOS, but I wasn't aware that they affected Xamarin.Android as well. Can you confirm?

[divega]

@cwrea you can ignore my previous request for confirmation that this also affects Android development. I have read enough of your posts to understand this part now. Thank you for sharing all this information with everyone!