Hi all. Here is my take on the issue:
- The bug was indeed fixed some time ago (just before Christmas last year), but instead as a fix to this similar issue: Unreal Engine Issues and Bug Tracker (UE-53089)
- At that time, we hadn’t released 4.19, but the code had already been branched for that release and so this fix missed the window for 4.19 changes.
- The ticket only reared its head again recently during 4.20 regression testing. An unrelated hot reload issue was found, but it was marked as a regression of this issue, which it is not.
- That was when I was made aware of this thread and everyone’s troubles, and so I came to offer the above code as an official workaround for until 4.20 gets released.
- I have no dealings with our public issue tracker, so I don’t know why UE-52220 has disappeared. It may be due to a false positive on our ‘sanitised for public’ checker, which ensures we don’t accidentally leak confidential information (for clarity: neither this bug nor the fix is in any way confidential).
- UE-52220 is still visible in our internal tracker - no attempt is being made to rewrite history here. I will see about getting the issue made public again.
I’m an internal developer and am not actively looking at public-facing sites for these types of issues, so I only respond to them when I’m made aware. I’m still sorry that people have felt left in the dark on this. But I would advise anyone to raise their concerns with the support teams.
Steve