Steam Integration on OSX broken after 4.9 Update

Steam was working quite well on UE4 – getting the overlay, achievements working, etc. – until we upgraded to 4.9 a couple months ago, at which point it stopped. Unfortunately we didn’t notice at the time, are now scrambling to figure out what went wrong.

Stepping through the code for the Stand-Alone build, I can confirm that the OnlineSubsystemSteam module is being loaded, and that it is successfully initializing itself. But, no overlay and no achievements.

It would be helpful to know, furthermore, what a proper steam-enabled cooked build is meant to look like. This guide

suggests copying the libsteam_api.dylib into the app package. However, I never did that pre-4.9, and never had an issue with Steam. Furthermore, looking through the app package of a working pre-4.9 build, there is no libsteam_api.dylib included. Did it somehow become necessary? In any case, manually including it in the package (in did not solve the problem.

Also notable is that the Steam version included in UE4 went from 1.30 to 1.32 in 4.9. I can’t find any references to the old version, so I don’t think it’s a version mismatch of any kind. I have also confirmed that all the files in Engine/Source/ThirdParty/Steam are where they are supposed to be.

Meanwhile, the PC build is working completely correctly.

Anybody else have this issue? Are there any other leads I should be hunting down? Is there any other way to diagnose what is going wrong?

We are due an engine update anyway, so I may be upgrading us to 4.10 in the coming days. But I sure would like to know what happened here.

Are you launching your title through Steam? I do not believe Steam on OSX hooks into the overlay correctly if you are not launching it through the Steam launcher.

I have tested the full build->upload to steam->down from steam loop, as well as adding the editor app as a non-steam game to the steam library and running in stand-alone. Neither seems to work.

Hi disla,

Due to the large volume of questions and comments concerning the Engine, we did not have a chance to respond to your post at the time you submitted it and, thus, the issue is now outdated. If you are still experiencing this issue in the current release of the Engine, please make a new post for assistance.

Steve H.