Hey! Recently a lot of users on my game began reporting issues about not being able to click on a specific prompt within our onboarding.
This was a major issue, and so I went out to try and figure out what was causing it exactly. Now as it turns out this bug was incredibly rare, and it was only happening to a specific subset of users. I believe that this is only happening to specific devices, I thought that originally it was only specific Android devices but one of the users who reported the issue to me said that he was running Linux.
So I think maybe it’s some sort of issue in regards to GetTextBoundsAsync failing to get the font or something? I could be totally off, I really have no idea, but basically whenever you run GetTextBoundsAsync the script can just completely fail.
Any code after the function is ran will never run, and no warning will appear in the output from the API saying that it failed or that it’s having an infinite yield. This issue was very difficult to track down and I believe it could be secretly damaging lots of other Roblox games too especially when it’s included within the onboarding.
I personally cannot replicate this on my device (MacOS), but there’s countless users who have this happen to them where their device fails at this exact step every time.
I also found another DevForum post with a potentially similar issue, except this one was solved and it was many years ago, so hopefully this can help us investigate why this bug started happening.
Also another user provided a timeframe at which this bug began happening, it could be completely off so take it with a grain of salt but he said that the bug began happening around 6/13/26
Reproduction File:
Once again, please note that I have never personally been able to recreate this issue on one of my devices (MacOS & iPhone), and I have also never experienced it on my Roblox account.
One of the users who we’ve spoke about that has experienced this bug in a live experience said that it happened on both Mobile & PC, and we’ve received countless reports from both on our feedback page, so it’s likely account based somehow?
GetTextBoundsAsync Reproduction.rbxl (62.3 KB)
Expected behavior
GetTextBoundsAsync should error instead of infinitely yielding.