Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

segaMS games aren't recognize by the client #18

Closed
dinovich opened this issue Feb 1, 2022 · 6 comments
Closed

segaMS games aren't recognize by the client #18

dinovich opened this issue Feb 1, 2022 · 6 comments

Comments

@dinovich
Copy link

dinovich commented Feb 1, 2022

I added segaMS games, and even inside the config everything looks fine.
But when I navigate the client to the segaMS system, I get the message: "No items to load, please add some games".
I tried to add the games to config again, but it looks like it's mapped properly and still doesn't recognize any game in the client.

Any ideas?

@project-bot project-bot bot added this to To do in Issue & PR Tracker Feb 1, 2022
@github-actions
Copy link

github-actions bot commented Feb 1, 2022

Thanks for opening your first issue here! Be sure to follow the bug or feature issue templates!

@thelamer
Copy link
Member

thelamer commented Feb 1, 2022

Can you post your full json here:
https://www.textdrop.link/

@dinovich
Copy link
Author

dinovich commented Feb 1, 2022

@thelamer
Copy link
Member

thelamer commented Feb 1, 2022

This json loads for me.
Check your browser console make sure you don't have anything misconfigured.
test-min

@dinovich
Copy link
Author

dinovich commented Feb 1, 2022

Figured it out, it was a caching issue. I noticed the browser pulled:
http://192.168.2.21:8196/user/config/segaMS.json
and it had empty items array in it.

Once I refreshed its cache, everything started working. I wonder if it's not a good idea to force a random query param to pull an updated JSON every time?

@thelamer
Copy link
Member

thelamer commented Feb 1, 2022

nope, works as intended.

@thelamer thelamer closed this as completed Feb 1, 2022
Issue & PR Tracker automation moved this from To do to Done Feb 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

2 participants