Search Issue Tracker

Fixed in 3.0.0-pre.5

Fixed in 3.0.1

Votes

14

Found in [Package]

2.1.0

Issue ID

1274768

Regression

Yes

"Could not load file or assembly 'UnityEngine.Purchasing'" error after reimporting project with IAP enabled

Package: Purchasing

-

Steps to reproduce:

1. Create new project
2. In services window, enable IAP
3. Import store package and go through installation steps (when done, there should be UnityPurchasing folder inside Assets/Plugins)
4. Right-click in project window and select Reimport All
5. When reimporting is done, notice error in console:
Error: Could not load signature of UnityEditor.Purchasing.GooglePlayProductCatalogExporter:ProductTypeString due to: Could not load file or assembly 'UnityEngine.Purchasing, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. assembly:UnityEngine.Purchasing, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null type:<unknown type> member:(null) signature:<none>

** The error does not impede the usage of the product since as soon as it is cleared, the IAP SDK can be used and this is non-fatal. **
The error won't reappear unless you redo these steps.

Reproduced with: 2020.1.5f1 (IAP 2.1.0), 2020.2.0b1 (IAP 2.1.0)
Not reproducible: 2019.4.10f1 (IAP 2.1.0), 2020.1.5f1 (IAP 2.0.6), 2020.2.0b1 (IAP 2.0.6) (1193773 was happening instead)

Comments (6)

  1. Takafumi-Yamashita

    Jan 05, 2021 06:11

    >I think this issue may cause that preventing app from building at first time on ci in my project.
    I misunderstood that.
    I found out it is fixed by https://issuetracker.unity3d.com/issues/unity-purchasing-define-becomes-disabled-when-recompiling-assemblies

  2. kolmich

    Dec 17, 2020 18:18

    Happens also in unity cloud build. 2020.1.6f1.

  3. auspicious-iman

    Nov 29, 2020 21:58

    Happening on 2020.1.15f1

  4. Takafumi-Yamashita

    Nov 20, 2020 05:46

    I think this issue may cause that preventing app from building at first time on ci in my project.

  5. Dazo1985

    Oct 20, 2020 12:17

    Got this error in 2020.1.9f1

  6. Ennothan

    Sep 08, 2020 13:37

    I got this error on 2019.4.9f1

Add comment

Log in to post comment