Unable to deploy example NDK app to Android 9: 'remote secure_mkdirs failed: Operation not permitted'

[bazelbuild]

Unable to deploy example NDK app to Android 9: 'remote secure_mkdirs failed: Operation not permitted'

[jin]

Update: I managed to repro the issue and found the root cause.

Somewhere between 28 and 29, when creating directories as part of adb push, the behavior changed w.r.t. directory permissions.

On 28, the created directories via adb push have the permissions drwxrwxr-x.
On 29, the permissions are drwxrwx--x. The difference is the read permission for others. For some reason, this causes the adb push to fail.

It turns out that inserting a adb shell mkdir -p /data/local/tmp/incrementaldeployment/com.example.android.bazel/native/ before pushing the files creates the directory with the correct permissions, and native_manifest can be pushed correctly.

[jin]

Does regular adb install work? Looks like adb push under Bazel doesn't have the correct permissions.

As an aside and mentioned in the Slack chat, we’re in the process of open sourcing mobile-install v2. It’s a complete rewrite of mobile-install in Starlark, and thereafter we will deprecate the native mobile-install in Bazel. AFAIUC, mi-v2 will solve this issue.

[pandasyr]

I had this happen before and for me it was because the apk signature mismatch (because I switched computer), which was solved by uninstalling the old apk.

[jgavris]

A regular install works, yes. That's what we're using in Android Studio.