-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Add new Leanplum E_Changed_Default_To_Fenix Event #12103
Comments
cc @cbonacuse this has landed! |
Hi, verified as fixed on both the latest ✔️ NightlyGoogle Pixel 3a - device ID Huawei Mate 20 Lite - device ID OnePlus A3 - device ID ✔️ BetaGoogle Pixel 3a - device ID Huawei Mate 20 Lite - device ID 48e981ae-5ec4-43f7-bbb2-5d4532f15627 OnePlus A3 - device ID |
@AndiAJ - it looks like the Beta screenshots are for the Search Widget event - did you try with this E_Changed_Default_To_Fenix one? @jhugman - I tested this on my Google Pixel 3 with Nightly Build 200730 and am not seeing the event fire, even though the default_browser attribute is correctly changing from org.mozilla.firefox to org.mozilla.fenix. I tried both cold starting and also backgrounding the app, opening the app, and then killing. |
Hi @cbonacuse , my bad, mixed up the screenshots, sorry for the inconvenience. ✔️ BetaGoogle Pixel 3a - device ID Huawei Mate 20 Lite - device ID |
@cbonacuse are you still not seeing it on your end? Want to make sure this is properly resolved 😄 |
@sblatz thanks for following up! I am not still :( |
@AndiAJ are you able to tell me the steps you used to verify this so @cbonacuse can confirm on her end? Also are you verifying using Glean or Amplitude 🤔 |
Hi @sblatz & @cbonacuse , I'm using only Leanplum.
► Re-checked on today's Nightly Build Google Pixel 3a - device ID Huawei Mate 20 Lite - device ID |
@AndiAJ & @sblatz I just did another test myself with the following steps and I'm still not seeing this on my Google Pixel 3 (OS 10 & Nightly build 200805) when I do a cold start or background the app. I'm checking in Leanplum as well. My Leanplum ID: 4ead7db7-0a20-4f5e-911b-4097b3db4048 When you say 'open device in a separate tab', are you not using an actual device but rather simulating it somehow?
|
Hi @cbonacuse & @sblatz I've just re-checked this matter on Nightly 200805 with a Google Pixel 3a (Android 10) using the above mentioned STR [added a couple of notes and an extra step (Step 6)] and everything seems to be working fine. Device ID -
|
@AndiAJ I followed your same steps above and I'm still not seeing the event for 4ead7db7-0a20-4f5e-911b-4097b3db4048. Could it have something to do with my device (Google Pixel 3 - yours is a 3a)? |
Hi, @cbonacuse , yes, Google Pixel 3a I've checked the timeline of your device and it dates back to the 3rd of April. |
@AndiAJ I can definitely try to install it again and see if that works. Is this in Beta yet as well? I can also test there. |
Hi @cbonacuse , yes it is available on today's Beta build 80.0.0-beta.4. (task index link if you want to install it) |
@AndiAJ I deleted and then re-installed Nightly and found my new device ID. I'm still not having the event fire for me but I see the attribute is changing showing that Nightly is my default browser. Device ID: 53d503bf-1812-46c0-ab26-fa42f7e00bb9 Steps to reproduce:
Happy to hop on a call next week to discuss this further too @sblatz |
The following were identified as missing in Fenix during a recent test by the Mobile Engagement team. This event by a similar name (E_Changed_Default_To_Fennec) is present in Fennec. This is requested to be in market by 8/25/20 (release 80).
This should be fired when the user changes their device setting to have the default browser sent to Firefox (Fenix), regardless of the app being presently opened or not.
Tasks:
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: