Re: PS5 version APEX lobby reflection bug

Currently, for some reason, the PS5 version of APEX Legends is experiencing bugs such as lag only in the lobby, synchronization lag, and time-consuming updates. When an ally joins a party, on the screen of the party that joined, they have already joined and clicked Ready, but on this screen they have not yet joined, and if you wait for about 3 or 4 minutes, it will be reflected that they have joined. However, instead of pressing Ready, it is displayed as level 1, and when I thought that Ready had been reflected, on this side, even though I had pressed Ready, only the Ready button at the bottom left was reflected. Therefore, the number part above the character will not be reflected. It usually takes about 10 minutes for a match to start, but during that time the participants are often waiting in a situation where the matching does not start even though everyone has pressed ready. Once the match starts, there will be no lag or synchronization, and you can play comfortably, but if you return to the lobby midway through, the situation will be even worse. Especially if you get a message at the bottom of the screen that your party leader has left during a match, you'll have to go back to the lobby or play with people you don't know. Also, even if you go back to the lobby, the reflection bug has occurred again, and it takes a long time as usual until everyone is reflected as ready, and when you think that preparation is reflected and matched, you may find yourself matching with someone else. I'll do some matchDuring that time, I may be the only one in the match on the ally's screen, so I have to repeat this one-person matching process two or three times in order to restart the match with my party members. By the way, I have tried all possible methods such as restarting and reinstalling, and this bug does not occur in other games, and hugs do not occur. The connection is also comfortable and the game is currently running.For some reason, the PS5 version of APEX Legends is experiencing bugs such as lag only in the lobby, synchronization lags, and time-consuming updates. When an ally joins a party, on the screen of the party that joined, they have already joined and clicked Ready, but on this screen they have not yet joined, and if you wait for about 3 or 4 minutes, it will be reflected that they have joined. However, instead of pressing Ready, it is displayed as level 1, and when I thought that Ready had been reflected, on this side, even though I had pressed Ready, only the Ready button at the bottom left was reflected. Therefore, the number part above the character will not be reflected. It usually takes about 10 minutes for a match to start, but during that time the participants are often waiting in a situation where the matching does not start even though everyone has pressed ready.
[16:10]
Once the match starts, there will be no lag or synchronization, and you can play comfortably, but if you return to the lobby midway through, the situation will be even worse. Especially if you get a message at the bottom of the screen that your party leader has left during a match, you'll have to go back to the lobby or play with people you don't know. Also, even if you go back to the lobby, the reflection bug has occurred again, and it takes a long time as usual until everyone is reflected as ready, and when you think that preparation is reflected and matched, you may find yourself matching with someone else. I'll do some matching. During that time, I may be the only one in the match on the ally's screen, so I have to repeat this one-person matching process two or three times in order to restart the match with my party members.
[16:11]
By the way, I have tried all possible methods such as restarting and reinstalling, and this bug does not occur in other games, and there are basically no bugs. The line is in good condition to play the game comfortably, and I have a wired connection, and this bug started occurring after I upgraded to the PS5 version. I am currently using a wired connection, and this bug started occurring after I upgraded to the PS5 version.