EOS 3.3.5 - Crashing when running any configuration options

[AdamPoncle]

Describe the bug
When running any of the configuration options () the Unity Editor crashes

To Reproduce
Steps to reproduce the behavior:

1. Open a project with EOS 3.3.5 installed in Unity 6000.0.36
2. Run either 'EOS Plugin -> EOS Configuration' or 'EOS Plugin -> Plugin Configuration'
3. Notice the Unity Editor crashes

Expected behavior
Should not error and allow me to configure the EOS plugin as 3.3.4 did.

Desktop (please complete the following information):

• OS: Windows x64
• Editor
• Unity 6000.0.36f1
• EOS 3.3.5

[paulhazen]

Hi @AdamPoncle, thanks for reaching out. Currently we do not officially support Unity 6, but I will look into this today.

Can you provide a few extra details?

For instance, did you upgrade from 3.3.4 to 3.3.5, or did you start a new project and add the plugin fresh? Both should work, but knowing which one will help me diagnose.

Also, can you describe how you added or upgraded the plugin (did you install through the package manager, install it by downloading the tar all from the release page, or clone the repository into your project)?

With these details we should be able to narrow down the issue to make a fix.

In the meantime I will experiment and see if I can replicate the issue.

[AdamPoncle]

Hey @paulhazen !

So I upgraded from Unity 2021.3.44f1 to Unity 6000.0.36f1 this year with the EOS Plugin 3.3.4. We were having various build issues with the plugin (which we ended up having to use our CI to remove it on all builds which did not require the EOS SDK).

Once 3.3.5 was released we then updated to that version in the project, but as mentioned it crashes every time we try and load any of the configuration windows.

The SDK is installed as a local tarball package which we manually add into our projects manifest.json. When we updated, we just pointed to the new SDK in the manifest and let Unity re-import it.

If you need anything else please feel free to reach out! Also apologies, I did not realise Unity 6 was not officially supported yet (but we had to upgrade our project for other reasons).

Thanks,
Adam

[WispyMouse]

You should be able to define EOS_DISABLE as a compiler symbol in the player settings to remove the plugin. It may still take some actions, but that should un-include most of the lpugin.

For the configuration window, I have something to try. Go to your StreamingAssets/EOS/ folder. Move all of these configuration values out of this folder, leaving it empty. Then open the configuration windows, and reapply your settings through the UI. If you try to launch the editor windows without these files and it still doesn't work, we'll have to try something else!

[AdamPoncle]

You should be able to define EOS_DISABLE as a compiler symbol in the player settings to remove the plugin. It may still take some actions, but that should un-include most of the lpugin.

For the configuration window, I have something to try. Go to your StreamingAssets/EOS/ folder. Move all of these configuration values out of this folder, leaving it empty. Then open the configuration windows, and reapply your settings through the UI. If you try to launch the editor windows without these files and it still doesn't work, we'll have to try something else!

Hey @WispyMouse!

Regarding EOS_DISABLE, we actively use that as we support multiple platforms in our project (Android, iOS, Xbox, PlayStation, Switch, Steam, Standalone) and we only require the SDK on Epic specific builds for Standalone. However this was still causing issues (in EOS 3.3.4 SDK) so we updated to try and resolve some of these issues, but they still persist. I can / should probably make a new ticket relating to those issues, but we have a CI solution for it at present.

As for the configuration, I have tried that. I have tried including our configuration files in that folder, and removing them. Both instances the window fails to load an just crashes Unity back to desktop.

Thanks,
Adam

[WispyMouse]

Could you possibly send us a log from Unity after it crashes? Unity writes to a log at AppData/Local/Unity/Editor/Editor.log. Perhaps there'll be some clue as to why it is crashing in there.

[WispyMouse]

Additionally if you feel comfortable, can you share a (optionally redacted) copy of your EpicOnlineServicesConfig.json and eos_product_config.json?

[paulhazen]

Following up again - I'm currently installing the exact version of Unity that you were utilizing so I can try reproducing the issue. In the meantime, I wanted to get clarity on a few points:

The SDK is installed as a local tarball package which we manually add into our projects manifest.json. When we updated, we just pointed to the new SDK in the manifest and let Unity re-import it.

This is sort of pedantic - but to make sure I am not misunderstanding - can I assume that when you say "SDK," here you actually mean the Unity plugin (which includes the SDK)?

Can you try moving your EpicOnlineServicesConfig.json file into a different location (effectively deleting it)? This will cause the plugin to generate new configuration files - but it should allow you to open the configuration windows at least - and knowing whether that works will help us narrow down the source of the problem. This should not be necessary, but again it will help narrow things down.

When you're able to follow up with answers to the above, I'll be better prepared to help you solve your problem. It would be really good if we could get this squared away for you before Friday.