[GH-ISSUE #313] Cannot install from CRX #277

Closed
opened 2026-02-25 22:36:41 +03:00 by kerem · 2 comments
Owner

Originally created by @ctr49 on GitHub (Jun 13, 2019).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/313

Software versions

  • Browser: Chromium 74.0.3729.157 (also tried with Chrome 74.0.3729.169) on macOS

  • Floccus: 3.3.0 (also tested with 3.3.0-beta5)

Steps to reproduce

  1. Download CRX from release page
  2. Drag and drop CRX into extensions view

Expected outcome

Extension being installed.

Actual outcome

Error message: "CRX_HEADER_INVALID"

Debug log

This is pre-install so I don't have a debug log.

  • Debug log provided
Originally created by @ctr49 on GitHub (Jun 13, 2019). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/313 <!-- Hello there! Thank you for providing feedback! Please answer the below questions to allow for as smooth a process of tackling the issue as possible :) (Note: Everything surrounded by arrows, like this text for example, will not be visible.) --> ### Software versions <!-- Please provide the versions of the following software products in your set up --> - Browser: Chromium 74.0.3729.157 (also tried with Chrome 74.0.3729.169) on macOS - Floccus: 3.3.0 (also tested with 3.3.0-beta5) <!-- Sync methods are either XBEL/webdav (signified as `webdav`), nextcloud Bookmarks legacy (signified as `nextcloud`), or nextcloud Bookmarks v0.14+ with folders (signified as `nextcloud-folders`) --> ### Steps to reproduce <!-- What did you do? Be as specific as possible --> 1. Download CRX from release page 2. Drag and drop CRX into extensions view ### Expected outcome <!-- What did you think was going to happen or what do you think should have happened? --> Extension being installed. ### Actual outcome <!-- What actually happened after you did the above steps? --> Error message: "CRX_HEADER_INVALID" ### Debug log This is pre-install so I don't have a debug log. - [ ] Debug log provided <!-- Thanks! Now, hit Submit and wait for a reply :) -->
kerem closed this issue 2026-02-25 22:36:41 +03:00
Author
Owner

@marcelklehr commented on GitHub (Jun 13, 2019):

This is to be expected with the standard chromium builds as they require a valid signature by the Chrome webstore. You will need to install it from the webstore directly. The download packages in this repo are more a nice-to-have for people with special needs, in most cases, the downloads from AMO or the chrome webstore are to be preferred.

<!-- gh-comment-id:501714571 --> @marcelklehr commented on GitHub (Jun 13, 2019): This is to be expected with the standard chromium builds as they require a valid signature by the Chrome webstore. You will need to install it from the webstore directly. The download packages in this repo are more a nice-to-have for people with special needs, in most cases, the downloads from AMO or the chrome webstore are to be preferred.
Author
Owner

@github-actions[bot] commented on GitHub (Mar 21, 2023):

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

<!-- gh-comment-id:1477489219 --> @github-actions[bot] commented on GitHub (Mar 21, 2023): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/floccus#277
No description provided.