I am experiencing an issue with the DS-5 debug configuration where the APK, Process, and Activity fields remain blank after selecting an APK file that was not available when the configuration was first created.
To reproduce the issue:
Remove the APK file from the project.
Create a new DS-5 debug configuration and select the project directory.
Try to browse for the APK file. Since it has not been built yet, it cannot be selected.
Click Apply and close the configuration dialog.
Build the project so the APK file becomes available.
Reopen the same debug configuration and select the APK using the workspace browser.
Notice that the Process and Activity fields remain blank.
Re-select the project directory using the workspace browser. The APK, Process, and Activity fields are now populated correctly.
It appears that selecting the APK file does not trigger the same field updates as selecting the project directory. I would expect the configuration to populate the relevant fields when the APK is selected or when Apply is clicked.
Is this a known issue, and is there a workaround that avoids having to reselect the project directory?
Tags: DS-5, Debug Configuration, APK, Android Debugging
Thanks for explaining the issue in detail. The behavior you described does seem inconsistent, especially when selecting the APK file does not populate the Process and Activity fields, but reselecting the project directory fixes the problem. Hopefully, a future update will make the configuration process more reliable and save developers from repeating these steps. For those who enjoy exploring mobile gaming updates and beta features, Astute OB54 Beta Server also shares Free Fire beta-related information and guides.