/system/bin/sh: sqlite3: inaccessible or not found [142003176]

Assigned

Bug

Reviewed (L1)

Status Update

No update yet.

Description

ma...@marcardar.com

created issue #1

Oct 3, 2019 10:35AM

Since SDK 29 (emulator revision 8), the adb shell command:

adb shell sqlite3 --version

gives:

/system/bin/sh: sqlite3: inaccessible or not found

Before this revision, it gave the correct SQLite version number.

Comments

al...@gmail.com <al...@gmail.com> #2Oct 4, 2019 02:26AM

vi...@google.com <vi...@google.com> Oct 4, 2019 04:13AM

Assigned to vi...@google.com.

vi...@google.com <vi...@google.com> #3Oct 4, 2019 06:17AM

ma...@marcardar.com <ma...@marcardar.com> #4Oct 4, 2019 07:15AM

ma...@marcardar.com <ma...@marcardar.com> #5Oct 4, 2019 07:54AM

uc...@google.com <uc...@google.com> Oct 4, 2019 05:20PM

Reassigned to bo...@google.com.

ma...@marcardar.com <ma...@marcardar.com> #6Oct 13, 2019 08:45AM

ka...@google.com <ka...@google.com> #7Dec 10, 2019 12:39AM

ma...@marcardar.com <ma...@marcardar.com> #8Dec 26, 2019 08:40AM

Guys it's enough to just star the issue.

fr...@gmail.com <fr...@gmail.com> #9Feb 7, 2020 11:57PM

Thanks for the reports. This is caused the by Kotlin plugins using deprecated APIs. See

https://youtrack.jetbrains.com/issue/KT-25428

Once the Kotlin plugins start using the new APIs, we will enforce a minimum version of the Kotlin plugins that has the fix so these warnings can go away.

ma...@protonmail.com <ma...@protonmail.com> #10Feb 20, 2020 09:29PM

Some quick comments:

- I filed

Issue 116245497

to better handle the warning display. This is too aggressive for a warning right now.
- I filed

Issue 116247924

to help people troubleshoot what is calling the deprecated API.

ma...@marcardar.com <ma...@marcardar.com> #11Apr 2, 2020 02:02AM

I too get the same warning.

ma...@marcardar.com <ma...@marcardar.com> #12Jul 17, 2020 02:54AM

I'm not using Kotlin. Why do I receive this message too?

fr...@iress.com <fr...@iress.com> #13Dec 4, 2020 11:08AM

@12. in that case please run a build from the command line, with -Pandroid.debug.obsoleteApi=true to see what calls the deprecated method.

ma...@marcardar.com <ma...@marcardar.com> #14Dec 12, 2020 03:38AM

I am getting nothing helpful from adding the obsoleteApi=true flag with AGP3.3.0-a13

seems by running with -d via gradle cli we can see that it is:
[org.jetbrains.kotlin.gradle.plugin.Android25ProjectHandler] [KOTLIN] Process variant [debug]
while inside an after eval listener which I assume was registered by the kotlin plugin.

be...@googlemail.com <be...@googlemail.com> #15Oct 4, 2022 01:06PM

Do you see a stack trace when running with -Pandroid.debug.obsoleteApi=true? The stack trace should reveal what is calling the deprecated API.

jp...@google.com <jp...@google.com> #16Mar 10, 2023 09:58PM

s9...@gmail.com <s9...@gmail.com> #17Aug 15, 2023 07:05AM

Downgrade to

com.android.tools.build:gradle:3.2.0