YouTube live chat mode does not work for iOS users

According to multiple reports, YouTube live chat mode is not working for iOS users.

YouTube’s live streaming feature allows you to watch videos as they are being recorded in real time. When you’re watching a live stream, the video starts playing as soon as it’s recorded and doesn’t buffer like regular videos.

The live streaming tool that allows creators to interact with their audience via video and chat. It works much like a typical chat room, but with the added benefit of being able to chat with other viewers and send emojis in real-time. One of the best aspects of live streaming chat is the ease with which you can connect with people from all over the world.

Reports of YouTube live chat mode not working for iOS users

Many people have trouble switching the comment view from “top chat” mode to “live chat” mode while broadcasting live on the platform.

When you click the control button, there doesn’t seem to be an option to change. Also, some claim that after touching the button, all they see is a small triangle below it.

Affected users took to social media to express their concern about the bug and also asked the developers to help them fix the bug.

The bug emerged recently and has caused controversy among YouTube creators, especially because it makes it difficult for them to engage with their viewers while streaming.

READ :  Apple Explains How Wi-Fi 6E Works on New iPad Pro

Others have tried logging out and back in to their YouTube account, as well as uninstalling and reinstalling the app on their devices, but that doesn’t seem to solve the problem.

“@TeamYouTube what happened to the switch from top chat to live chat while watching @YouTube live streams?” reported one user.

Another reported, “I’ve done the things listed above, logged in and out of my account, and reinstalled the app on my devices, but I still can’t get the live chat feature to work.”

Official confirmation but no workaround

Furthermore, YouTube has officially recognized this and has identified the problem and is investigating it. However, no official time frame was given.

There are currently no workarounds either.