Has the EDM4U dependency been fixed in GPG v2.1?

[mudsplash]

Hello,
GPG v2.0.0 had upgrading requirement that required us to pin the External Dependency Manager for Unity to v1.2.82.
This dependency has been causing a lot of compatibility issues with other plugins/ SDKs during development.

Also, there was an issue that was causing failures in builds because some AARs weren't being included in the project and there were problems with proguard too.

I was relieved to see an update and was thinking of upgrading to GPG v2.1 but there is no point if this isn't fixed yet since I need something that reliably works on prod.

[kuoliangkwong]

I'm having the same problem after upgrading to latest EDM4U 1.2.186

> Could not resolve all files for configuration ':launcher:releaseRuntimeClasspath'.
    > No variants of com.google.games:gpgs-plugin-support:2.1.0 match the consumer attributes:
        - com.google.games:gpgs-plugin-support:2.1.0 configuration runtime declares a library for use during runtime:
            - Incompatible because this component declares a component, as well as attribute 'artifactType' with value 'srcaar' and the consumer needed a component, as well as attribute 'artifactType' with value 'android-classes-jar'

Upon checking, the settingsTemplate.gradle is pointing to the wrong folder

maven {
    url (unityProjectPath + "/Assets/GooglePlayGames/com.google.play.games/Editor/m2repository") // Assets/GooglePlayGames/com.google.play.games/Editor/GooglePlayGamesPluginDependencies.xml:11
}

Using EDM4U v1.2.182 would point to the correct generated local repo instead:

maven {
    url (unityProjectPath + "/Assets/GeneratedLocalRepo/GooglePlayGames/com.google.play.games/Editor/m2repository") // Assets/GooglePlayGames/com.google.play.games/Editor/GooglePlayGamesPluginDependencies.xml:11
}

[Unarmed1000]

googlesamples/unity-jar-resolver#716

You can do a local workaround for the discovered bug by

1. Move directory Assets/GooglePlayGames/com.google.play.games/Editor/m2repository to Assets/GooglePlayGames/m2repository
2. Move the meta file Assets/GooglePlayGames/com.google.play.games/Editor/m2repository.meta to to Assets/GooglePlayGames/m2repository.meta
3. Edit Assets/GooglePlayGames/com.google.play.games/Editor/GooglePlayGamesPluginDependencies.xml from

<repositories>
<repository>Assets/GooglePlayGames/com.google.play.games/Editor/m2repository</repository>
</repositories>

to

<repositories>
<repository>Assets/GooglePlayGames/m2repository</repository>
</repositories>

This seems to ensure that settingsTemplate.gradle gets generated with the correct path for the new location.

url (unityProjectPath + "/Assets/GeneratedLocalRepo/GooglePlayGames/m2repository") // Assets/GooglePlayGames/com.google.play.games/Editor/GooglePlayGamesPluginDependencies.xml:11

That should work until they release the next update.

[rico345100]

No, it's not fixed