Latest Android Retroarch in F-Droid/APK crashes before loading ROMs
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Hi!
I found that both the latest Retroarch version that can be downloaded from F-Droid (1.9.0_GIT) and the apk in the official website are not working properly.
It boots and downloads the base assets and the cores can be downloaded but as soon as you try to load any content it crashes without any error and returns to the Android launcher.
I thought it was a problem on my Oneplus 5T phone but my old Oneplus 2 does the same. And now I have a Xiaomi 12t Pro and it does exactly the same.
I tried downloading the .apk (1.12.0) directly from the official website but I get the same behaviour.
The Play Store version works like a charm, both the regular and the plus one.
I tried the three different builds, by the way, regular, aarch64 and 32bit.
The log is attached, but I can't seem to find any relevant error.
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
Start by reviewing the attached retroarch.debug.log and reproducing content loading with the F-Droid or official APK, comparing it with the working Play Store builds. Test the reported regular, aarch64, and 32-bit builds on the listed Android devices; done means loading content no longer returns to the launcher and the cause is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, c
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100