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

Error > Icon of notification is not an absolute URL and does not work in mobile and desktop clients #258

Open
cyclistguy opened this issue Jan 24, 2025 · 4 comments
Assignees
Labels
0. Needs triage Pending approval or rejection. This issue is pending approval. bug Something isn't working needs info Not enough information provided

Comments

@cyclistguy
Copy link

Before entering a bug issue, checking if anyone else is experiencing the below. A quick google search indicates several other apps have been experiencing the same.

Upon enabling the flow_notifications app, nextcloud log is flooded with the following errors:

Icon of notification is not an absolute URL and does not work in mobile and desktop clients [app: flow_notifications, subject: \OCP\Files::postCreate]

@blizzz blizzz added 0. Needs triage Pending approval or rejection. This issue is pending approval. bug Something isn't working needs info Not enough information provided labels Jan 29, 2025
@blizzz
Copy link
Member

blizzz commented Jan 29, 2025

Hi @cyclistguy thanks for your report. Which Nextcloud and app version are you running? If you say other apps are suffering from the same issue, have you double check the issues at the server repository?

@cyclistguy
Copy link
Author

Running current version 30.0.5, community docker release. I've tested in three different environments, one being a fresh install, and issue occurs on all three. As I understand it, these errors have existed under previous releases, but were not being displayed in logging. The issue I believe is application specific....just a quick search for a few examples:
nextcloud/survey_client#316
nextcloud/files_antivirus#403

@blizzz
Copy link
Member

blizzz commented Jan 30, 2025

Okay, thanks, I'll have a look, but it may take a bit, due to some absence shorty.

@blizzz blizzz self-assigned this Jan 30, 2025
@dajusc
Copy link

dajusc commented Feb 9, 2025

Thank you for looking into this @blizzz
It would be happy seeing this resolved, as it completely spams the log on my NC 30.0.5 instance and generates several MiB of log entries every day...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0. Needs triage Pending approval or rejection. This issue is pending approval. bug Something isn't working needs info Not enough information provided
Projects
None yet
Development

No branches or pull requests

3 participants