[HOLD for payment 2024-08-19] [Fullstory] Initializing the Onyx object to identify the user when they have an infinite session on New Dot

[anmurali]

Problem:
Initializing the Onyx object on SignInWithShortLivedAuthToken will make it so a user on Classic with an infinite session, on redirect to New Dot will now be identified in FS. But if they were already on New Dot, and had an infinite session, we will not identify them till they explicitly login next.

Solution:
Initialize this object on OpenApp/Reopen App as well.

Note: While we do this, can we also make it so the Onyx object includes the tryNewDot.classicRedirect.dismissed
If that is true - send true, if false then send false
If that NVP does not exist, send empty

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.18-10 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [No QA] adding new property for userMetadata #46907

If no regressions arise, payment will be issued on 2024-08-19. 🎊

[danieldoglas]

This is done, there's no payment to be made