-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix the FCM token error #431
Conversation
vector/src/gplay/java/im/vector/app/push/fcm/NotificationTroubleshootTestManagerFactory.kt
Show resolved
Hide resolved
Co-authored-by: ClaireG <[email protected]>
|
||
<!-- Allow system certificates for firebase --> | ||
<domain-config cleartextTrafficPermitted="false"> | ||
<domain includeSubdomains="false">firebaseinstallations.googleapis.com</domain> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we consider the store dimension gplay vs fdroid before adding this domain config?
We may ignore this remark because fdroid variant is built without pinning, but I prefer mention it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's possible to have a specific network security config for gplay + withpinning variant
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch, I just updated the PR and split the config file for both variants
d26e79b
to
c120368
Compare
#402
The FCM token could not be retrieved because of the pinning restriction which does not allow the system certificates. These certificates are required to request the FCM token through the firebase API. This PR allows the use of the system certificates for the firebase domain only.
This PR also hide the "Test push" step from the "Troubleshoot Notifications" screen. This step was triggering a notification using the push server
notify
endpoint. The push server has been moved to a new internal sygnal server which is only accessible from the Synapse. This step will be hidden while there is no equivalent public API to trigger a notification.