Improve visibility of what is slow in BootsplashVisible

[rlinoz]

Add more spans/logs or some other Sentry features to the existing BootsplashVisible spans to find out what exactly influences the super long spans.

Basically we'd need to divide each underlying process (e.g. the navigation part) into smaller parts that would then show in Sentry so we can see which exact part took so long to finish.

Issue Owner

Current Issue Owner: @BartekObudzinski

[JKobrynski]

While working on the parent issue, we've added a bunch of new spans to track bootsplash time in the app. As of now, all related logic is implemented in Expensify.tsx with one span ending in LocaleContextProvider.tsx

Upon gathering some data and analysing the super long lasting BootsplashVisible spans, it turned out that we are going to need more information to be able to accurately identify problems and then address them. The spans that we currently have are not precise enough for us to be able to do it.

As of now, the BootsplashVisible span has 4 child spans:

• BootsplashVisibleOnyx - to track the time it takes Onyx to init
• BootsplashVisibleLocale - to track how long it takes to figure out the locale that should be used
• BootsplashVisibleNavigation - to track how long it takes for navigation to initialize
• BootsplashVisibleHider - to track the time it takes from showing <SplashScreenHider /> to actually hiding the bootsplash

What we need to do, is introduce more granulation to the current spans, so we can track the underlying processes.

In my opinion, this issue consists of two steps:

1. Figure out which Sentry features we should use, e.g. simply use more child spans, use something different than spans, use spans along with some other Sentry features
2. Implement the Sentry features, making sure spans are ended properly and testing them

[JKobrynski]

Update:

I won't be available next week, I will most likely be back on Monday January 19th. I've already reached out to our team to let them know that this issue is up for grabs and has Critical status. I added all the context that I have about this issue in a comment above. If this issue needs some extra attention during my absence feel free to reach out to @VickyStash who is going to help you find someone to address it. I will continue my work on this issue when I'm back!

[BartekObudzinski]

Hello, I'm Bartek from callstack and I would like to work on this ticket