TLDR;
Did you had custom CanInteractMessage prior to the recent addition of the same API by Epic? If you did, then congratulations, Epic burned a type member name that collides with your code. This results in a situation where the code of your previous game build is compiled against the new tools and bumps into this compiler failure. It’s not about your new game build, it’s Epic’s current way of determining verse persistence backwards compatibility that itself breaks when Epic does not provide backwards compatibility against our published games.
What you can do now?
Ping Epic possibly even Sabrina or Magnus to forward this issue to the right team. You will not be able to publish your game(s) until they deploy a proper patch on their end.
This is a similar situation where their tools nuked my game for an entire week after releasing v40.
Long story short, “verse validation” during publishing will fail if your old game build cannot compile against Epic’s new tools without emitting any errors.
This is a very frustrating developer experience!
Start
|
v
New game?
|-- Yes --> Compile with new tools
| |
| +-- Issue? ---- Yes --> Cannot publish
| |
| '-- No --------> Publish / No issue
|
'-- No --> Published game update
|
v
Compile update with new tools
|
+-- Issue? ---- Yes --> Cannot publish update
|
'-- No
|
v
Additionally compile old build with new tools
(verse persistence backwards compatibility check)
|
+-- Issue? ---- Yes --> Cannot publish update
|
'-- No --------> Publish update / No issue