-
Notifications
You must be signed in to change notification settings - Fork 33
[Bug] No push notifications after reinstalling #969
Comments
I think I'm also seeing this bug (or something similar). After migrating data to a new phone, push notifications didn't work. I've tried uninstalling, reinstalling, etc, but haven't been able to get them working. |
Another datapoint here is that I can't reproduce this issue when building from source and running via android-studio. I don't hit #965 doing this either, which leads me to believe the two bugs are probably related somehow. Some data is probably being saved somewhere it shouldn't be, which is causing the app to misbehave on reinstall. |
I tried installing from F-Droid just to test, and I can confirm that notifications still don't work. I don't encounter #965 when installing from F-Droid though. |
I may have found another way to reproduce this bug (or maybe it's a separate issue, not sure), which is to enable and disable unified push. Specifically, what I did was: Install ntfy Hopefully I'll have some time this weekend to experiment with it. |
Same here, this bug happens to me started few versions ago. Reinstalling, clean data, switch over to unified push, nothing works. |
Funnily enough push notifications suddenly started working again for me last week after being broken for ~3 months. |
I finally got round to setting up a Unified Push system, and confirmed that notifications from Megalodon still don't work even with that. Unified Push works, but Megalodon doesn't. |
Describe the bug
After reinstalling Megalodon to troubleshoot #964 and #965, Megalodon is no longer sending push notifications. I have ensured that the app has notification permission, ensured notifications are enabled in the app, and have reinstalled several times, but the issue persists. I am still getting push notifications from the official Mastodon app, but not Megalodon. Even without Mastodon installed to prevent conflicts, I still don't get push notifications from Megalodon.
Given that this occurred after a reinstall, I'm wondering if this is related to #965.
To reproduce
Steps to reproduce the behavior:
Does this happen in the official app?
Does this issue also occur with the respective upstream release?
No (Mastodon Play Store latest)
Screenshots and screen recordings
N/A
Version
Megalodon version: 2.1.6+fork.110 (110) (Play Store latest)
Crash log
N/A
The text was updated successfully, but these errors were encountered: