Known issues

Conflict of multiple precompiled assemblies with Newtonsoft.json.dll

Issue description

The issue appears when importing the asset on Unity version 2020.3.10f1 and later. The following error message is displayed:

Copy
Full screen
Small screen
    Multiple precompiled assemblies with the same name Newtonsoft.json.dll included on the current platform. Only one assembly with the same name is allowed per platform.

    The conflict arises because the Newtonsoft.json.dll library is included in both the Unity Editor and the asset. The library is included in the versions 2020.3.10f1 and later of the editor. And the asset includes the library to support the earlier versions of Unity Editor.

    Issue status: Fixed in 0.6.4.4.

    Workaround

    1. Remove the Newtonsoft.json.dll library from the asset:
      1. Create a new Unity project.
      2. Install asset from Unity Asset Store.
      3. Go to Assets\Xsolla\Core\Browser\XsollaBrowser\Plugins directory.
      4. Remove Newtonsoft.Json.dll and Newtonsoft.Json.dll.mdb files.
    2. Restart Unity Editor.

    Was this article helpful?
    Thank you!
    Is there anything we can improve? Message
    We’re sorry to hear that
    Please explain why this article wasn’t helpful to you. Message
    Thank you for your feedback!
    We’ll review your message and use it to help us improve your experience.
    Hide

    Newtonsoft.json.dll library could not be found

    Issue description

    The issue appears if you upgraded a pre-existing project to Unity version 2020.3.10f1 or later. Importing an asset from the Unity Asset Store into such a project is accompanied by many error messages like this:

    Copy
    Full screen
    Small screen
      The type or namespace name ‘Newtonsoft’ could not be found (are you missing a using directive or an assembly reference?)

      The problem occurs because the Newtonsoft.json.dll library is not included in the asset for Unity version 2020.3.10f1 and later. The library is supplied for Unity version 2020.3.10f1 and later, as it is part of the editor. But when updating the project for these versions, the library requires manual installation.

      Issue status: Fixed in 0.6.4.4.

      Workaround

      Install the Newtonsoft.json.dll library manually using the Unity Package Manager.

      Was this article helpful?
      Thank you!
      Is there anything we can improve? Message
      We’re sorry to hear that
      Please explain why this article wasn’t helpful to you. Message
      Thank you for your feedback!
      We’ll review your message and use it to help us improve your experience.
      Hide

      Unable to resolve reference UnityEditor.iOS.Extensions.Xcode

      Issue description

      The issue appears when using External Dependency Manager on Unity version 2020.1.0f1 and later.

      When building the application, an error message is displayed:

      Copy
      Full screen
      Small screen
        Assembly 'Packages/com.google.external-dependency-manager/ExternalDependencyManager/Editor/Google.IOSResolver_v1.2.161.dll' will not be loaded due to errors:
        Unable to resolve reference 'UnityEditor.iOS.Extensions.Xcode'. Is the assembly missing or incompatible with the current platform?
        Reference validation can be disabled in the Plugin Inspector.

        Issue status: Fixed in 0.6.4.5.

        Workaround

        Install iOS Build Support module from Unity Hub.

        Was this article helpful?
        Thank you!
        Is there anything we can improve? Message
        We’re sorry to hear that
        Please explain why this article wasn’t helpful to you. Message
        Thank you for your feedback!
        We’ll review your message and use it to help us improve your experience.
        Hide

        Error occurred running Unity content on page of WebGL build

        Issue description

        The issue appears in some cases when logging in to a WebGL build. The following error message is displayed:

        The problem occurs because the IL2CPP compiler is used when building in WebGL. It optimizes the project and removes unused code from libraries. The compiler cannot correctly determine whether a module, class, or method is being used in a project if reflection is used to retrieve objects. The problem is described in more detail in the Unity documentation.

        Issue status: Can’t be fixed on the SDK side.

        Workaround

        1. Open Unity project.
        2. In the main menu, go to Edit > Project Settings.
        3. In the Player section, go to the WebGL build settings tab.
        4. Go to the Other Settings section.
        5. Uncheck Strip engine code box.
        6. Go to the Publishing Settings section.
        7. Check the Decompression Fallback box.
        8. Create a new WebGL build.

        Was this article helpful?
        Thank you!
        Is there anything we can improve? Message
        We’re sorry to hear that
        Please explain why this article wasn’t helpful to you. Message
        Thank you for your feedback!
        We’ll review your message and use it to help us improve your experience.
        Hide
        Last updated: July 30, 2021

        Found a typo or other text error? Select the text and press Ctrl+Enter.

        Report a problem
        We always review our content. Your feedback helps us improve it.
        Provide an email so we can follow up
        Thank you for your feedback!