Qt Creator Android 15 adb.exe pull /system/bin/app_process64 error

Vitagrit

QtCreator with Android device was working fine until updated OS to Android 15.
Now the apk is built and runs but every time it displays compile error:
The command "<PATH>\Android\SDK\platform-tools\adb.exe -s <DEVICE_ID> pull /system/bin/app_process64 <PATH>\app_process" terminated with exit code 1.

Message box:
Ignore all errors? - Qt Creator
found some build errors in current task. do you want to ignore them?
Click Yes and the app runs, but I assume missing the step below (which I think gets a list of running processes?).

Qt Creator COMPILE OUTPUT:
...
Android package built successfully in X ms.
-- It can now be run from the selected device/emulator.
-- File: <PATH>.apk
The process "<PATH>\androiddeployqt.exe" exited normally.
Package deploy: Running command "<PATH>\platform-tools\adb.exe -s <DEVICE_ID> pull /system/bin/app_process64 <PATH>\app_process".
The command "<PATH>\adb.exe -s <DEVICE_ID> pull /system/bin/app_process64 <PATH>\app_process" terminated with exit code 1.
Package deploy: Running command "<PATH>\adb.exe -s <DEVICE_ID> pull /system/bin/linker64 <PATH>\linker64".
Package deploy: Running command "<PATH>\adb.exe -s <DEVICE_ID> pull /system/lib64/libc.so <PATH>\libc.so".
...

TESTED:
Reinstalled Qt Creator, checked Devices, Kits, android build platform.
Re-enabled developer options and USB debugging on device.

Running the command manually (that produces the error) in Qt Creator terminal :
adb: error: failed to copy '/system/bin/app_process64' to '<PATH>\android-app-process\app_process': remote open failed: Operation not permitted

Android Studio deploys fine to the device.
Qt Creator Emulator app runs fine.
Is this an Android 15 problem?

cristian-adam

Please do open a bug report at https://bugreports.qt.io/secure/CreateIssue.jspa?pid=10512

I am seeing the same state on macOS with Android 15 and a Samsung Galaxy S23.

The file rights on the device are:

dm1q:/ $ ls -al /system/bin/app_process64                                                                                        
-rwxr-xr-x 1 root shell 23104 2022-01-01 01:00 /system/bin/app_process64

the same as on the emulator:

emu64a:/ $ ls -al /system/bin/app_process64                                                                                      
-rwxr-xr-x 1 root shell 51768 2024-09-13 23:46 /system/bin/app_process64

But when trying to copy the file from the device, it fails with:

% ./adb pull /system/bin/app_process64 .
adb: error: failed to copy '/system/bin/app_process64' to './app_process64': remote open failed: Operation not permitted

cristian-adam

I've tried with Android Studio, similar situation. Emulator works, device doesn't.

failed to connect to socket 'localabstract:/io.qt.dice-0/platform-1751563898159.sock': could not connect to localabstract address 'localabstract:/io.qt.dice-0/platform-1751563898159.sock'
2025-07-03 19:31:39.736 28518-28521 nativeloader            io.qt.dice                           D

Vitagrit

@cristian-adam said in Qt Creator Android 15 adb.exe pull /system/bin/app_process64 error:

I am seeing the same state on macOS with Android 15 and a Samsung Galaxy S23.

Thanks for that, yes it seems to be a file access issue, I also wondered if there might be a new Developer Mode setting to enable this to work

SMF-Qt

@Vitagrit

I have had the same problem [https://forum.qt.io/topic/162533/testing-android-apk-with-qtcreator-fails-with-an-error] while setting up an android development environment.
My current work around is to create the arm64-v8a APK file and manually copy it to the target devices download directory and install it from there, all my debugging is done using the X86_64 simulator.

Rampe

Thx for the topic and ticket, discussion continuing in https://bugreports.qt.io/browse/QTCREATORBUG-33203

cristian-adam

This issue has been fixed at Android: Remove app_process retrieval

You can get a Qt Creator 17.0.1 snapshot the next days with the fix.

SMF-Qt

@cristian-adam

Tested qtcreator 17.0.1 with my Samsung A06 Phone and Tab9 Tablet and both now deploy correctly.

Thankyou.