# EOS Plugin for Unity builds crash on open if multiple deployment id's are added to the Deployment Configuration 

**URL:** <https://forums.unrealengine.com/t/eos-plugin-for-unity-builds-crash-on-open-if-multiple-deployment-ids-are-added-to-the-deployment-configuration/2858455>\
**Category:** Developer Portal\
**Tags:** epic-online-services, question\
**Created:** [February 20, 2026, 12:42am UTC](https://forums.unrealengine.com/t/eos-plugin-for-unity-builds-crash-on-open-if-multiple-deployment-ids-are-added-to-the-deployment-configuration/2858455 "2026-02-20T00:42:52Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [February 20, 2026, 12:42am UTC](https://forums.unrealengine.com/t/eos-plugin-for-unity-builds-crash-on-open-if-multiple-deployment-ids-are-added-to-the-deployment-configuration/2858455/1 "2026-02-20T00:42:52Z")

</div>

EOS SDK version: 1.19.0.3

EOS Plugin for Unity version: 6.0.0

I added a second deployment id to the EOS configuration so that I can select the one I want to use with the Deployment dropdown before I build, which seems to be the intended use.

This causes the build to crash immediately upon opening due to the exception:

`The thread tried to read from or write to a virtual address for which it does not have the appropriate access.`

---

<div class="post-metadata">

**Author:** ![EOSPlugin\_Jeff](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@EOSPlugin\_Jeff](https://forums.unrealengine.com/u/EOSPlugin_Jeff)\
**Post date:** [February 25, 2026, 10:47pm UTC](https://forums.unrealengine.com/t/eos-plugin-for-unity-builds-crash-on-open-if-multiple-deployment-ids-are-added-to-the-deployment-configuration/2858455/2 "2026-02-25T22:47:24Z")

</div>

Hi Manny,

I was unable to reproduce this issue using the 6.0.0 package and Unity 2021.3.16. I configured the sample app included in the plugin with the following:

- sandbox 1
  - deployment 1
  - deployment 2

- sandbox 2
  - deployment 3

I tested using all three deployments and was able to launch the client and log in without a crash. Would you be able to provide the following information so we can investigate further?

- Unity version being used.
- Client log of the crash reproduction.
- Are you able to reproduce using the sample application?
- Does the deployment you’re attempting to use work if you only have a single deployment configured instead of multiple?

-Jeff

---

<div class="post-metadata">

**Author:** ![EOSPlugin\_Jeff](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@EOSPlugin\_Jeff](https://forums.unrealengine.com/u/EOSPlugin_Jeff)\
**Post date:** [February 27, 2026, 10:08pm UTC](https://forums.unrealengine.com/t/eos-plugin-for-unity-builds-crash-on-open-if-multiple-deployment-ids-are-added-to-the-deployment-configuration/2858455/3 "2026-02-27T22:08:57Z")

</div>

Thanks for the info about the eos\_product\_config.json. We had made fixes to the config window in 6.0.0 and haven’t been able to reproduce a null sandbox for the newly added deployment. I tried adding the deployments first and saving it to confirm the sandbox is null in the json. Once I added the sandbox ID, it populated both deployments in the json.

If you have steps to reproduce a null sandbox ID for the added deployment, we can take another look and work on fixing the bug.

-Jeff

---

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [February 27, 2026, 10:12am UTC](https://forums.unrealengine.com/t/eos-plugin-for-unity-builds-crash-on-open-if-multiple-deployment-ids-are-added-to-the-deployment-configuration/2858455/4 "2026-02-27T10:12:54Z")

</div>

The way I figured out that this was the issue was I noticed in eos\_product\_config.json the SandboxId for the added deployment was null. Removing the additional deployment solved the issue. Definitely seems like a bug with the EOS unity editor window.
