Skip to content

Commit ecd96b6

Browse files
felipe-beamablefelipe-beamable
committed
Change - Update steam instructions
1 parent d24f09f commit ecd96b6

1 file changed

Lines changed: 56 additions & 1 deletion

File tree

‎docs/unreal/samples/beamball/steam-integration.md‎

Lines changed: 56 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -87,4 +87,59 @@ This sample is NOT a template you can start your own repository from. However, i
8787
- Content inside the `BEAMPROJ_SteamDemo` except things inside a `ThirdParty` directory.
8888

8989
## Why don't we provide a client build?
90-
Because clients must be pointed at your `steam-demo` realm. As such, you'd need to generate the build yourself, which you can do by packaging it normally for any of our supported platforms.
90+
Because clients must be pointed at your `steam-demo` realm. As such, you'd need to generate the build yourself, which you can do by packaging it normally for any of our supported platforms.
91+
92+
---
93+
94+
## Required Files for Steam on Desktop Platforms
95+
96+
### SSL Certificate (`cacert.pem`)
97+
98+
Beamable uses secure socket connections, and on some platforms the OS requires a trusted CA certificate bundle to validate them. Without this file, Beamable network calls may fail silently at runtime.
99+
100+
1. Locate the certificate file bundled with the engine:
101+
102+
```
103+
\Epic Games\UE_5.6\Engine\Content\Certificates\ThirdParty\cacert.pem
104+
```
105+
106+
2. Copy it into a folder named `Certificates` inside your project's **Source** folder:
107+
108+
```
109+
<ProjectRoot>/Source/Certificates/cacert.pem
110+
```
111+
112+
3. In your project settings, add this folder to the **Additional Non-Asset Directories to Copy** list (under **Packaging**) so Unreal includes it in the packaged build:
113+
114+
```
115+
Source/Certificates
116+
```
117+
118+
Unreal will then bundle the certificate with the build, allowing Beamable to establish trusted connections at runtime.
119+
120+
---
121+
122+
## macOS Development: Disabling App Sandbox
123+
124+
When developing on macOS, the App Sandbox may block Steam network calls and Beamable connections. If you are working in a **development build**, you should disable the sandbox by editing the entitlements file.
125+
126+
Open the following file in your project:
127+
128+
```
129+
Build/Mac/Resources/Sandbox.Server.entitlements
130+
```
131+
132+
Set the `com.apple.security.app-sandbox` key to `false`:
133+
134+
```xml
135+
<?xml version="1.0" encoding="UTF-8"?>
136+
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
137+
<plist version="1.0">
138+
<dict>
139+
<key>com.apple.security.app-sandbox</key>
140+
<false/>
141+
</dict>
142+
</plist>
143+
```
144+
145+
> **Warning:** Only set `APP_SANDBOX` to `No` in development builds. Re-enable it before submitting to production or the Mac App Store.

0 commit comments

Comments
 (0)