Patrick Remy

Same for me, but as far as I know I am not importing myself those sort of components. I am using vite 2.3.8 and nuxt-vite 0.1.1, but also with the...

As a workaround, you can replace `nuxtron build` with a custom npm script ``` "scripts": { "build": "npm run build:clean && npm run build:renderer && npm run build:background", "build:clean": "rm...

Same now here.. UPDATE: Fixed by recloning!

Which API are you using for sending pushes to FCM devices? Does it work for real Android devices? Did you properly set the `senderId` according to your Firebase project?

In my tests I used the HTTP API, you could easily test it via curl: https://firebase.google.com/docs/cloud-messaging/http-server-ref

Yes, a release would be nice!

Please see this issue, the howto is no longer working: https://github.com/Patrick-Remy/howto-fedora-coreos-hetzner-cloud/issues/1 It's a bit sad, that the only solution is to resize the VM down afterwards, but see this cleaner...

I'm sorry, I do not plan to update it, the old documentation was already time intensive and I did setup my coreos server, but feel free to update my documentation...

I can confirm, that I also experience readable streams from client side, stop receiving any messages after a few days, sometimes weeks. I enabled debug output via `GRPC_TRACE=connectivity_state,health_check_client,executor,http,http_keepalive,http2_stream_state,call_error,op_failure,timer,subchannel,server_channel,client_channel_call,handshaker` and `GRPC_VERBOSITY=DEBUG`,...

I am not sure, if that helped, and if my bug was related to grpc or to the grpc server side application. Some months since that, the stream worked pretty...