[HowLongToBeat] 404 error when opening the extension

[FelixLisczyk]

Extension

https://www.raycast.com/Cronos87/howlongtobeat

Raycast Version

1.80.0

macOS Version

14.6

Description

When opening the extension, the following error message appears in the status bar: Could not perform search. Error: Request failed with status code 404. The same error appears when searching for a game.

Steps To Reproduce

1. Open the extension

Current Behaviour

The error message described appears.

Expected Behaviour

There should be no error message. The game search should work as expected.

[raycastbot]

Thank you for opening this issue!

🔔 @Cronos87 @whitespacecode you might want to have a look.

💡 Author and Contributors commands

The author and contributors of `Cronos87/howlongtobeat` can trigger bot actions by commenting: - `@raycastbot close this issue` Closes the issue. - `@raycastbot rename this issue to "Awesome new title"` Renames the issue. - `@raycastbot reopen this issue` Reopens the issue. - `@raycastbot assign me` Assigns yourself to the issue. - `@raycastbot good first issue` Adds the "Good first issue" label to the issue. - `@raycastbot keep this issue open` Make sure the issue won't go stale and will be kept open by the bot.

[whitespacecode]

Not sure what happend but the raycast npx @raycast/api@latest publish added a pull request instead.. :/ https://github.com/raycast/extensions/pull/13888

Workflow:

Need to install the following packages:
@raycast/api@1.80.0
Ok to proceed? (y) y
ready -  validate git repository
ready -  getting fork
ready -  preparing clone
error -  checking for new contributions
some contributions are available. Pull them using `npx @raycast/api@latest pull-contributions`
[09:30:11] [cost 31.755s] npx @raycast/api@latest publish                                         
[09:30:22] [~/Code/raycast/extensions/howlongtobeat] ❱❱❱ npx @raycast/api@latest pull-contributions 
ready -  getting fork
ready -  preparing clone
ready -  pulling new contributions
Some contributions conflict with your changes.

I then merged the conflicts and ran npx @raycast/api@latest publish again

Anyway @FelixLisczyk the fix is pushed. Waiting on who can help resolve this.