-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Theming app code signature not found after upgrade #9568
Comments
This affects me too. Updated from 13.0 to 13.2 and now get the same warning. |
I'm getting it also... Operating system: |
@cmseal @deddc23efb @INLinuxdude Did you update the theming app though the apps management today? |
Yes - this app is missing the signature :/ |
Doh. Sorry. Yeah, obviously I missed adding that signature file :( |
@blizzz And please also remove the "*.orig" files 😉 |
@MorrisJobke already cleaned up. |
Could you tell me how to fix this please? Do I need to wait for next version? |
We will publish a new version soon (within a few hours). |
Great, thank you! |
Fixed with 1.4.3. After updating, you need to click on "Rescan" in the admin settings to trigger a new integrity check. This happens automatically only when running the updater, not after single app installs/updates. |
Thanks the fix worked for me. |
I get a code integrity fail after updating the theming app.
What should I do? |
@alexandre1985 as you can see in the Results, your issue has nothing to do with the theming app, but the |
Steps to reproduce
Expected behaviour
No issues with code signing
Actual behaviour
Theming app code signature not found
Server configuration
Operating system:
CentOS 7
Web server:
Apache 2.4
Database:
MariaDB
PHP version:
7.1
Nextcloud version:
13.0.2
Updated from an older Nextcloud/ownCloud or fresh install:
Updated from 13.0.1
Where did you install Nextcloud from:
Signing status:
Signing status
Results
Raw output
Array
(
[theming] => Array
(
[EXCEPTION] => Array
(
[class] => OC\IntegrityCheck\Exceptions\InvalidSignatureException
[message] => Signature data not found.
)
)
The text was updated successfully, but these errors were encountered: