Closed ArchBlood closed 2 weeks ago
@ArchBlood What did you modify in the class?
Added the following, no other modifications have been made to the core of v1.17 or the latest version of the module.
/**
* Exclude source map files from being published.
* @inheritdoc
*/
public $publishOptions = [
'only' => [
'firebase-app-compat.js',
'firebase-messaging-compat.js',
]
];
Hmm, can you reproduce the issue on our community (latest develop) version?
Hmm, can you reproduce the issue on our community (latest develop) version?
Currently with the community site the following console errors happen as for this specific error, I have no access to clear cache via File from the community site so I would not know if it can be reproduced on the community site.
Unchecked runtime.lastError: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received
dashboard:1 Unchecked runtime.lastError: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received
dashboard:1 Unchecked runtime.lastError: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received
dashboard:1 Unchecked runtime.lastError: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received
Do you think the error only occurs with the “file” cache backend?
Can you send a screenshot of the console errors? Do they occur on a specific page?
Do you think the error only occurs with the “file” cache backend?
Can you send a screenshot of the console errors? Do they occur on a specific page?
After updating my current test site for #44 I have no errors that are noticeable, I'll have to create a new instance once I'm back at the office, which will probably be around Tuesday due to Monday being Veteran's Day here. I've only tested with File and no other option due to Cron issues with APCu flushing cache when disabling or deleting modules.
Currently the following errors show when accessing the mail module but that can be left for a separate issue, currently I haven't seen the issues reported in https://github.com/humhub/fcm-push/issues/59#issuecomment-2466295289 again since yesterday.
Thanks for the feedback. For the errors in the console, we probably need issues in the core. But I think there was already a PR about this. I'm closing the issue here. If it occurs again, please reopen it. Thanks!
The following error can pop up when clearing cache, it doesn't happen all the time but does happen
Error log
Suggestion
Update the
FirebaseAsset
class as follows which seems to help fix the issue;