unauthorized access to /system/lib/libsqlite.so

[Drew-E]

When the library makes it's connection the database, the following error occurs. Interestingly, the sample apple displays the pop-up after resuming the app from a sleep state. My app displays the error on app start (which is when I make the first connection to the database). The popup does not actually prevent the database from being functional and persisting data across app starts/closures (which makes sense given the error below). Even so, it's not feasible to deploy an app that shows a warning pop-up on app start. It works fine with the VS android emulators.

Device Info
Motorola Droid Turbo 2
OS Version 7.0

Pop-Ups

Error Message
Time Device Name Type PID Tag Message
07-17 21:22:50.152 Motorola XT0000 Warning 23395 linker library "/system/lib/libsqlite.so" ("/system/lib/libsqlite.so") needed or dlopened by "/data/app/Mono.Android.DebugRuntime-1/lib/arm64/libmonosgen-32bit-2.0.so" is not accessible for the namespace "classloader-namespace" - the access is temporarily granted as a workaround for http://b/26394120, note that the access will be removed in future releases of Android

[MelbourneDeveloper]

I am getting the same error on sleep as well, so it's something that needs to be sorted out.

In order to log details, try setting up USB debugging on your Android phone, and then access the Android log here in VS 2017:

Image

[MelbourneDeveloper]

Also, other people have encountered this problem with other SQLite wrappers. It looks as though it's a problem in Android platform class. This thread has a lot of information:

https://forums.xamarin.com/discussion/78234/android-libmonosgen-library-sqlite-problems-with-app-native-libraries

Apparently, this NuGet package fixes the problem in the PCL library:
https://www.nuget.org/packages/SQLite.Net.Platform.XamarinAndroidN

It's unfortunate that I can't see the code for this library. When I can get hold of this code, I should be able to see where the bug is and fix it.

[MelbourneDeveloper]

I think the answer lies here:
https://developer.xamarin.com/releases/android/xamarin.android_7/xamarin.android_7.0/

Note: Due to a change by Google, Android N will now only permit linking to NDK-provided native libraries. libsqlite.so is not an NDK-provided native library. Consequently, existing apps using e.g. Mono.Data.Sqlite.dll will crash when running on Android N. This may include other SQLite-using assemblies, not distributed with Xamarin.Android.

Xamarin.Android 7.0, which is part of Cycle 8, updates Mono.Data.Sqlite.dll to include a custom built version of libsqlite.so, named libsqlite3_xamarin.so.

All Developers need to audit their code for P/Invoke and ensure that referenced native libraries are either included in the Android NDK, or are included within the app.apk itself. The only Xamarin.Android-provided assembly impacted by this change is Mono.Data.Sqlite.dll.

It looks like the library needs to reference the custom built C++ library from Xamarin. I don't feel like this is a good thing since it means relying on Xamarin's bifurcation of the SQLite library, but I will do some investigation to find out how to do this. It raises the question: why does Xamarin need to bifurcate the SQLite library? Perhaps there is a bug in the SQLite library on Android, but why isn't that bug fixed in the core SQLite code rather than by the Xamarin team?

[MelbourneDeveloper]

Here is a good article on what seems to be the problem:
http://ericsink.com/entries/sqlite_android_n.html

[FrozenKiwi]

Where has this issue got to? Is there a resolution in sight?

[MelbourneDeveloper]

Unfortunately not yet. However, we are having similar issues with UWP. We have to get our app in to the Windows, and Play stores, so we are now working to figure out which binaries to deploy, and how to deploy them. Rest assured that it will happen at some point because we need to get our app in to the stores, but when it will happen is another question.

[BaileyMillerSSI]

How is everything going with this bug? I am starting to debug on a real phone and seeing this error is getting annoying. Also it cannot continue into production.

Is there any plan to fix this problem? If not this package is DOA for Android development.

[andersonnsantos]

Same issues here, I hope anyone had resolve it, and post here for us.

[BaileyMillerSSI]

I worked around this by removing this package and creating my own entity framework package.

[MelbourneDeveloper]

@BaileyMillerSSI , @ALEITZINGER , @andersonnsantos, @Drew-E

Sorry for the slow response. I don't know why, but I don's seem to get any notifications about these Github issues. Unfortunately, I've not had time to look in to this issue, and SQLite support for our app is no longer a focus. Development on this repo is basically stalled for a while.

I would certainly like for someone else to debug this problem and submit a pull request. If anyone has time please let me know and I'll do my best to help you along.