Search Unity

Unity IAP 1.20.1 causing UWP build errors

Discussion in 'Unity IAP' started by Wadjey, Oct 23, 2018.

  1. Wadjey

    Wadjey

    Joined:
    Feb 4, 2015
    Posts:
    244
    Hi,
    After updating Unity IAP to v1.20.1 I'm unable to build for UWP, I'm getting build errors in VS15.8.7!
    This issue doesn't exist in the v1.20.0

    Bug case: #1093054
     
  2. JeffDUnity3D

    JeffDUnity3D

    Joined:
    May 2, 2017
    Posts:
    14,446
    What is the build error that you are receiving? Please post here also.
     
  3. Wadjey

    Wadjey

    Joined:
    Feb 4, 2015
    Posts:
    244
    Here is the error:
    Code (CSharp):
    1. Severity    Code    Description    Project    File    Line    Suppression State
    2. Error        The command ""D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Unity\Tools\AssemblyConverter.exe" -platform=uap -lock="D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\project.lock.json" -bits=64 -configuration=Debug -removeDebuggableAttribute=False -uwpsdk=10.0.17763.0 -path="." -path="C:\Program Files\Unity20174\Editor\Data\PlaybackEngines\MetroSupport\Players\UAP\dotnet\x64\Debug" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.TerrainPhysicsModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.TextRenderingModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.StyleSheetsModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.TerrainModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.UIElementsModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.TilemapModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.ScreenCaptureModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.SharedInternalsModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.PhysicsModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.SpriteShapeModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.SpriteMaskModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.VRModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.WebModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.VehiclesModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.VideoModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.WindModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.UnityAnalyticsModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.UnityConnectModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.UIModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.UNETModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.UnityWebRequestTextureModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.UnityWebRequestWWWModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.UnityWebRequestAudioModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.UnityWebRequestModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.Physics2DModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.AIModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.AccessibilityModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.AssetBundleModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.AudioModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.AnimationModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.ARModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\Assembly-CSharp-firstpass.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.InputModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.JSONSerializeModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.ImageConversionModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.IMGUIModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.ParticleSystemModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.PerformanceReportingModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.ParticlesLegacyModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.CrashReportingModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.DirectorModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.ClothModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.CoreModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.GridModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.GameCenterModule.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\Stores.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.Timeline.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\winrt.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\ChannelPurchase.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\nunit.framework.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.UI.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\Purchasing.Common.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.SpatialTracking.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.Analytics.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\Security.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.HoloLens.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\FacebookStore.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.StandardEvents.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\Apple.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.Purchasing.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityEngine.Networking.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\UnityStore.dll" "D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\Tizen.dll"" exited with code 1.    Delete_UnityIAP1_20_1    D:\MyUnityProjects\Delete_UnityIAP1_20_1\Builds\UWP\Delete_UnityIAP1_20_1\Delete_UnityIAP1_20_1.csproj    449  
    3.  
     
  4. Wadjey

    Wadjey

    Joined:
    Feb 4, 2015
    Posts:
    244
  5. JeffDUnity3D

    JeffDUnity3D

    Joined:
    May 2, 2017
    Posts:
    14,446
    @Wajdik I was able to upgrade and build my IAP project using IAP 1.20.1, Unity 2018.13f1 and Visual Studio 15.8.6 without issue. I haven't tested with other versions. Does it recreate for you with a new/empty project with only IAP 1.20.1 imported?
     
  6. Wadjey

    Wadjey

    Joined:
    Feb 4, 2015
    Posts:
    244
    Hi,
    Yes this issue is happening for me with a newly created project, I just created an new Unity project (Unity 2017.4.13f1) and built for UWP (Unity C# Projects), then opened the project with VS15.8.7 and finally when I click on build I get this error!
     
  7. JeffDUnity3D

    JeffDUnity3D

    Joined:
    May 2, 2017
    Posts:
    14,446
    If you are in a position to update to the Unity version I mentioned, that might be one option. In the meantime, I will test with the version you have mentioned. Can you try with VS15.8.8? I see that it is the latest version when I check Updates in VS. This way we can test on the same version.
     
  8. Wadjey

    Wadjey

    Joined:
    Feb 4, 2015
    Posts:
    244
    Just tested with VS15.8.8 and got the same error.
    Unfortunately I can't upgrade to Unity 2018, and as I mentioned above, this issue doesn't exist in Unity IAP 1.20.0
     
  9. JeffDUnity3D

    JeffDUnity3D

    Joined:
    May 2, 2017
    Posts:
    14,446
    Understood, I will test on 2017.4.13f1 and should have my results within 24 hours, stay tuned.
     
  10. JeffDUnity3D

    JeffDUnity3D

    Joined:
    May 2, 2017
    Posts:
    14,446
    I just tried on 2017.4.13f1 without issue. So it looks like it specific to your system. Can you try on another computer with an empty project? Also, you mentioned D: drive, can you try on C:\Users\[username]\Documents (to make sure it's not a permission issue)
     
    DarekRusin likes this.
  11. Wadjey

    Wadjey

    Joined:
    Feb 4, 2015
    Posts:
    244
    That's really strange!
    I just created a new projects in the C: drive, with Unity 1.20.0 I can build without any problem, but with Unity 1.20.1 I'm getting that error!
    I also tried on another PC and I got the same issue.
    Could you please try with the project attached to the bug case #1093054 ?
     
  12. JeffDUnity3D

    JeffDUnity3D

    Joined:
    May 2, 2017
    Posts:
    14,446
    Your attached project worked for me. I deleted the Library folder, used a new MyBuild folder, deleted the .sln files and all .lock files first. I noticed you didn't have a scene created, so I just used the default empty scene. Please test on a new/empty project. I used IL2CPP scripting. Update - I too get the error when using .NET scripting. Is 1.20.0 or IL2CPP an option for you? When removing IAP, I don't get an error, so something is not right. I'll let the IAP team know.
     
    Last edited: Oct 30, 2018
  13. Wadjey

    Wadjey

    Joined:
    Feb 4, 2015
    Posts:
    244
    Hi,
    That's right, I'm using .NET scripting and can't upgrade to IL2CPP!
    I'll stay with Unity IAP v1.20.0 until a fix will be provided.
     
  14. Wadjey

    Wadjey

    Joined:
    Feb 4, 2015
    Posts:
    244
    Hi @JeffDUnity3D,
    Any update regarding this issue and when we'll get a fix?
    Here is the bug case: #1093054
     
  15. JeffDUnity3D

    JeffDUnity3D

    Joined:
    May 2, 2017
    Posts:
    14,446
    This likely will not be addressed in a timely manner, we are focusing on iOS and Android first.
     
  16. Wadjey

    Wadjey

    Joined:
    Feb 4, 2015
    Posts:
    244
    @JeffDUnity3D Sad to hear that, I thought it will be fixed quickly as it's a blocking bug that prevents us to build our games for UWP :/
     
    Last edited: Dec 22, 2018
  17. CanisLupus

    CanisLupus

    Joined:
    Jul 29, 2013
    Posts:
    427
    Sorry to ask again, but is this not being worked on yet, @JeffDUnity3D?

    (To anyone reading, please vote on this issue.)

    In our case this look totally unrelated to UWP, since it's Apple stuff when building for UWP:
    Maybe a misconfigured dll on your end...?

    We can't move to IL2CPP (some encryption methods we use are not available, and asset bundles are incompatible) and this bug forces us to use a previous version of the Unity Purchasing system.

    Problem is... versions 1.19 and before have the bug that consumes non-consumable purchases on initialize, version 1.20 fixes that but adds an unnecessary permission on Android, and 1.20.1 makes it impossible to build for UWP. So none are actually usable... Also, at some point the plugin started constantly spamming the console:
    Please please please fix this soon. :(
    Daniel
     
  18. JeffDUnity3D

    JeffDUnity3D

    Joined:
    May 2, 2017
    Posts:
    14,446
    @CanisLupus Are you reporting a new issue? Is this stack trace for the same issue that you asked users to vote on? The console error looks to be caused by our code likely incorrectly parsing your locale and date setting (as shown in the error), I suspect you are outside of the US. This issue will likely be addressed in an upcoming version since it potentially affects all IAP users. We are not currently actively working any UWP issues, and focusing on Android and iOS.
     
  19. CanisLupus

    CanisLupus

    Joined:
    Jul 29, 2013
    Posts:
    427
    Hey Jeff, unfortunately I don't know if the problem is the exact same since the issue (the one mentioned by @Wajdik, number #1093054) has no stack trace, but it also happens in the AssemblyConverter phase and does not happen with Unity Purchasing 1.18 (the only other one we tested). The issue is

    The problem seems at least related. This one mentions UnityEngine.Purchasing.AppleStoreImpl, which we find weird for UWP.

    The important part is that these AssemblyConverter errors will soon be blocking our release as well as Wajdik's, unless we move to another version of Unity Purchasing, which in turn has other problematic issues (I reported the issue on non consumables being consumed, actually). I worry that 2019.1 will come and remove support for .NET without first fixing this issue on 2018.x.

    I realize UWP is not "as important" as some other platforms, but this was working before. ;)

    Best regards,
    Daniel
     
  20. JeffDUnity3D

    JeffDUnity3D

    Joined:
    May 2, 2017
    Posts:
    14,446
    @CanisLupus You mentioned "working before", can you elaborate what changed? Can you provide steps to reproduce on a new/empty project? Please list all versions you are using (Unity, IAP)
     
    Last edited: Jan 4, 2019
  21. CanisLupus

    CanisLupus

    Joined:
    Jul 29, 2013
    Posts:
    427
    @JeffDUnity3D "Working before" means that the UWP project compiles in Visual Studio when using Unity Purchasing 1.18 but gives the stack trace above when using 1.20.1. We haven't tested the intermediate versions since they have other issues.

    We are using Unity 2018.2.17f1. No Xcode since this is on Windows (that should be clear :)), but it's Visual Studio 15.9.4. The fact that errors are related to Apple platforms is weird.

    The steps to reproduce are:
    - Create an empty Unity project
    - Import and activate Unity IAP version 1.20.1
    - Build for UWP using the .NET scripting backend
    - Get reference rewriter errors in Unity, but build completes
    - In Visual Studio, build (for example for x86)
    - Get more errors (Apple stuff)

    We didn't submit another bug report since we thought this was at least similar to issue #1093054.

    On our actual (not test) project, we don't get the reference rewriter errors in Unity (!!), but still get all the other ones later in Visual Studio.
     
  22. JeffDUnity3D

    JeffDUnity3D

    Joined:
    May 2, 2017
    Posts:
    14,446
    What is different between your actual project (no errors) versus the test project (with errors).
     
  23. CanisLupus

    CanisLupus

    Joined:
    Jul 29, 2013
    Posts:
    427
    We don't know. Same Unity version and Unity Purchasing modules...

    But there are errors even in our main project; only in Visual Studio, though. They are the same errors (the ones in my stack trace above) that we get in the empty project. We just don't get errors in Unity itself when creating the build.
     
  24. JeffDUnity3D

    JeffDUnity3D

    Joined:
    May 2, 2017
    Posts:
    14,446
    Just found out that this issue should be addressed in the next release. No ETA, but my guess might be in about a month.
     
  25. CanisLupus

    CanisLupus

    Joined:
    Jul 29, 2013
    Posts:
    427
    Hey Jeff, thats great to hear. Do you mean one of the next minor versions? Or the bigger 2018.4? Just so we know what to expect in our update path. Thanks.
     
  26. JeffDUnity3D

    JeffDUnity3D

    Joined:
    May 2, 2017
    Posts:
    14,446
    CanisLupus likes this.
  27. Wadjey

    Wadjey

    Joined:
    Feb 4, 2015
    Posts:
    244
  28. JeffDUnity3D

    JeffDUnity3D

    Joined:
    May 2, 2017
    Posts:
    14,446
    Are you still getting the error with IAP 1.22?
     
  29. Wadjey

    Wadjey

    Joined:
    Feb 4, 2015
    Posts:
    244
    Yes, just tried it and I'm still getting the error
     
  30. HTON8

    HTON8

    Joined:
    Jan 7, 2015
    Posts:
    5
    Hi, do you solve this problem?
    I get the same error when build UWP( .NET scripting):
    Code (CSharp):
    1.   Copying unprocessed assemblies...
    2.   Running AssemblyConverter...
    3.   Failed to fix references for method System.Void UnityEngine.Purchasing.AppleStoreImpl::OnProductsRetrieved(System.String)
    4.   Failed to fix references for type UnityEngine.Purchasing.AppleStoreImpl
    5.   System.Exception: Failed to resolve System.Console
    6.      in Unity.ModuleContext.Retarget(TypeReference type, GenericContext context)
    7.      in Unity.ModuleContext.Retarget(MethodReference method, GenericContext context)
    8.      in Unity.FixReferencesStep.Visit(MethodDefinition method, GenericContext context)
    9.      in Unity.FixReferencesStep.Visit(TypeDefinition type)
    10.      in Unity.TypeDefinitionDispatcher.DispatchType(TypeDefinition type)
    11.      in Unity.TypeDefinitionDispatcher..ctor(ModuleDefinition module, ITypeDefinitionVisitor visitor)
    12.      in Unity.FixReferencesStep.ProcessModule()
    13.      in Unity.ModuleStep.Execute()
    14.      in Unity.FixReferencesStep.Execute()
    15.      in Unity.Step.Execute(OperationContext operationContext, IStepContext previousStepContext)
    16.      in Unity.Operation.Execute()
    17.      in Unity.Program.Main(String[] args)
    Unity version: 2018.2.21f1
    IAP version: 1.22.0
    VS version: 16.2.5
     
  31. JeffDUnity3D

    JeffDUnity3D

    Joined:
    May 2, 2017
    Posts:
    14,446
    Apologies on the delay, this update is indeed planned for the next release, currently scheduled towards the end of September pending QA testing.
     
    Wadjey likes this.
  32. Wadjey

    Wadjey

    Joined:
    Feb 4, 2015
    Posts:
    244
    @JeffDUnity3D There is any update regarding the new release?
     
  33. JeffDUnity3D

    JeffDUnity3D

    Joined:
    May 2, 2017
    Posts:
    14,446
    Hopefully this week!
     
    Wadjey likes this.
  34. CanisLupus

    CanisLupus

    Joined:
    Jul 29, 2013
    Posts:
    427
    I don't know about this particular error anymore since I haven't done UWP builds for a while, but this one (case 1136555) was also reported in March 2019 and still no news.
     
    Wadjey likes this.
  35. Wadjey

    Wadjey

    Joined:
    Feb 4, 2015
    Posts:
    244
    Hi @JeffDUnity3D,
    I've reported this issue 1 year 7 months ago and it still not fixed in the latest Unity IAP version (v1.23.1), is it that complicated to fix? Please can you provide us an accurate release date for the fix?
     
  36. JeffDUnity3D

    JeffDUnity3D

    Joined:
    May 2, 2017
    Posts:
    14,446
    We need to update the package to use the Windows 10 billing library from Microsoft. Probably not too complicated once we are able to get to it, higher priorities and resource constraints have been the issue, unfortunately even more so now. Sorry no ETA, but likely at least a few months out.