[HOLD for payment 2024-08-14] [Troubleshooting] Make it possible to export network queue

[puneetlath]

Similar to how we make it possible to export Onyx state in the Troubleshooting section, let's make it possible to export the network queue. This will help us in scenarios where we need to see what is happening with the network queue in order to be able to troubleshoot an issue.

Issue Owner

Current Issue Owner: @puneetlath

[melvin-bot]

Triggered auto assignment to @greg-schroeder (NewFeature), see https://stackoverflowteams.com/c/expensify/questions/14418#:~:text=BugZero%20process%20steps%20for%20feature%20requests for more details. Please add this Feature request to a GH project, as outlined in the SO.

[muttmuure]

@adhorodyski @hurali97 could you comment on this one and we'll assign you?

[hurali97]

Hey @puneetlath 👋

I agree that we should be able to export the network queue but let's say, the user is experiencing an issue and we ask him to export the network queue using this new feature and when he does it and shares with us, the network queue is empty, as we know that the queue gets empty over time. In such a case, this feature won't be of helpful.

My proposal is to allow exporting network queue but also allow exporting the network requests and responses. This will come in handy especially on Android and iOS, where we lack the remote debugging. In some cases, it might be useful to analyse the responses from the network. Though, there are some constraints like:

• There's auth token and user specific details, which we will have to hide
• The record for keeping the network response will grow over time, so the idea is to not persist this record at all
  • Which means that we will keep this in memory and as soon as the user closes the app, this will be reset and rightly so because we will be only interested in the latest network responses.
  • Also, for in memory record, we can set a limit to how much we want to save because we don't want to bloat the memory.

Let me know what you think of this 👍

[puneetlath]

That sounds good to me. But mind posting that in the #newdot-quality room for some more eyes first?

[puneetlath]

It's being actively worked on and is getting close.

[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.17-2 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• feat: log network response and request with filter options in debug console #45769

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

For reference, here are some details about the assignees on this issue:

• @hurali97 does not require payment (Contractor)

[melvin-bot]

BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

• [@hurali97] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.
• [@puneetlath] Link the GH issue for creating/updating the regression test once above steps have been agreed upon.

[melvin-bot]

Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.

[puneetlath]

Looks like @allroundexperts reviewed this one so needs compensation.

Payment summary:

• C+ - @allroundexperts - $250

Thanks y'all!

[JmillsExpensify]

$250 approved for @allroundexperts