Open Softvision-PatriciuPop opened 1 year ago
➤ Yoana Rios Diaz commented:
Patriciu Pop I’m getting up to speed with this bug as I’m not 100% familiar with this feature I did find however this Note to QA from the implementation ticket ( https://mozilla-hub.atlassian.net/browse/FXIOS-6019 ) For QA:
Please test that the engagement notification is send > 48h after first install when user is inactive after the first 24h and as well that it’s not send when the user is active in the second 24h. Additionally the users notification preferences need to be respected.
Please note that the notification will not be send exactly at 48h. The scheduling depends on when Apple wakes the app up in the background. It should happen every 4 hours but can also take much longer.
I think changing the system time right away to 2 days after might be breaking the flow of allowing Apple to wake up the app in the background and scheduling the notification.
➤ Yoana Rios Diaz commented:
Andrei Bodea you tested https://mozilla-hub.atlassian.net/browse/FXIOS-6019 ( https://mozilla-hub.atlassian.net/browse/FXIOS-6019|smart-link ) and tip that you could share that will help testing this issue?
➤ Yoana Rios Diaz commented:
Checking the implementation I realize we also check that the user allows “Tips and features“ in the App Settings > Notification
!Simulator Screenshot - iPhone 14 - 2023-05-11 at 13.33.11.png|width=1170,height=2532!
➤ Patriciu Pop commented:
Hi Yoana Rios Diaz ! Sorry for the late reply, I’ve checked the device’s notification settings and the Firefox notifications are enabled. Also, I forgot to mention in the notes that I’ve enabled the “Tips and Features“ toggle in the app itself.
On the Android side changing the system time to 4h in the future was enough to trigger the notification. If we can’t use the same trick here is there another way we could force the notification to appear aside from waiting 2 days?
➤ Yoana Rios Diaz commented:
Hi Patriciu Pop if the permission and Tips and Features are enabled I think the remaining issue is the background task to schedule the notification, we don’t have any control over this is Apple who wakes up the App which should happen every 4h.
I think is a good idea to first change the time to 4h after to see if that triggers the background task that schedules the notification. Another idea will be to install the app and wait 4h with the same purpose wait for the system to schedule the notification and then update the system time to 48h after the install.
➤ Patriciu Pop commented:
I’ve tested just now by moving the time forward 4h, then 24h, and another 24h with no luck. I’ve set-up a new profile on the physical device and I’m waiting for the 4h to elapse before trying again. From what I saw there isn’t a notification option on the xcode simulator, is this something that can be verified only on physical devices?
➤ Patriciu Pop commented:
Update: I’ve retested this by waiting 4h to pass naturally and then changed the system time in the future, but I haven’t managed to trigger the notifications. I also left the testing device on during the weekend and after 2 days no notifications were displayed.
@Softvision-PatriciuPop I verified that the notifications are indeed working using TestFlight build 30885 as well as with a build from Xcode. Please note that using a simulator you will not get the notifications - you have to test on a real device. Apart from notifications being allowed and "Tips and Features" being enabled the app must also allow Background App Refresh. Could you check that this is enabled in Settings.app on your test device? Here is how I tested:
Hope that helps.
➤ Patriciu Pop commented:
Hi Winnie! Thanks for the following up. I've verified that both the "Tips and Features" and "Background App Refresh" toggles are enabled and I've tried the steps provided above with and without being enrolled in the experiment. Sadly I could not get the notifications to trigger, I've also asked another colleague to verify this and she had the same issue.
➤ Winnie Teichmann commented:
Patriciu Pop I made some changes that went into the latest Testflight build for v114 (31138) - could you please verify that the notifications work now?
➤ Winnie Teichmann commented:
Patriciu Pop could you please test the new beta build (31343)? This one works for me even with developer mode off on the device.
➤ Cosmin Muntean commented:
Hi Winnie Teichmann ! Patric is currently on PTO, but I have tried to verify this issue and I can still reproduce it, there is no notification triggered. I have verified this with the build for v114 (31343) from Test Flight on iPhone 13 mini (iOS 15.6). Here are the steps that I have tried:
Actual results:
I have also tried with the Firefox app closed, or restarting the Firefox app after enrolling in the experiment, but the notification is still not triggered. Please note that the movie device is not connected to any other devices. The "Background App Refresh" option is enabled.
Please let me know if I have missed any steps or if there is another Experiment that I can use for testing this.
➤ Cosmin Muntean commented:
In the past few days, I have re-tested the iOS notifications using the Firefox Beta 9000 (31343) build on an iPhone 13 mini with iOS 15.6.
With the help received from Winnie Teichmann I have managed to trigger the notification from each treatment branch of the “Release iOS re-engagement notifications A/B experiment 114” experiment.
Considering this, we can mark this ticked as verified fixed.
Prerequisites
Steps to reproduce
Expected behavior
Actual behavior
Device & build information
Notes
┆Issue is synchronized with this Jira Task