Just saying: With proper logging (server and client), debugging and test driven development there wouldn’t be any need to frustrate consumers for getting a better idea of where to dig into the code, which at the very end would not happen at all with solid QA, as this would be flagged as severe BEFORE releasing to the customer anyhow.
There is code responsible for that issue and looking into commits at your repository would already identify the code changes that increased the issue in 4.96. If there aren’t any changes to the responsible code then you are in serious trouble otherwise the direction for the coding team is clearly defined thereof. Next sprint fixed.
Truly the current Tickets doesn’t give them any hint as no stacktrace or other evidence from the users device is provided in the ticket, which could be achieved if a log could be attached.
Just get the information to the team that the vast majority of players do experience this issue for months, period.