ERR_FILE_EXISTS in OneSignalSDKUpdaterWorker.js.php

Hi,

The ERR_FILE_EXISTS message you’re seeing is a bug in Chrome that should not be displayed. It appears even on popular sites like PInterest.com. You can find more information about the bug here: https://code.google.com/p/chromium/issues/detail?id=541797

As of Chrome 50 (released a week or two ago), the bug should be fixed.

hello, i have the same Problem after unistalling this Plugin. My Site has a Lag because of that? how can i complete remove everything of this Plugin in my Site?? pls help

Hi,

Sorry for the delay in getting back to you, but if our plugin is uninstalled, it shouldn’t cause any lag. Files are deleted when plugins are uninstalled.

Database settings remain, but we store an extremely small amount of information (probably less than 1 KB of text total), so it should not affect your database performance. I’m not aware of a way to clear database settings on plugin uninstall; this is something built into WordPress, not something we do intentionally.

Are these /wp-content/plugins/onesignal-free-web-push-notifications/sdk_files/ “directory” need to be accessible? or just need *.php files?

Is there any thing need to be adjust on NGINX + PHP-FPM eg: write rules etc?

Hey hernandy,

The reply two weeks ago was a little incorrect. The reason you continued to have the ERR_FILE_EXISTS bug was due to a background worker running as part of the browser (that we register to fetch and display notifications). You have probably fixed the issue since then, but in case you haven’t, you can follow these instructions to remove the background worker: https://documentation.onesignal.com/docs/website-push-common-problems#clearing-your-cache-and-resetting-push-permissions.

The “sdk_files” directory itself does not need to be accessible. Only the three .PHP files inside need to be accessible.

If you’re getting 403 forbidden or kind of similar issues when accessing the files, then your rules will need to be adjusted. I’m not sure whether your current server rules are permissive enough for the files to be publicly accessible.

You’ll see any errors accessing those files in the browser’s developer tools console when you try to subscribe. It’ll be a red error giving you the full URL to the file and letting you know there was some kind of error accessing it.