upgrade - Fatal Signal 31 error when upgrading android app from API 24 to 26 -


i getting error -

a/libc: fatal signal 31 (sigsys), code 1 in tid 4168 (m.messagingdapp)  

when upgrade app api 24 26 (have java.nio.file features). error can see in logcat. works fine when running api 24. gets error when accessing api i'm using called go-ethereum on line -

string f = this.getfilesdir() + "/.ethereum"; long n = geth.lightscryptn; long p = geth.lightscryptp; accountmanager = geth.newaccountmanager(f, n, p); //here 

there seem lots of other errors on different parts of logcat in drop down menu i.e system_process. however, new android , don't know looking (i have googled of them separately have gotten no fix). thanks.

full lolcat -

07-25 22:17:14.774 9625-9625/? i/zygote: not late-enabling -xcheck:jni  (already on) 07-25 22:17:14.825 9625-9625/? w/zygote: unexpected cpu variant x86  using defaults: x86 07-25 22:17:15.181 9625-9625/benkrarup.ethereum.messagingdapp w/zygote:  class android.support.v4.util.simplearraymap failed lock verification  , run slower. 07-25 22:17:15.181 9625-9625/benkrarup.ethereum.messagingdapp w/zygote:  common causes lock verification issues non-optimized dex code 07-25 22:17:15.181 9625-9625/benkrarup.ethereum.messagingdapp w/zygote:  , incorrect proguard optimizations. 07-25 22:17:15.184 9625-9625/benkrarup.ethereum.messagingdapp w/zygote:  class cz.msebera.android.httpclient.conn.util.publicsuffixmatcherloader  failed lock verification , run slower. 07-25 22:17:15.191 9625-9625/benkrarup.ethereum.messagingdapp  d/networksecurityconfig: no network security config specified, using  platform default 07-25 22:17:15.216 9625-9625/benkrarup.ethereum.messagingdapp  w/java7support: unable load jdk7 types (annotations,  java.nio.file.path): no java7 support added 07-25 22:17:15.596 9625-9657/benkrarup.ethereum.messagingdapp a/libc:  fatal signal 31 (sigsys), code 1 in tid 9657 (m.messagingdapp) 

android 8 o (sdk 26) limits system calls allowed security reasons enabling feature called secure computing in linux kernel.

this means whitelisted calls can executed , other call result in signal 31 (sigsys), code 1 (sys_seccomp), experiencing. need examine stack trace of signal find out system call not allowed (which not listed in question).

you can find list of allowed calls here. other call not allowed.

you can find google wrote here.


Comments

Popular posts from this blog

node.js - Node js - Trying to send POST request, but it is not loading javascript content -

javascript - Replicate keyboard event with html button -

javascript - Web audio api 5.1 surround example not working in firefox -