[2508.4][RG35XX-SP] Retroachievements not working

Hello,

I have a problem similar to this one RG35XX H Retroachievements not working - #2 by Manulio .

It is written that is has been fixed but for my case (RG35XX-SP, MuOS 2508.4) it is not the case.
I have fixed one type of error in changing the password on the RetroAchievement website. I use now, a basic one of 8 characters.

The Retroachievements settings are rebooted even if I saved my settings in all the different overrides type files (game, core, etc.). I quit RetroArch after saving, I don’t use the start button, so it is not a mistake on my side.. The settings disappear when I come back to RetroArchMenu (User settings and Achievements menu).

On the shortcut menu of RetroArch “Achievements” it is written “not logged in” and I cannot do anything but it looks like when I come back to one of my game that is trying to connect because I have this error: “Missing RetroAchievements account information”

I have updated the goose version step by step with the different update files, version after another in respecting your FAQ and release note. My MuOS bios is on SD1 all the configs files, games, saves, etc. are on SD2

In checking the MuOS configuration files on SD2, we can see that cheevos_password, cheevos_token and cheevos_login are empty and that parameters exist in three different parts of the file. I tried to delete the file in doing the combination L2+X but MuOS displays on the screen an “error failed to erase the file”.

So it looks like a problem from MuOS.

The fix done here cheevo fix by GrumpyGopher · Pull Request #630 · MustardOS/internal · GitHub, show that it doesn’t take in account the custom name. It always “info/config/retroarch.config”

Huh? What?

No, you are doing this all incorrectly and the GitHub PR you linked does not fix what you think it does.

Adding your login details will be detected upon saving the RetroArch configuration and will be placed into its own individual file. This configuration file is then loaded at runtime alongside the main RetroArch configuration.

I’m not sure what you have done exactly but trust me when I say this. If there was an issue with achievement logins we would have heard about it for quite some time now and this wouldn’t be the first.

The only current issue with achievements at the moment, which is seemingly out of our control, is that it is caching slower than normal.

Again, let me reiterate, I would suspect you have done something erroneous and now are failing to login. Try using the RetroArch Restore Tasks in the task toolkit and try again.

I have reflashed my SD1 I have the same problems: this one describe on this ticket plus the same other problems that I have not yet describe yet. Before to do it. I will try to reflash the both SD and to put everything on SD1.

I don’t why. But it works if the setup has been done before the migration on SD2.

This topic was automatically closed 60 minutes after the last reply. New replies are no longer allowed.