Troubleshooting: PWA and push notifications

The installable app works on a site that runs at the domain root, for example https://example.com. These steps assume that setup.

The browser does not offer to install the app

Cause. One of these:

• The site is not on HTTPS.
• You are not on a page that carries the manifest. It is linked only on job archive pages, single job pages, and the jobs archive, employer dashboard and candidate dashboard pages you set under Settings > Pages.
• The site has no Site Icon, so the manifest has no icons.
• The site runs in a subfolder. The manifest (/wcb-manifest.json) and service worker (/wcb-service-worker.js) are only served at the domain root.

Fix.

1. Serve the site over HTTPS.
2. Upload a Site Icon under Settings > General. The manifest uses the 192 and 512 pixel versions.
3. Open one of the pages listed above and reload.
4. Open https://your-site.com/wcb-manifest.json in the browser. It should show JSON. If it shows a 404 page, check for a server rule or cache that intercepts the address.

See PWA.

The installed app shows the wrong color

Cause. The manifest takes its color from the Brand colour.

Fix. Change the color under Career Board > Settings > Brand, then open /wcb-manifest.json and check that theme_color shows the new value.

Offline pages do not load

Cause. The service worker only handles /jobs/, /companies/ and /candidates/, and only pages that were visited before are cached. If your job archive uses a different slug, its pages are not cached.

Fix. Visit the page once while online. Use the standard /jobs/ slug if you need offline viewing.

Push notifications do not arrive

Cause. Push is sent only to the native companion app. The website and the installed PWA do not send browser push. The member’s phone must also be registered.

Fix.

1. Sign in to the companion app on the phone. The app registers its push token with POST /wcb/v1/push/register-device.
2. Check the phone allows notifications for the app.
3. Push is sent in the background, so scheduled tasks must run (Action Scheduler or WP-Cron).
4. The mobile app connection needs a valid license. See Troubleshooting: license and updates.
5. A device that the push service reports as no longer registered is removed. Sign in to the app again to register it.

A push is sent for the same events that add a row to the notification bell. See Notifications.