nextcloud / nextcloud/documentation
Instructions to fix "invalid code integrity" pretty sparse
Open
Nobody has claimed this yet.
1. to develop
enhancement
feature: install and update
manual: admin
- Dominant language
- JavaScript
- Stars
- 628
- Forks
- 2.5k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 135
Description
Reading admin_manual/issues/code_signing.rst it's not quite clear
- why this can happen: how worried should I be? are bugs in the updater code (or whichever other parts of nextcloud relate to this) common?
- how to fix this exactly: the text merely says
Here I'm wondering:The solution is to upload the correct "index.php" and "version.php" files, and delete the "test.php" file.
- where do I get the correct files for my version of nextcloud from?
- how do I confirm I got the right files?
- do I need to stop/start the service?
- ...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with admin_manual/issues/code_signing.rst and review the existing explanation of invalid code integrity. Research and document why the check can fail, where the correct index.php and version.php files come from, how to verify them, and whether service handling is required. Done means the recovery instructions answer these questions clearly.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100