Amplitude native dependencies about unity-plugin HOT 6 CLOSED

@MartinGonzalez jetbrains is used by okhttp library, that's why they're there.

from unity-plugin.

Just to know

Why you are delivering jar files if we can now have the EDM4U dependency to resolve them?

from unity-plugin.

I'm sorry.
Does Amplitude have any dependencies with com.android.installreferrer:installreferrer:1.0 ?

from unity-plugin.

I'm sorry.
Does Amplitude have any dependencies with com.android.installreferrer:installreferrer:1.0 ?

from unity-plugin.

@Deroido I think not, you can validate in Plugins/Android folder and also in AmplitudeDependencies.xml

FYI if you run EDM4U will delete local .aar/.jar files so there will not be duplicated dependencies. I guess it's for backward compatibility.

 <androidPackage spec="com.amplitude:android-sdk:2.28.2">
      <repositories>
        <repository>https://maven.google.com</repository>
      </repositories>
    </androidPackage>

    <androidPackage spec="com.squareup.okhttp3:okhttp:4.2.2">
      <repositories>
        <repository>https://maven.google.com</repository>
      </repositories>
    </androidPackage>
  </androidPackages>

from unity-plugin.

Hello @MartinGonzalez ,

I can confirm your test is correct, the EDM4U plugin does replace old imported files with new ones.

Our engineering team has noticed it is inconvenient for SDK users to import the files themselves. It's one less engineering task and even internally we have run into import issues relating to Java version 7 vs 8 vs 11 and the OpenJDK path used on MacOS and Windows.

Dante

from unity-plugin.