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.
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
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
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
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.