Luis Rivera

After experiencing the same issue I started digging. Go to Chrome Developer Tools / Application > Service Workers When reloading the page the service worker changes from sw.js to OneSignalSDKWorker.js...

Problem found. According to OneSignal documentation their service worker overwrites other service workers. To fix this '@nuxtjs/onesignal' imports sw.js (the sw created by `@nuxtjs/pwa` with workbox) into OneSignalSDKWorker.js as recomended...

> ```ts > build: { > transpile: [ > '@fortawesome/fontawesome-svg-core', > '@fortawesome/pro-solid-svg- > '@fortawesome/pro-regular-svg-icons', > '@fortawesome/pro-light-svg-icons', > '@fortawesome/free-brands-svg-icons' > ] > } > ``` The transpile should include "@fortawesome/vue-fontawesome" too....

I get this error only if i try to verify the token generated by `createCustomToken`. If you pass the token to `signInWithCustomToken` in the client app then get the user...

Fun thing.. Mine was partially "working" for months (no recordings tho), then I decided to "Pull latest images and Restart" and now I'm part of this thread.