[Bug] Infinite Import Loop with Unity 6.X Build Profiles

[Pulse-Git]

Please fill in the following fields:

• Unity editor version: 6000.0.40f1
• External Dependency Manager version: using playgameservices/play-games-plugin-for-unity v2.0.0 and manually updated EDM to 1.2.186 (Manually updated because of https://github.com/googlesamples/unity-jar-resolver/issues/622 )
• Source you installed EDM4U: .unitypackage
• Features in External Dependency Manager in use: Android Resolver
• Plugins SDK in use: -
• Platform you are using the Unity editor on: Windows

Please describe the issue here:

(Please list the full steps to reproduce the issue. Include device logs, Unity logs, and stack traces if available.)

Please answer the following, if applicable:

What's the issue repro rate? 100%

What happened? How can we make the problem occur?

Simply switch to an Build Profile (Unity 6.X Feature)

File -> Build Profiles -> Add Build Profile -> Switch to that Profile, now were stuck in an infinite import loop

Auto-Resolve is disabled

[google-oss-bot]

This issue does not seem to follow the issue template. Make sure you provide all the required information.

[Pulse-Git]

I figured out that normal build profiles are working, but as soon as you "Customize Player Settings" we get an infinite reload loop. Not sure which setting is causing this

[argzdev]

Hey @Pulse-Git, thanks for flagging this. I tried to reproduce this behavior with the following steps:

1. Create a new unity project
2. Import GooglePlayGamesPlugin-2.0.0.unitypackage, but uncheck EDM4U (1.2.182)
3. Import external-dependency-manager-1.2.186.unitypackage
4. File -> Build Profiles -> Add Build Profile -> Switch to Profile (iOS)
5. Click Customize player settings

So far, I haven't had any issues. Am I missing anything? Can you share a MCVE so we can investigate this further?

[google-oss-bot]

Hey @Pulse-Git. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

[google-oss-bot]

Since there haven't been any recent updates here, I am going to close this issue.

@Pulse-Git if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.