Fate-Grand-Automata / Fate-Grand-Automata/FGA
Built-in recorder bug and crash
- Dominant language
- Kotlin
- Stars
- 2.4k
- Forks
- 362
- Avg merge
- 9h 54m
- Merged PRs (30d)
- 19
Description
I wanted to test out using the built-in recorder, since I remember that I couldn't use it before, but the same thing is happening.
I switch on the recorder in the settings and then run the app. When I tap the 'Play' button, the pop-up asking me to confirm which Auto-skill setup to use appears, but the Play/Stop button disappears completely. Even after confirming the skill setup, nothing happens afterwards.
If I try to do it a second time (going back to FGA to start it up then back to FGO), this time it freezes and I get that pop-up that tells me that FGA stopped running. But then the whole screen freezes. I can either leave it alone for several minutes before FGA is closed and FGO is running normally again, or I can turn off my display and turn it back on to find FGO running normally. Either way, FGA closes.
If I try to start up FGA a third time, I get redirected to allow the app Accessibility. When I check, the App is still allowed to do everything it needs. I just turn it off, then turn it back on again. Even so, I can't start up FGA again as it keeps redirecting me to give it permission to access what it needs even though it has it already.
I uninstall the app and reinstall it, give it access again, and everything works. EXCEPT for the recorder.
I've tried it with the "Notch Calculation" both on and off with the same results.
I've switched off Game Launcher. Same result.
I've switched off the Game Booster. Same result.
Not sure if anyone else is having this issue.
Device Info:
- Device model: Samsung A71
- Screen size: 1080 x 2400
- Android Version: 10
- RAM: 8GB
Contributor guide
Research direction
Start by reproducing the built-in recorder flow on the Samsung A71 running Android 10, including the first and second launches and the Accessibility permission loop. Compare the Play/Stop button, app freeze, FGA closure, and recorder behavior after reinstall; done means recording starts normally without crashes or repeated permission prompts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- accessibility, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100