I can reproduce the issue with Glitch 2022. We'll be getting a 4.8.2 maintenance release out this week and we'll include the fix for this. In the meantime it's possible that renaming it to Glitch (2022) might fix it.