Quick Menu missing options when launching game via intent — core_info.cache not built properly
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Is there an existing issue for this?
- This is a bug in RetroArch frontend
- I have searched the existing issues
Description
Bug: core_info.cache is built incorrectly when launching game via intent (without entering main menu)
RetroArch version: 1.20.0 and 1.21.0 (Android)
Platform: Android (tested on emulator and real devices)
Steps to reproduce:
- Launch RetroArch directly using an intent that specifies a core and a ROM file (bypassing the frontend GUI).
- RetroArch boots the game correctly.
- However, the generated
core_info.cacheis incomplete or missing proper info from the intended core. - This results in incomplete Quick Menu options, such as the "Save State" button being missing.
Workaround:
Manually copying a valid core_info.cache file (generated during normal GUI usage) to the correct directory bypasses the issue and restores full functionality.
Expected behavior:
RetroArch should load the correct .info file of the core when launched via intent and generate a valid core_info.cache file with full core metadata.
Notes:
- This issue affects all tested versions.
- Might go unnoticed because most users use the frontend menu, not direct intents.
Expected behavior
No response
Steps to reproduce the bug
Bug: core_info.cache is built incorrectly when launching game via intent (without entering main menu)
RetroArch version: 1.20.0 and 1.21.0 (Android)
Platform: Android (tested on emulator and real devices)
Steps to reproduce:
- Launch RetroArch directly using an intent that specifies a core and a ROM file (bypassing the frontend GUI).
- RetroArch boots the game correctly.
- However, the generated
core_info.cacheis incomplete or missing proper info from the intended core. - This results in incomplete Quick Menu options, such as the "Save State" button being missing.
Workaround:
Manually copying a valid core_info.cache file (generated during normal GUI usage) to the correct directory bypasses the issue and restores full functionality.
Expected behavior:
RetroArch should load the correct .info file of the core when launched via intent and generate a valid core_info.cache file with full core metadata.
Notes:
- This issue affects all tested versions.
- Might go unnoticed because most users use the frontend menu, not direct intents.
Version/Commit
1.21.0
Bisect Results
No response
Present in the nightly version
I don't know
Platform & operating system
Android 10
Affected Cores
No response
Environment information
No response
Relevant log output
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the Android launch both through a direct intent and through the frontend GUI, then compare the generated core_info.cache and the resulting Quick Menu options. Trace the intent launch path and the .info-file/cache generation; done means the intended core metadata is present and options such as Save State appear without manually copying a cache file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, c
- Domain
- frontend, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100