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

Importing (Iteration x) infinite loop

Discussion in 'Unity IAP' started by bwrutt, Dec 5, 2019.

Thread Status:
Not open for further replies.
  1. bwrutt

    bwrutt

    Joined:
    Jun 3, 2019
    Posts:
    4
    I'm currently trying to get IAP up and running on my game, but when I try to import the IAP package the installer seems to get stuck in an infinite loop of iteration. The first step of the installer is fine and second step seems to be, but then as shown below the installer gets stuck at the stage Plugins\UnityPurchasing\Bin\Facebook\live\FacebookStore.dll

    Has anyone ever encoutered this issue and know of a way to fix it?

    I can end the loop by ending task and then have to delete the UnityPurchasing folder to get back into my project since the iteration loop starts again on load.

    I have tried importing the package both from services and the unity asset store.

    Thanks in advance
     

    Attached Files:

  2. JeffDUnity3D

    JeffDUnity3D

    Unity Technologies

    Joined:
    May 2, 2017
    Posts:
    14,446
    What version of Unity? Does this happen on a new/empty project as well?
     
  3. bwrutt

    bwrutt

    Joined:
    Jun 3, 2019
    Posts:
    4
    Just to add on in case it makes a difference, i have tried on a blank project and i get exactly the same issue
     
  4. bwrutt

    bwrutt

    Joined:
    Jun 3, 2019
    Posts:
    4
    Sorry Jeff, think our posts overlapped. I am 2019.3.0a2 and empty/new projects don't make a difference unfortunately
     
  5. JeffDUnity3D

    JeffDUnity3D

    Unity Technologies

    Joined:
    May 2, 2017
    Posts:
    14,446
    You are testing with an Alpha release (.0a2), I too have issues with that version. It works for me, with Unity 2019.3.0f1
     
    bwrutt likes this.
  6. bwrutt

    bwrutt

    Joined:
    Jun 3, 2019
    Posts:
    4
    ah, probably should've tried that before posting, but anyway thank you very much for the quick reply - appreciated!
     
  7. GaetanRhinox

    GaetanRhinox

    Joined:
    Feb 18, 2019
    Posts:
    2
    At our company, we have recently upgraded to the release version of 2019.3 and several colleagues of mine are still having this issue. Yet, I can find no reference to it, except this forum post. Anyone else having issues with this?

    Our current "solution" is to completely delete the Library cache and all generated files, however the problem comes back after switching to a new scene in the project.
     
  8. JeffDUnity3D

    JeffDUnity3D

    Unity Technologies

    Joined:
    May 2, 2017
    Posts:
    14,446
    So for some of your developers, it's working as expected? What specific version of 2019.3? Do you have Editor code running when you switch between scenes during design time in the Editor? So if you just switch scenes, it no longer compiles? Are you able to reproduce with a new project?
     
  9. GaetanRhinox

    GaetanRhinox

    Joined:
    Feb 18, 2019
    Posts:
    2
    Myself and others had the issue but somehow by repeatedly deleting the Library cache it seems to have stabilized (for now). Yet another, the issue suddenly appeared and did not go away.

    Eventually, we managed to 'fix' the issue by reverting the AssetPipeline to V1 (Deprecated).
    The version we are running is Unity 2019.3.0f6
    Our projects are pretty complex, so we do not have a clear idea on how to start reproducing it (i.e. finding the minimal case). Thus we have not attempted recreating it with a new project.
     
  10. JeffDUnity3D

    JeffDUnity3D

    Unity Technologies

    Joined:
    May 2, 2017
    Posts:
    14,446
    Understood, I assume you've confirmed that you (or another asset) is not calling PlayerPrefs.DeleteAll which has been discussed separately.
     
  11. JACLEMGO

    JACLEMGO

    Joined:
    May 30, 2013
    Posts:
    30
    Im experiencing an endless import cycle on multiple projects using Unity 2019.3.1f1, but its seems it's more caused by Shader Graph 7.2.1. When I revert back to Shader Graph 7.1.8, all is fine again.
     
Thread Status:
Not open for further replies.