PI'm sorry to hear you're experiencing issues logging into your Amazon Games account through the Heroic Games Launcher. This is a known issue that some users have encountered. Here are a few steps you can try to resolve the problem:
Delete Specific Configuration Files:
Linux Users: Navigate to the directory ~/.config/heroic/nile_config/nile/ and delete the files named user.json, library.json, and installed.json. This action has helped some users resolve the login issue.
GITHUB.COM
Flatpak Users: For those using the Flatpak version of Heroic, the files might be located in ~/.var/app/com.heroicgameslauncher.hgl/config/heroic/nile_config/nile/. Deleting the same set of files in this directory has also been reported to fix the issue.
GITHUB.COM
Windows Users: On Windows, the configuration folder is typically found at C:\Users<your_username>\AppData\Local\Programs\heroic. Deleting the aforementioned files from this directory may help resolve the login problem.
GITHUB.COM
Please note: After deleting these files, you might need to re-import or reinstall your Amazon games, as Heroic may not recognize them as installed.
Update Heroic Games Launcher: Ensure you're using the latest version of Heroic Games Launcher, as updates often include fixes for known issues. For instance, version 2.15.2 addressed Amazon Games library synchronization failures.
GAMINGONLINUX.COM
Use the Latest 'nile' Build: Some users have reported that updating to the latest nightly build of 'nile' (the tool Heroic uses to interact with Amazon Games) resolves login issues. You can download the latest version from the official repository and configure Heroic to use this updated 'nile' binary.
REDDIT.COM
Seek Community Support: If the above steps don't resolve your issue, consider reaching out to the Heroic Games Launcher community. The Heroic Games Launcher GitHub Issues page and the Heroic Games Launcher subreddit are active platforms where you can seek assistance.
I hope these steps help you regain access to your Amazon Games through the Heroic Games Launcher
Delete Specific Configuration Files:
Linux Users: Navigate to the directory ~/.config/heroic/nile_config/nile/ and delete the files named user.json, library.json, and installed.json. This action has helped some users resolve the login issue.
GITHUB.COM
Flatpak Users: For those using the Flatpak version of Heroic, the files might be located in ~/.var/app/com.heroicgameslauncher.hgl/config/heroic/nile_config/nile/. Deleting the same set of files in this directory has also been reported to fix the issue.
GITHUB.COM
Windows Users: On Windows, the configuration folder is typically found at C:\Users<your_username>\AppData\Local\Programs\heroic. Deleting the aforementioned files from this directory may help resolve the login problem.
GITHUB.COM
Please note: After deleting these files, you might need to re-import or reinstall your Amazon games, as Heroic may not recognize them as installed.
Update Heroic Games Launcher: Ensure you're using the latest version of Heroic Games Launcher, as updates often include fixes for known issues. For instance, version 2.15.2 addressed Amazon Games library synchronization failures.
GAMINGONLINUX.COM
Use the Latest 'nile' Build: Some users have reported that updating to the latest nightly build of 'nile' (the tool Heroic uses to interact with Amazon Games) resolves login issues. You can download the latest version from the official repository and configure Heroic to use this updated 'nile' binary.
REDDIT.COM
Seek Community Support: If the above steps don't resolve your issue, consider reaching out to the Heroic Games Launcher community. The Heroic Games Launcher GitHub Issues page and the Heroic Games Launcher subreddit are active platforms where you can seek assistance.
I hope these steps help you regain access to your Amazon Games through the Heroic Games Launcher
Pwhy did you respond to a support post with chatgpt LOL
Don a post from jan even the log is out of date who even knows if that above advice applies to the problem (money on it doesnt since its wanting you to delete nile for whatever reason)
Dbut has no proof that nile is the problem since the log link is no longer valid
