raycast / raycast/extensions

[HowLongToBeat] "Auth Token: Not Found" Error

Open
#30,809 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug extension extension: howlongtobeat platform: macOS
Dominant language
TypeScript
Stars
7.8k
Forks
6.9k
Avg merge
2d 6h
Merged PRs (30d)
442

Description

Extension

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

Raycast Version

2.2.0.0

OS Version

macOS Tahoe 26.6.2 arm64

Description
Error:
Error: Failed to get auth token: Not Found
at Ou.getAuthToken (~/.config/raycast/extensions/9fec163c-3a81-4104-a7de-df5b3d75ad73/index.js:158:4167)
at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
at async Ou.postWithAuth (~/.config/raycast/extensions/9fec163c-3a81-4104-a7de-df5b3d75ad73/index.js:158:4447)
at async tr.search (~/.config/raycast/extensions/9fec163c-3a81-4104-a7de-df5b3d75ad73/index.js:158:5514)
at async ~/.config/raycast/extensions/9fec163c-3a81-4104-a7de-df5b3d75ad73/index.js:181:4386
Steps To Reproduce

Simply run the extensions one and only command and the error will occur...

Current Behaviour

The command opens, but the "Failed to get auth token: Not Found" error.

Expected Behaviour

When the command opens, information from "HowLongToBeat.com" should be populated...

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Open the linked HowLongToBeat extension and run its only command to reproduce the failure. Inspect the getAuthToken call shown in index.js and the request that returns Not Found. Done means the command opens and populates information from HowLongToBeat.com without the auth-token error.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
api, authentication
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
50/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.