Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Dismiss Notice

Bug Can't build addressables as soon as I upgraded project to unity 2020.3 and up IAP

Discussion in 'Addressables' started by severin1212, Jun 7, 2021.

  1. severin1212

    severin1212

    Joined:
    May 18, 2020
    Posts:
    29
    Hello
    I tried to build addressables but failed in unity and and UCB , I get this error in unity:

    Library\PackageCache\com.unity.purchasing@3.1.0\Runtime\Stores\AppleAppStore\AppleStoreImpl.cs(310,34): error CS0433: The type 'AppleReceiptParser' exists in both 'UnityEngine.Purchasing.Security, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' and 'UnityEngine.Purchasing.SecurityStub, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null'
    Library\PackageCache\com.unity.purchasing@3.1.0\Runtime\Stores\SubscriptionManager.cs(225,31): error CS0433: The type 'AppleReceiptParser' exists in both 'UnityEngine.Purchasing.Security, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' and 'UnityEngine.Purchasing.SecurityStub, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null'
    I found other people complaining for the same reason when building for IOS but none of their solutions worked for me and I am building for Android.
    I deleted library , deleted IAP folder , reimported everything , nothing worked , please help , I am out of ideas here and this is blocking the whole project from release.
     
  2. alexds9

    alexds9

    Joined:
    Feb 9, 2019
    Posts:
    16
    Did you find a solution to this problem?
    I have the same problem and have no idea what to do.
     
  3. TreyK-47

    TreyK-47

    Unity Technologies

    Joined:
    Oct 22, 2019
    Posts:
    1,796
  4. alexds9

    alexds9

    Joined:
    Feb 9, 2019
    Posts:
    16
    @TreyK-47, In the post @JeffDUnity3D reference this issue as known that hasn't been resolved yet in IAP 3.2.3, I don't know what bug number the development team is using for it.