News: EXTRA_FILE warning (not signed in signature.json)
IMPORTANT
Read and tick the following checkbox after you have created the issue or place an x inside the brackets ;)
- [x] I have read the CONTRIBUTING.md and followed the provided tips
Explain the Problem
I get the error below.
Technical information
=====================
The following list covers which files have failed the integrity check. Please read
the previous linked documentation to learn more about the errors and how to fix
them.
Results
=======
- news
- EXTRA_FILE
- vendor/arthurhoaro/favicon/resources/cache/url1be7b227fa4c5a9af5e8f68f26d24cee
Raw output
==========
Array
(
[news] => Array
(
[EXTRA_FILE] => Array
(
[vendor/arthurhoaro/favicon/resources/cache/url1be7b227fa4c5a9af5e8f68f26d24cee] => Array
(
[expected] =>
[current] => 2dec25f4997fb386bc5603cf245d645c62bf34929a2c3025d3afc3496e12dc94e6732608b551dddec315c8655da89e9ca6a76b95a7ca9d8c6b159a3b93d72712
)
)
)
)
Which according to the documentation means:
The file does not exist in signature.json. This usually happens when a file has been removed and signature.json has not been updated. It also happens if you have placed additional files in your Nextcloud installation folder.
This problem only showed up after I updated to Nexctloud 15.0.6, so it could be unrelated to News.
System Information
- News app version: 13.1.5
- Nextcloud version: 15.0.6
AquaL1te
All 23 comments
I get the the same error(with [expected] =>"") for about 10 url* files after Update Nextcloud 15.0.4 to 15.0.5 and News from 13.1.4 to 13.1.5 at the same time.
First i tried a "occ maintenance:update:htaccess" without success.
The solution in my case was to delete this files from vendor/arthurhoaro/favicon/resources/cache
But I'm not sure if this was the fine way and I don't know what was the reason. I hope the developers can say something about it.
tioannidis
on 5 Apr 2019
We probably need to move the favicon cache to the data directory.
Grotax
on 5 Apr 2019
I'd say system tmp is better. It's a cache after all.
SMillerDev
on 5 Apr 2019
@Grotax @SMillerDev could you please tell me what was the trigger ? the Nextcloud Update to 15.0.5 or or the the News Update to 13.1.5?
I want to avoid this error on my prod Instanz. Should I wait with both updates until the next News release?
Regards,
Theo
tioannidis
on 5 Apr 2019
I think it's the Nextcloud update, which triggers the rescan. And this issue exists since News 13.1.0
I did check the code but I'm not sure where I could change the config for favicon.
Grotax
on 5 Apr 2019
https://github.com/ArthurHoaro/favicon/blob/master/README.md#configure
The favicon service is used across multiple files. You may introduce a wrapper or decorator.
The mail app is using the same library. Above code might be handy for you. I guess mail app does not use the cache feature from the favicon lib.
kesselb
on 9 Apr 2019
Fixed by #485
Grotax
on 10 Apr 2019
This should be fixed in 13.1.6
I'm currently not sure how the update process for apps works but if it's like
rm -rf $app
tar xf app.tar.gz
Then it should work fine.
Otherwise you might need to delete the url* files in the cache one time.
Grotax
on 11 Apr 2019
After updating the News app, and rescanning the files, the error was gone :+1:
AquaL1te
on 11 Apr 2019
Cool, thanks for the feedback
Grotax
on 11 Apr 2019
Updated NC today from 15.0.7-15.0.8.
News app 13.1.6 was already installed before upgrade.
After upgrade I still got the message as stated in this issue.
rm url* in the cache folder and rescanning files made it disappear as mentioned in https://github.com/nextcloud/news/issues/484#issuecomment-482089430 .
Running fine now.
mjanssens
on 18 May 2019
Why is this always coming up over and over again only for the news app? The only failing integrity checks always originate from News. All other apps and there are many never show any of that behavior. What's going wrong there? Same again now when updating to 16.0.1. News app is 13.1.6.
=======
- news
- EXTRA_FILE
- vendor/arthurhoaro/favicon/resources/cache/url62f3ff5e77de86cbd502d3c35d3321c3
- vendor/arthurhoaro/favicon/resources/cache/url60b21b80678c03f8492521c82faa1869
- vendor/arthurhoaro/favicon/resources/cache/url54e93a40963a951e1d78f5598986ef29
- vendor/arthurhoaro/favicon/resources/cache/urlb90bf36c3407789d087b074d3a3c91e1
- vendor/arthurhoaro/favicon/resources/cache/url26d065d8a4ffa52ac7cb9246fea84ff2
Raw output
==========
Array
(
[news] => Array
(
[EXTRA_FILE] => Array
(
[vendor/arthurhoaro/favicon/resources/cache/url62f3ff5e77de86cbd502d3c35d3321c3] => Array
(
[expected] =>
[current] => 3375d39f6a8df25e0a2d732ea5d673e9ab116b65c58e9ca6966fe57187211b670fa0d33897f7e3abca59ce35b72b9ccfccc400119eb2c97ce2605c6f73fdc3fd
)
[vendor/arthurhoaro/favicon/resources/cache/url60b21b80678c03f8492521c82faa1869] => Array
(
[expected] =>
[current] => c8c8ba3e086029351e1d52103243ae3f21e1d6a3cb63e2146f9e556cf35ffae672525f731f04af0cc2f6da6a5a0bf8822446931d427c21e31cb593d98b674914
)
[vendor/arthurhoaro/favicon/resources/cache/url54e93a40963a951e1d78f5598986ef29] => Array
(
[expected] =>
[current] => 504196d4cdd29d1036312d658465ca5ca935218c7a2a07d9ea23239781954311802c304e6a59a01673c4d2c604bd0cd6f155d60b646c59d14a750ec17b930ad9
)
[vendor/arthurhoaro/favicon/resources/cache/urlb90bf36c3407789d087b074d3a3c91e1] => Array
(
[expected] =>
[current] => a77b32c0421d5453c9b97a0aec1b855af16a387c8aac4360c046544ea867613f7bbf67bdec93e2f75510c5b2fa7421fe29440a9deed07b6993659ec174fe99c1
)
[vendor/arthurhoaro/favicon/resources/cache/url26d065d8a4ffa52ac7cb9246fea84ff2] => Array
(
[expected] =>
[current] => 3525842ca3b9366de81f09c31e54efe2248abc0512ef2c1078ef6205e67a345247ddebe86bf7522db1b564974d603338494923d9f1a0c92fb11fc42c1335cf1d
)
)
)
)
rayfun
on 26 May 2019
The issue itself is fixed. Delete the files in vendor/arthurhoaro/favicon/resources/cache/ and trigger a rescan.
kesselb
on 26 May 2019
It's absolutely clear to me what needs to be done but why do I have do it? No other app requires manual fixing after an update. Only news shows this behaviour over and over again.
Shouldn't such tasks be handled as part of the update process?
rayfun
on 26 May 2019
I don't know what "such tasks" are but if you think an update should remove content that might be faulty, that's never going to happen. Its not an option to even remove system files as a plugin. And just removing system files in case they were wrong seems shitty.
SMillerDev
on 26 May 2019
For me it popped up for the very first time when upgrading to NC17 beta1.
As you said it should have been fixed with #485 I am unsure if this is a new problem or something else…
tobiasKaminsky
on 16 Aug 2019
So my guess would be that you had a older version of news installed and never deleted the files in the cache directory.
Grotax
on 16 Aug 2019
I am not sure
- I was on NC16, no files integrity problems
- I switched to NC17 beta1, no news update
- I manually enabled untested news app
- suddenly there was this warning
I enabled news app on my local test system, where news was never installed, and there is no warning with latest version, therefore I close it.
Thank you!
tobiasKaminsky
on 16 Aug 2019
Unfortunately this issue is not fixed. News app is still writing Cache to vendor/arthurhoaro/favicon/resources/cache
mw80
on 30 Sep 2019
did you update to 14.0?
SMillerDev
on 30 Sep 2019
And did you delete the files manually?
Grotax
on 30 Sep 2019
I updated to 14 and deleted the cache after each nextcloud update. I thought it was already fixed with 13.1.6. I will check after next nextcloud update again. Thanks.
mw80
on 30 Sep 2019
Hm, I found again files in /nextcloud/apps/news/vendor/arthurhoaro/favicon/resources/Cache. This should not happen, correct?
mw80
on 1 Oct 2019
Related issues
criwe
·
7Comments
flurischt
·
3Comments
hanzei
·
7Comments
j-ed
·
7Comments
bcutter
·
5Comments
Most helpful comment
I'd say system tmp is better. It's a cache after all.