-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Populate chats from message center #9457
Comments
cc @Julesssss @AndrewGable – I don't know when I'll have time to look into this, but I think it's a good idea and might be a way to fix the "ghost messages" issue |
This is internal because push notifications can't be tested by external contributors |
I can't speak for iOS here, but if a user opens the Android app by tapping a notification we can retrieve the app data from the Intent bundle. It seems that accessing the NotificationManagerService at app-open to read all notifications is NOT possible. This doesn't solve for all cases, because the notification will only contain data for that specific chat. UNLESS we start sending all unread message data as part of the notification. Slightly hacky and maybe we'll eventually hit the 4kb limit, but this handles most cases. |
Haven't had time to investigate this yet. If anyone wants to help out with this feel free to self-assign and we can collaborate on it. If it's viable I think this could be a game-changer for the mobile apps. |
No updates, remains low priority. |
Hey @sketchydroide, do you know if it is possible to read all notifications from NotificationCenter in iOS? The only thing I could find was this hack from a 10 year old StackOverflow post. It's not possible on Android, we can only access the notification intent & bundle if the user taps the notification. |
I don't think so, but not 100% sure, notifications should be read if you are listening to them |
Does this listener require that the app is open and|or in the foreground? |
for push notifications no, iOS will open the app if necessary, or the push is open, if the app is in background it can still process notifications |
Held on the P/S |
High-level design doc in review |
Got tied up with deploy fires and improvements |
Posted about this in slack: https://expensify.slack.com/archives/C04E99DVBTP/p1688080702244769 |
Was OOO most of last week, I anticipate progress on this closer to the end of the week |
No update yet this week, but this has been in the back of my mind. Just spread a little thin at the moment. |
No update 😞 |
Same |
This issue has not been updated in over 15 days. @roryabraham eroding to Monthly issue. P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do! |
No update |
No update |
Going to close this as it's not clear that it will be necessary in a world with #reliable-updates |
Problem
NewDot mobile is prone to "ghost chats". They happen when:
Solution
Disclaimer: I don't know if this is actually possible, but it's worth looking into. That's why I'm creating this issue...
When opening the app, read any new notifications in the "message center". Use the payloads of those notifications to populate the chats you received, without needing a network connection.
The text was updated successfully, but these errors were encountered: