Manifest not found
- Dominant language
- JavaScript
- Stars
- 9.3k
- Forks
- 694
- PR merge metrics
- No merged PRs in 30d
Description
**System**
* Windows
* 11
* Chrome
* 120.0.6099.71
**Extension**
buster
* Extension version: [e.g. 1.0.0]
latest
* User input simulation: [e.g. yes, no]
* Client app version: [e.g. 1.0.0]
* Client app installed successfully: [e.g. yes, no]
**Bug description**
"Failed to load extension from C:\users\\AppData\local\buster Manifest file is missing or unreadable"
Install appeared to succeed just fine.
**Logs**
Browser:
```
// REPLACE WITH LOGS
```
Client app:
```
2023/12/15 09:09:22.000000 Starting client (version: 0.3.0)
2023/12/15 09:09:22.000000 Receiving message
2023/12/15 09:18:33.279124 invalid character '\x00' looking for beginning of value
Then gobbledegook...
After reinstall:
2023/12/15 09:24:47.014641 Starting client (version: 0.3.0)
2023/12/15 09:24:47.014641 Receiving message
2023/12/15 09:24:47.014641 Processing message
2023/12/15 09:24:47.014641 Command: ping
2023/12/15 09:24:47.014641 Sending response
2023/12/15 09:24:47.014641 Receiving message
2023/12/15 09:24:47.015640 Closing client
But same message.
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the reported extension path, C:\users\\AppData\local\buster, and buster-client-log.txt, comparing the logs before and after reinstall. Request exact installation steps, the extension version, and browser console output to reproduce the manifest-loading error on Windows 11 with Chrome 120. No source files or tests are identified; done means the reproduced installation loads without the missing-or-unreadable manifest error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100