Skip to content
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

Support receiving notifications via a long connection when running in the background to make it usable on devices that do not support GMS. #8014

Open
NCPSNetworks opened this issue Jun 13, 2024 · 0 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@NCPSNetworks
Copy link

Per Mattermost guidelines, GitHub issues are for bug reports: http://www.mattermost.org/filing-issues/.

For troubleshooting see: http://forum.mattermost.org/.
For feature proposals see: http://www.mattermost.org/feature-requests/

If you've found a bug--something appears unintentional--please follow these steps:

  1. Confirm you’re filing a new issue. Search existing tickets in Jira to ensure that the ticket does not already exist.
  2. Confirm your issue does not involve security. Otherwise, please see our Responsible Disclosure Policy.
  3. File a new issue using the format below. Mattermost will confirm steps to reproduce and file in Jira, or ask for more details if there is trouble reproducing it. If there's already an existing bug in Jira, it will be linked back to the GitHub issue so you can track when it gets fixed.

Summary

Mattermost Mobile cannot receive push notifications in regions where FCM is blocked or on devices without GMS installed.

Environment Information

  • Device Name: iPhone 13 Pro Max
  • OS Version: 17.5.1
  • Mattermost App Version: 2.16.0
  • Mattermost Server Version: 9.8.1

Expected behavior

I noticed that Mattermost Mobile cannot receive push notifications in regions where FCM is blocked or on devices without GMS installed.

Possible fixes

By establishing a long connection directly from the client to the Mattermost server, bypass FCM to receive push notifications (the client needs to run in the background).
It can be provided as an optional feature for users, disabled by default. (The benefit is that it supports these devices without requiring many changes, though it does consume slightly more power.)

@amyblais amyblais added the kind/feature Categorizes issue or PR as related to a new feature. label Jun 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

2 participants