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

[bug] Unable to subscribe to push notifications with Toot! on iOS #1139

Closed
QuietMisdreavus opened this issue Nov 24, 2022 · 5 comments
Closed
Labels
bug Something isn't working not implemented yet We probably will implement this. But we haven't yet ;)

Comments

@QuietMisdreavus
Copy link

Describe the bug with a clear and concise description of what the bug is.

Mastodon-client apps on iOS do not seem to deliver push notifications for a GTS instance i recently joined. Metatext popped some error dialogs upon first signing in (that i cannot reproduce), but Toot! has a specific button to enable push notifications, which returns a 404:

iOS dialog saying "Failed to enable notifications: Server did not return an OK response code (404)"

What's your GoToSocial Version?

GoToSocial 0.5.2 git-c31f219

GoToSocial Arch

(unknown - i am not the admin of this instance)

Browser version

No response

What happened?

The "Notifications" feed loads fine while in the app (both Metatext and Toot!), but iOS apps do not generate push notifications this way, so it requires manually checking the feed to see notifications of any kind.

What you expected to happen?

Expected the app to subscribe to push notifications similarly to how Mastodon instances can.

How to reproduce it?

  1. Use Toot! to sign in to a GTS instance.
  2. Open the in-app settings menu, either through the three-dot menu in the corner, or via the "Settings" link in your profile view.
  3. Scroll to the "Notifications" heading.
  4. Tap "Enable Notifications".

Anything else we need to know?

No response

@QuietMisdreavus QuietMisdreavus added the bug Something isn't working label Nov 24, 2022
@tsmethurst
Copy link
Contributor

We don't implement push notifications yet so that makes sense :D

@tsmethurst tsmethurst added the not implemented yet We probably will implement this. But we haven't yet ;) label Nov 24, 2022
@QuietMisdreavus
Copy link
Author

That makes sense! Thanks for the update ❤️

@whtiehack
Copy link

hi, is there any update on this now?

@tsmethurst
Copy link
Contributor

hi, is there any update on this now?

nope! we still don't implement them, and it's not on the roadmap; likely this is a nice-to-have that we'll work on once we're in beta

@daenney
Copy link
Member

daenney commented Jan 25, 2024

We don't have push notification support, so it's not so much a bug. I'm going to close this one in favour of #1350, as that's the feature request for WebPush which would resolve this. Feel free to subscribe to that one if you'd like to get updates when work starts on that. Though it's probably going to be a while longer still 😅.

@daenney daenney closed this as completed Jan 25, 2024
@tsmethurst tsmethurst closed this as not planned Won't fix, can't repro, duplicate, stale Apr 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working not implemented yet We probably will implement this. But we haven't yet ;)
Projects
None yet
Development

No branches or pull requests

4 participants