Repository navigation
Missing Android N compatibility because of behavior changes #216
Description
Hello,
Google changed some things regarding linking/loading libs: https://developer.android.com/preview/behavior-changes.html#ndk
This also affects SQLCipher. E.g. the Test-Suite failed 10 out of 32 tests.
Log show up following:
03-10 09:09:17.497 26856-26869/net.zetetic:provider W/linker: library "libutils.so" ("/system/lib/libutils.so") needed or dlopened by "/data/app/net.zetetic-1/lib/arm/libsqlcipher_android.so" is not accessible for the namespace "classloader-namespace" - the access is temporarily granted as a workaround for http://b/26394120
03-10 09:09:17.497 26856-26869/net.zetetic:provider W/linker: library "libcutils.so" ("/system/lib/libcutils.so") needed or dlopened by "/data/app/net.zetetic-1/lib/arm/libsqlcipher_android.so" is not accessible for the namespace "classloader-namespace" - the access is temporarily granted as a workaround for http://b/26394120
03-10 09:09:17.517 26856-26869/net.zetetic:provider W/linker: library "libnativehelper.so" ("/system/lib/libnativehelper.so") needed or dlopened by "/data/app/net.zetetic-1/lib/arm/libdatabase_sqlcipher.so" is not accessible for the namespace "classloader-namespace" - the access is temporarily granted as a workaround for http://b/26394120
03-10 09:09:17.518 26856-26869/net.zetetic:provider W/linker: library "libandroid_runtime.so" ("/system/lib/libandroid_runtime.so") needed or dlopened by "/data/app/net.zetetic-1/lib/arm/libdatabase_sqlcipher.so" is not accessible for the namespace "classloader-namespace" - the access is temporarily granted as a workaround for http://b/26394120
03-10 09:09:17.518 26856-26869/net.zetetic:provider W/linker: library "libbinder.so" ("/system/lib/libbinder.so") needed or dlopened by "/data/app/net.zetetic-1/lib/arm/libdatabase_sqlcipher.so" is not accessible for the namespace "classloader-namespace" - the access is temporarily granted as a workaround for http://b/26394120
Reacted by Chundelac, Riyaz Mohammed Ibrahim, Baptiste Candellier, Patrick Fuentes, Dmitrii, Viktor and swati6532
Activity
developernotes commentedon Mar 10, 2016
Hello @TheNephilim88
Thank you for your early report of SQLCipher for Android on Android N. We hope to begin looking into the Android N build soon. Take care!
splendidbits commentedon Mar 17, 2016
As per https://developer.android.com/preview/behavior-changes.html#ndk
So instead of OpenSSL being compiled for each arch and being statically linked in the .so, I believe now that the bordingSSL library so (or a?) should be linked directly through the ndk from the user's OS. OpenSSL has been deprecated and removed in favour of boringssl
developernotes commentedon Mar 17, 2016
Hi @staticfish
We have historically built a static OpenSSL because of the differing versions of OpenSSL bundled across the various Android OS's. We will consider this change in the future.
TheNephilim88 commentedon Mar 19, 2016
Did anyone found time to look into this?
I know Android N is still dev preview, but its annoying nonetheless, especially if users dont understand and are giving bad ratings because of it :(
sjlombardo commentedon Mar 19, 2016
neutron666 commentedon Mar 20, 2016
But that's what dev previews are for, make issues appear early and fix them. I really would like to continune testing the N dev preview, but i need a app based on this lib urgently and it's very annoying to being able to use it. PLEASE start on fixing this problem as soon as possible.
mikecousins commentedon Mar 28, 2016
Hopefully this gets prioritized soon. The ease for user's to install the latest dev preview has resulted in quite a few people not being able to run anything using your library.
smarkovik commentedon Apr 6, 2016
Hello guys,
any ideas when this will get in your pipeline?
N preview has been out for a while and the apps which depend on sql cipher are essentially blocked.
sjlombardo commentedon Apr 6, 2016
@smarkovik we just finished up a release of SQLCipher yesterday. Now that is out of the way, we'll be switching over to look at this issue as a priority.
smarkovik commentedon Apr 14, 2016
Hello @sjlombardo,
Not being pushy but just curious of your progress? any ETAs?
could the community help ?
developernotes commentedon Apr 14, 2016
Hi @smarkovik
We are actively working on this project and will make our changes available as soon as everything is working. Thanks!
mvojjala commentedon Apr 27, 2016
Hi @sjlombardo
We are also in same situation. Not able use our app on Android N because of this issue. Just want to check with you if you have any update or tentative dates of a possible update.
Thanks
sjlombardo commentedon Apr 27, 2016
@mvojjala we're making appreciable progress on this issue, but it does involve some fairly major changes. Keep an eye on this ticket, and/or at https://discuss.zetetic.net/c/sqlcipher for information about upcoming availability for testing.
fuentespatrick commentedon Apr 27, 2016
I appreciate the effort and the update @sjlombardo.
My team is similarly blocked, so the significant work is greatly appreciated!
developernotes commentedon Apr 28, 2016
Hi folks,
We have just announced a beta of SQLCipher for Android with support for Android Developer N Preview here. Please take a look if you are interested in helping test out these changes. Thanks!
48 remaining items
jaredpetker commentedon Jun 20, 2016
Yea, I saw that initially and decided to live on the wild side which sadly bit me back, I assume you all have some pipeline internally for worrying about building with newer toolchains, until then yea, seems like all is well thanks!
ashishmody commentedon Jun 21, 2016
Hey @developernotes, do we know when will the update with this fix be released? Do we have a timeline in place? Looks like Google froze the APIs for N and is encouraging developers to get their apps ready for N soon. Any timeline would really help us plan! Thanks!
smarkovik commentedon Jun 21, 2016
I second that!
On Tue, Jun 21, 2016, 08:10 ashishmody notifications@github.com wrote:
Tancho
developernotes commentedon Jun 21, 2016
Hi @ashishmody, @smarkovik
We are planning a release soon, now that the N API has been finalized, and we've tested the library against the latest Developer Preview 4 (i.e., NPD56N). We appreciate your patience and enthusiasm!
developernotes commentedon Jun 23, 2016
Hi folks,
This is just an update, we have just release SQLCipher for Android 3.5.0 with support for Android N. More information can be found here. Thanks!
dfyx commentedon Jun 24, 2016
Will there be official binaries? The link in https://www.zetetic.net/sqlcipher/sqlcipher-for-android/ doesn't work for anything newer than 3.1.0 and when I build my own binaries, they are much larger (5 MB for armeabi and armeabi-v7a and 7 MB for x86) than the 1.6 MB mentioned in the blog post.
dfyx commentedon Jun 24, 2016
Nevermind, found the aar at http://central.maven.org/maven2/net/zetetic/android-database-sqlcipher/3.5.0/android-database-sqlcipher-3.5.0.aar which is just a renamed zip file.
(I just need the .so files for a .NET project)
developernotes commentedon Jun 24, 2016
Hi @dfyx
The native libraries included in the AAR package are compiled for the Android OS specifically and will not run on another environment.
dfyx commentedon Jun 24, 2016
@developernotes I know. I was talking about a Xamarin Android project.
CoconutByte commentedon Jul 1, 2016
@developernotes
when the column is defined by TEXT, It seems that the cursor.getInt() method can't return the right value of the column. Using the newest Version of sqlcipher released for Android N.
developernotes commentedon Jul 1, 2016
Hi @liuzhihuinb
I was not able to reproduce the problem you describe with the SQLCipher for Android test suite. Are you doing something different?
CoconutByte commentedon Jul 4, 2016
@developernotes
Thank you for you reply.
I found the problem in my app when I updated the sqlCihper to the version of 3.5.1.
As my app worked perfectly with the sqlCihper before,I'm confused.
I have wrote a demo for using cursor.getInt() ,I think you can reproduce it with the code below.
https://github.com/liuzhihuinb/SqlCipherDemo.git
developernotes commentedon Jul 5, 2016
Hi @liuzhihuinb
It appears your application may have a problem with the
minfunction instead? Are you able to reproduce the issue with the SQLCipher for Android test suite? We have a test that usesTEXTas the storage type, but requests an integer back from the cursor correctly..CoconutByte commentedon Jul 6, 2016
Hi @developernotes
Yes, I had reproduced this problem in the SQLCipher for android test suite.
As this issue had been closed. I submitted a new issue below since other people may encounter the same issue.
#244