Closed Bug 1215635 Opened 4 years ago Closed 3 years ago
Not getting consistent notifications during testing of Buddy
Several members of the QA team who have tested BuddyUp recently have reported not consistently getting notifications. This issue has occurred using both the Flame device as well as the Z3 device. Most recently Isabel did some testing and reported her logs in Bug 1142155#c10. She said she did not get notifications 50% of the time. fredy has also last reported that he was not consistently receiving them as well. We will use this bug to report our results and discuss what might be occurring here.
Other testing comments from yesterday - testing occurred on Flames with Marko and Yunito: I had positive results on notifications before test day, but now i tested with Yunito and he was able to get ntoifications but I didn't - both had flames with latest builds. I'm getting emails but not notifications. I also noted that when it's about to recive notification on screen, you get small icon of loading data (next to the wifi/sim icons) and it should pop up notification after that, but nothing happens now
Something to note about all notifications: If you are viewing a question, you won't get notifications for it. Instead the question will update to show the new content. To fully test notifications, make sure to leave the question page. Possibly by closing the app or by navigating to a different question page.
Hi, Here some feedback after more tests: It is confirmed that in that scenario you will not receive a notificatin, when the question view is open. But, there are still missing notifications. According to the tests it seems something user related. I flashed one device pushed buddyup, used it with a new user and notifications were working, then I removed the app, restarted the device and pushed the app again, then I used an older user who was not receiving notifications and again, notificatios are missing. That is strange but I do not have a better explanation. In the screenshot attached you will find a summary of the tests, it could not be clear, please let me know any doubt or comment.
[Blocking Requested - why for this release]: Notifications are important to the BuddyUp experience - as detailed in a email from UX - From Jacqueline: "We cannot expect the user to repeatedly check the app for a response. We currently give them no indication about when this response might come in and it would be very frustrating for the user to check repeatedly and receive no answer. This might result in them missing the answer altogether or being unclear about what they should be doing next. Also, this would be inconvenient for the user who is answering questions, as they won’t get any notification if the user has a follow up question or needs more help"
blocking-b2g: --- → 2.5?
Testing today on Production BuddyUp after discussion with Kadir: https://docs.google.com/spreadsheets/d/1RwrDyLqSUTYndQGIh20qgoh4HeF74QWK3Ci59aFXm7k/edit#gid=0 As you can about 1/2 the time I did not receive notifications. Testing conditions are listed on the sheet.
A quick update: Today I was testing notifications. I am not facing the previous problem I had with certain users. In fact today I received the notifications for each user that were missing. Marcia is it ok for you too, right?
(In reply to Isabel Rios from comment #7) > A quick update: > Today I was testing notifications. I am not facing the previous problem I > had with certain users. In fact today I received the notifications for each > user that were missing. > > Marcia is it ok for you too, right? Isabel: I will test today and let you know. Everyone testing in the bug today needs to do the following: (1) Use the latest pull from Github (2) Don't worry about what version of Fx OS you have - 2.5 or 2.0 is fine (3) Use existing user accounts and create new accounts (4) Report any notification failures right away
Ok, my tests were with latest app from Github with existing users with 2.5 on Flame. Will try also with new ones. Thanks
SUMO has moved to Lithium and this bug is for a SUMO project that isn't around anymore. Given that, I'm closing as WONTFIX.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.