It seems that when I start a match and engine notifies GameSession about it, host stops updating its connection to EOS services and after some time the session disappears from the search. Also interesting that even when I had “a cached” (just not updated) session result and wanted to join it, it didn’t allow me, as session was started several minutes ago and host declined my connection.
I wouldn’t like to change quite a lot of code about starting and ending match, is there an option to disable this behaviour?
I do set SessionSettings.bAllowJoinInProgress = true;
I tried to fix this with overriding HandleMatchHasStarted() within custom GameMode, to remove a line that notifies online session about match start (I have my own logic for modifying session attribute to display that match was started eg “5 min ago”)
But I didn’t get feedback yet on whether it solved the issue.
Not sure yet if it’s actually the solution, but it may lie in need to manually register players for sessions (unlike lobbies, where they are registered automatically). See OnlineSessionInterface->RegisterPlayer()
Without it, eos backend maybe removes session as inactive after some time