This bug did not occur when I switched back to 1.12 or a previous version, so it is a bug with pre-release 5.
I get the same issue. This has NOT been resolved. If it has, what is the fix for it?
Reporter: Benjamin Willcox
Assignee: (Unassigned)
Created: 2018-06-28T15:07:57Z
Updated: 2025-04-27T15:50:00Z
Resolved: 2018-06-28T21:12:17Z
Confirmation Status: Unconfirmed
Labels:
Retrieved 2025-09-15T13:43:24Z
I get the same issue. This has NOT been resolved. If it has, what is the fix for it?