duckstation android failed to load cd image permission denied

[2daysale]

Question I downloaded latest Android Duckstation on my Nvidia shield. I can load ROMs and play games in the stand alone Duckstation. When I choose Duckstation from within LaunchBox I get this error-duckstation  failed to load cd image permission denied.

I did turn off preload CD image in the stand alone Duckstation -restarted Shield. Get the same error in LaunchBox -

Thanks

 

[chelnov]

Same Problem with me on Pegasus frontend. New Update is causing this issue as older version run without any problem, and so far not getting any fix.

[HugoBR]

I'm having the same problem and came here for a solution... Well maybe in the next launchbox update.

[CamboSoup]

I am having the same issue. Anyone have a fix? Looking at other front ends like daijisho, the fix was changing file.uri to file.path. Only issue is that I do not know how to do this in LaunchBox

Edited August 6, 2023 by CamboSoup

[retrodude]

Same problem here, any news?

[HugoBR]

Updated to the new version , still has the same problem with duckstation. 

[Jessica]

Duckstation still doesn't work with launchbox, works fine with all other frontends.

[DragoonDemon4]

Having the same issue With Duckstation, and when I install the legacy version, it upgrades to the google play version, and then it broke up. All the other front ends fixed the issue, but not launchbox, Why?

[retrodude]

Still no fix? 

Edited January 24, 2024 by retrodude

[CamboSoup]

Is there any update on this. Duckstation works in all other Android front ends other than Launchbox

[Howitzer99]

This is still an issue, can the devs look into this?  Duckstation works properly when run outside of LaunchBox, but when running from inside, it gives the permission errors outlined above.

Edited Monday at 09:40 AM by Howitzer99

[faeran]

On 3/30/2025 at 11:39 PM, Howitzer99 said:

This is still an issue, can the devs look into this?  Duckstation works properly when run outside of LaunchBox, but when running from inside, it gives the permission errors outlined above.

This will actually be working in the next update.

The issues with this emulator are stated in a few places around this forum, so I won't go too much into detail here. The gist is that it doesn't have to do with whether an emulator is working, but whether a frontend has the ability to send a file path to it that the emulator can read (which is harder said than done on Android). There are two solutions to this, one that an emulator dev can implement, the other that we can implement (via scoped storage). The emulator dev solution is more user friendly, while scoped storage is less user friendly.

In saying that, we are in the process of implementing scored storage, as well as going through a giant list of emulators, including Duckstation, and making sure they can launch via one of the two ways.

This will be a culmination of a few months of blurry eyed work here, so yeah, we are looking into this 😉