Troubleshooting guide

Compile errors when importing the Beam SDK

You may see errors like:

"System.Exception: Package directory not found: \.nuget\packages\System.Private.DataContractSerialization\4.10".

To fix it, you can close and open Unity.

InteractivityState never changes to InteractivityEnabled

If you want to connect to the Beam service, you need to enter your OAuth Client ID and Version ID in the Beam Editor. You can get to the Beam editor by going to the Beam menu and selecting Beam Editor.

Also make sure the code that is calling Beam.GoInteractive is getting called.

Beam code dialog won’t disappear or your game is not receiving input messages

Unity pauses automatically when focus is not on the editor. To fix this, you can go to the Beam Editor and click the "Run in background" button. You can get to the Beam Editor by going to the Beam menu and selecting Beam Editor.

Channel page looks connected, but the SDK is not connected

If you are still connected to your channel page in between pressing play and pause in the Unity editor, sometimes the UI does not update and it will look like you are connected when you are not or vice versa. If this happens, refresh the browser.

Connected elsewhere

If you get a message about being connected from another client, close Unity and your browser and try again.

Control is missing

Your control may be missing because you need to add the control to each of the Small Grid (phones), Medium Grid (Tablets) and Large Grid (Desktops) layouts in Interactive Studio. For instance, if you only added your control to the Large Grid (Desktops) and you open your browser not full screen, depending on the size of your monitor you may get one of the other views that does not have your control in it.

Cannot connect

If it is not one of the above issues, the next most common cause is a mismatch between your OAuth Client ID, Project Version ID and the user you are logged in as. Make sure the OAuth Client ID is not associated with the Project Version ID. You can find this information in the Interactive Studio (https://beam.pro/i/studio). Additionally, you must be logged in as the Beam user who created the Interactive project when you go to http://beam.pro/go.

Duplicate reference build errors

If you see a build errors like:

error CS1703: An assembly `Newtonsoft.Json' with the same identity has already been imported. Consider removing one of the references

This means there are two copies of the DLL. The Beam SDK uses Newtonsoft.Json and WebSocketSharp.dll. If there are duplicate DLL reference errors, you can select one of the DLLs and in the inspector exclude all platforms so that only one version of the DLL is included.

Advanced troubleshooting

For advanced troubleshooting, you can turn on verbose logging. This can be done in the Beam Editor, in the Advanced section. You can view the Beam editor by going to the Unity menu Beam > Open Beam Editor.

Other issues

If you find issues, you can report them on the Git repo: https://github.com/WatchBeam/interactive-unity-plugin/issuesYou can submit feedback at: https://feedback.beam.pro