Is there an existing issue for this?
Description
New frontend bug. When installing a core from the filesystem with the "Install or restore a core" button and that core already exists, the progress bar stays at 0% with "Scanning core: Core name".
You can work around it by deleting the existing core first. This is android as usual
Expected behavior
Core gets replaced if it wasn't exactly the same core as before (I can't recall if it also refused to install a older version but regardless I dont think thats a good idea if it worked that way).
Steps to reproduce the bug
- Get a .so off the buildbot to a core you have installed
- Try to install it with the install or restore core button
- Watch the task hang at 0% (just the task, RetroArch continues running)
Version/Commit
1.22.2 (August 23 2026)
Bisect Results
No response
Present in the nightly version
Yes, this is reproduced in the nightly build
Platform & operating system
Android 15
Affected Cores
No response
Environment information
I do have Threaded tasks turned on if you were wondering.
Relevant log output
Is there an existing issue for this?
Description
New frontend bug. When installing a core from the filesystem with the "Install or restore a core" button and that core already exists, the progress bar stays at 0% with "Scanning core: Core name".
You can work around it by deleting the existing core first. This is android as usual
Expected behavior
Core gets replaced if it wasn't exactly the same core as before (I can't recall if it also refused to install a older version but regardless I dont think thats a good idea if it worked that way).
Steps to reproduce the bug
Version/Commit
1.22.2 (August 23 2026)
Bisect Results
No response
Present in the nightly version
Yes, this is reproduced in the nightly build
Platform & operating system
Android 15
Affected Cores
No response
Environment information
I do have Threaded tasks turned on if you were wondering.
Relevant log output