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.

Sign up for GitHub

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

Jump to bottom

winget cannot find pokemon showdown version and always thinks there is an available upgrade #8623

Closed
ix0rai opened this issue Jan 11, 2022 · 5 comments
Closed

winget cannot find pokemon showdown version and always thinks there is an available upgrade #8623

ix0rai opened this issue Jan 11, 2022 · 5 comments

Comments

@ix0rai
Copy link

ix0rai commented Jan 11, 2022

When installing pokemon showdown through winget, winget always acts as if there is an applicable update to 0.3.0 for it and claims that the current installed version is Unknown
image

Performing the upgrade does not fix the issue, the version is still Unknown
@ix0rai
Copy link
Author

ix0rai commented Jan 11, 2022

it seems like this isn't an issue with showdown, it's an issue with winget, sorry to bother you all

@ix0rai ix0rai closed this as completed Jan 11, 2022
@ix0rai
Copy link
Author

ix0rai commented Jan 11, 2022 •
edited
Loading

reopening after getting this response after asking on the winget repository:
issue for reference

It is because pokemon showdown doesn't write displayversion registry key, so winget cannot read it from ARP list. You should ask the developer of pokemon showdown to make their installer write this key.

@ix0rai ix0rai reopened this Jan 11, 2022
@ix0rai
Copy link
Author

ix0rai commented May 2, 2022

Could this issue be transferred to the showdown client?

@ix0rai
Copy link
Author

ix0rai commented Jul 22, 2022

small update: I'm not using windows anymore, which would make it quite a bother to test this issue
I'm no longer going to be any help if someone wants to look into fixing this

@monsanto
Copy link
Member

monsanto commented Jan 7, 2023 •
edited
Loading

Issue creator is no longer interested & I am also not interested in maintaining the .exe

@monsanto monsanto closed this as completed Jan 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@monsanto @ix0rai