Android 执行Runtime.getRuntime().exec报错Permission denied

在Android上调用Runtime.getRuntime().exec()函数执行命令时，报错了。

java.io.IOException: Cannot run program "/data/data/com.example.testhband/outTest": error=13, Permission denied

使用命令 run-as com.example.testhband进入APK安装目录，发现outTest存在，权限也是正常的。

再查看应用程序的AndroidManifest.xml，也没发现什么特别的权限；

在网上查到资料，Android API 29以后，就不能在/data/data/安装包目录/ 下直接执行程序了，需要对程序打包方式进行处理，但是如果是 apk的 targetSdkVersion 小于29，还是可以兼容运行的。我把targetSdkVersion改为23，使用这个版本的SDK编译就可以了。

hen targeting API 29 (Android 10 / Q) or above, it is not possible anymore to have execute permission for files stored within the app's home directory (data), which is exactly what you are describing (/data/data/%package%/).

This Android 10 modification was introduced in commit: https://android-review.googlesource.com/c/platform/system/sepolicy/+/804149 and was then confirmed officially by Google here: https://issuetracker.google.com/issues/128554619

This significant change is being discussed by various projects, in termux/termux-app#1072 for instance. One recommended and (hopefully) future-proof way is to extract program binaries into the application's native lib directory (with android:extractNativeLibs=true), where files can still be executed but are stored read-only for improved security.

Here are examples showing how to handle this change, in Termux with commit f6c3b6f in the android-10 branch or in this other project showing how to run the Erlang runtime on Android by exctrating all the files from a .zip archive into the jniLibs/"abi" subdirectory ("abi" being arm64-v8a for 64-bit ARM, armeabi-v7a for 32-bit ARM, etc.) with the imposed lib___.so filename format expected by the Android platform. Executable files can simply be moved in the right project folder manually, the important part is to use the lib___.so format for the filenames.

In the Android Manifest file, setting the attribute android:extractNativeLibs="true" will get these lib___.so files extracted at installation time in the right native lib directory, with support for execute permission. Symlinks can finally be created if needed in the usual app directory to use the regular executable names, instead of the harder-to-manipulate lib___.so versions.
 

参考链接

https://stackoverflow.com/questions/64786837/what-path-to-put-executable-to-run-on-android-29/64792194#64792194
https://github.com/JeromeDeBretagne/erlanglauncher/issues/2
https://developer.android.com/about/versions/10/behavior-changes-10#execute-permission