Parse Server crash on FCM network error using http/2

[mtrezza]

New Issue Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.
• I can reproduce the issue with the latest versions of Parse Server and the Parse Server Push Adapter.

Issue Description

The http/2 implementation in firebase-admin throws on network errors instead of handling them, which lets them propagate to the node process, which eventually crashes the process.

• For GOAWAY errors a fix has been implemented with Parse Server crash on FCM response GOAWAY #340.
• For other network errors such as ECONNRESET there is no easy remediation.

The proper solution for any network error is to fix firebase/firebase-admin-node#2789, for example via an event listener.

Steps to reproduce

This issue occurs on network error events, such as ECONNRESET.

Actual Outcome

Unhandled error crashes app.

Expected Outcome

Error should be handled by the firebase-admin.

Workaround

• Use the older version HTTP/1.1 by setting fcmEnableLegacyHttpTransport: true in your push options.
• Catch the error in a global Node process error handler.

Environment

Client

• Parse Server Push Adapter version: 6.8.0

Server

• Parse Server version: 7.3.0

[parse-github-assistant]

Thanks for opening this issue!

• 🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.

[mtrezza]

This issue needs to be fixed first in the firebase-admin SDK, see firebase/firebase-admin-node#2789.