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

browser/keyboard sounds path in manifest.json not found in archive #213

Open
citricteadog opened this issue Mar 31, 2024 · 2 comments
Open

Comments

@citricteadog
Copy link

image
i spent so many hours trying to find the solution but literally nothing works, and when i change the browser_sounds and keyboard_sounds to sound and keyboard in the manifest file, opera just doesnt add the sounds. im so confused and exhausted

@Thetree007
Copy link

I have this same problem just on a smaller scale with a few errors, i have also tried everything. I asked someone on the gx developer discord and they said it might be the servers of opera gx.
pain

@TBTS-2011
Copy link

image i spent so many hours trying to find the solution but literally nothing works, and when i change the browser_sounds and keyboard_sounds to sound and keyboard in the manifest file, opera just doesnt add the sounds. im so confused and exhausted

Greetings @citricteadog,

Issue #195 has the exact same problem as issue #213.

Well, this problem might occur because the mod might be corrupted, it can be warped, it can contain a bug, or the browser is not responding properly.

Here are some good methods to follow if you encounter these problems:


  • Check the manifest file:

    Verify the file name and ensure the manifest file is named correctly. It should be named
    manifest.json and located in the root directory of your mod folder.

  • Confirm its presence:

    Double-check that the manifest file actually exists in the correct location.

  • Check the encoding:

    Sometimes, the encoding of the manifest file might be incorrect, causing Opera GX to fail to read
    it. So, to avoid that, open the file in a text editor that supports different encodings, and we
    recommend using Notepad++, and try saving it in UTF-8 encoding format for ease of access.

  • Inspect the contents:

    Open the manifest file with a text editor and ensure it's properly formatted in JSON format. You
    can find examples of valid manifest files online for reference.

Even if you did take the above listed inspections, then it might be a good time to check with the GX team, and try to fix the issue with them, or just do one more check-up to the Music files (of course there would be nothing wrong with them, but it's a good time check them too), which seems to be the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants