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

Migration from old client does not enable notifications #1723

Closed
Skirmisher opened this issue Jul 18, 2020 · 6 comments · Fixed by #1821
Closed

Migration from old client does not enable notifications #1723

Skirmisher opened this issue Jul 18, 2020 · 6 comments · Fixed by #1821
Assignees
Labels
S-Critical Prevents work, causes data loss and/or has no workaround

Comments

@Skirmisher
Copy link

When upgrading from old Riot-Android to Element today, I had to manually check "Enable notifications for this session" under notification settings in the app. I gather that I would have been missing notifications had I not checked all the app settings (or if I hadn't understood the potentially confusing setting text and ignored it). If this requires intervention by the user for some reason, they should be prompted about it on first startup after migration.

@o0laxkilla0o
Copy link

I just checked my Element android client and can confirm this setting was disabled. I will reach out to my users which is a good mix of IOS and Android to see how their clients behaved after their migrations.

@o0laxkilla0o
Copy link

I have confirmed one IOS user has experienced this, after enabling notifications flowed as expected. It is late here tomorrow once I get more responses ill update the issue.

@hpdeifel
Copy link

I've observed this for three users, which is everyone that upgraded straight from riot to element. When I installed the beta a few weeks back, it correctly migrated the setting.

@RussellAult
Copy link

I can confirm this for myself and another user. We both upgraded with the Google Play change-over, and neither of us were receiving notifications after the upgrade.

If it makes a difference we're using a private HomeServer, and when I ran the "Troubleshoot Notifications" function, in addition to notifications being disabled for the session, it was complaining that the FCM token wasn't registered to the HomeServer. Hitting the "register" button solved that problem, and enabling session notifications got notifications flowing again. After this, enabling session notifications was enough for things to start working again for the other user as well.

I can't say for sure, but it also looks like it's not importing the advanced notification settings either (e.g. I swear I had encrypted messages sent to a group set to "noisy").

@bmarty bmarty added this to the Post-Element release milestone Jul 21, 2020
@ganfra
Copy link
Member

ganfra commented Jul 23, 2020

I can't reproduce it at the moment, tried multiple way. Maybe there was some malformed data in push rules.
We could offer to show notification troubleshoot for FTUE?

@532910
Copy link
Contributor

532910 commented Jul 26, 2020

I've already enabled notifications for this session on 3 phones after update from Riot to Element. All three were samsungs.

@BillCarsonFr BillCarsonFr self-assigned this Jul 27, 2020
@bmarty bmarty added S-Critical Prevents work, causes data loss and/or has no workaround and removed 🔥 fire labels Oct 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-Critical Prevents work, causes data loss and/or has no workaround
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants