# SQLCipher Issues on Android N Developer Preview

**URL:** https://discuss.zetetic.net/t/sqlcipher-issues-on-android-n-developer-preview/1251
**Category:** SQLCipher
**Created:** [March 22, 2016, 9:28pm UTC](https://discuss.zetetic.net/t/sqlcipher-issues-on-android-n-developer-preview/1251 "2016-03-22T21:28:49Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![sjlombardo](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.zetetic.net/sjlombardo/32/3_2.png) [@sjlombardo](https://discuss.zetetic.net/u/sjlombardo)
#### Post date: [March 22, 2016, 9:28pm UTC](https://discuss.zetetic.net/t/sqlcipher-issues-on-android-n-developer-preview/1251/1 "2016-03-22T21:28:49Z")

</div>

We’re currently aware of the issue running SQLCipher on the Android N Developer Preview and we are tracking an [open issue in GitHub for it](https://github.com/sqlcipher/sqlcipher/issues/158). The problem can cause crashes with the following reports:

```
Detected problems with app native libraries (please consult log for detail):
libsqlcipher_android.so: unauthorized access to 'libutils.so'
libsqlcipher_android.so: unauthorized access to 'libcutils.so
libsqlcipher_android.so: unauthorized access to 'libnativehelper.so'
libsqlcipher_android.so: unauthorized access to 'libandroid_runtime.so'
libsqlcipher_android.so: unauthorized access to 'libbinder.so'

```

We’ll be working on a resolution as high priority, though it may require some substantial changes to SQLCipher so we do not have a timeline right now. We’ll be sure to post updates here as they are available.

---

<div class="post-metadata">

### Author: ![praveenb](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.zetetic.net/praveenb/32/507_2.png) [@praveenb](https://discuss.zetetic.net/u/praveenb)
#### Post date: [January 26, 2017, 3:08pm UTC](https://discuss.zetetic.net/t/sqlcipher-issues-on-android-n-developer-preview/1251/2 "2017-01-26T15:08:52Z")

</div>

Feared to the core when i see this issue occurring on my Android N device.

But relieved after going through several related links and finally found these links, cleared my blues away

> [@SQLCipher for Android Release—Android N Support](https://discuss.zetetic.net/t/sqlcipher-for-android-release-android-n-support/1465):
>
> We are happy to announce the release of SQLCipher for Android 3.5.1. This is an urgent and mandatory upgrade for applications wishing to support Android N when it is publicly released. This release of SQLCipher for Android incorporates several major changes to facilitate operating on Android 2.1 through Android N, supporting armeabi, armeabi-v7a, and x86 platforms. The Google Android team contacted us directly, requesting many of the changes below. These changes were mandatory to make SQLCipher…

If you are using previous usage.

Alternately, if your previous usage of SQLCipher for Android was packaged as a zip archive that included 3 .so files per platform (i.e., libdatabase\_sqlcipher.so, libsqlcipher\_android.so, and libstlport\_shared.so), you should remove all of those. Our new packaging will only include one .so file (i.e., libsqlcipher.so) for each native platform. In addition to the different native libraries, you should also remove the ICU zip file (i.e., icudt46l.zip) previously included within the assets directory of your application.

and you should remove SqlCipher jar files also.

And followed this link  
[https://www.zetetic.net/sqlcipher/sqlcipher-for-android/](https://www.zetetic.net/sqlcipher/sqlcipher-for-android/)

these links helped a lot.

I see my app size also reduced from 9.79 MB to 3.88 MB, that’s cool.

Thank you so much for your team effort to bring out of this issue. I also see its simple to integrate now.  
I can’t say enough Thanks to you. So just saying Thanks a Ton 🙂
