- All - Fixed #440 and fixed #447 by specifying the parameter type while calling
GetApplicationIdentifier()Unity API using reflection, due to a new overloaded method introduced in Unity 2021.2. - Android Resolver - Fixed #442 by patching
Dependency.IsGreater()when the version strings end '+'.
- Version Handler - Fixed #431 by replacing the use of
HttpUtility.UrlEncode()which causes NullReferenceException in certain version of Unity. - Android Resolver - Check that androidSdkRootPath directory exists before using as sdkPath.
- Android Resolver - Fixed Android Resolver integration tests with Unity 2019.3+.
- Android Resolver - Added support for Android packages with classifier in their namespaces.
- iOS Resolver - Added new settings in iOS Resolver to configure generated Podfile.
- iOS Resolver - Added a new attribute
addToAllTargetsin Dependencies.xml.
- iOS Resolver - Fixed XML parsing for
bitcodeEnabledattribute in Dependencies.xml.
- Version Handler - Fixed measurement reporting
- Version Handler - Improved #413 by preventing Version Handler from running from static constructor when it is disabled.
- Package Manager Resolver - Remove GPR
- Android Resolver - Fixed the issue that Android Resolver does not resolve again before build in Unity 2020 if it failed to resolve previously.
- Android Resolver - Fixed a regression that gradleResolver can be null until Initialize() is called.
- Android Resolver - Fixed a regression that Android Resolver failed in Unity
2019.3+ due to
gradleTemplate.propertiesnot enabled whenmainTemplate.gradleis not enabled at all.
- Android Resolver - Fixed #322 where the Unity editor will lose its target SDK
setting between Unity restarts if
>28is selected in 2019. This is due to Unity AndroidSdkVersions enum does not contain values above 28. - Android Resolver - Fixed #360 where building Android app with Untiy 2019.3+
may fail due to Jetifier and AndroidX not enabled properly in generated
Gradle project. This fix requires the user to enable
Custom Gradle Properties Templatefound underPlayer Settings > Settings for Android > Publishing Settings.
- Version Handler: Fixed editor freeze when
-executeMethodis used in non-batch mode. - Android Resolver: Normalized file paths when generating local Maven repo since the path may contains a mix of forward and backward slash on Windows.
- Export Unity Package: Fixed generation of .unitypackage with tarfile on Windows.
- Android Resolver: Delay initialization until active build target is Android and the editor is not in play mode.
- iOS Resolver: Delay initialization until active build target is iOS and the editor is not in play mode.
- Export Unity Package: Workaround directory creation racy if multiple export operations are spawned at the same time.
- Android Resolver: Fixed that the generated local repo assets contains redundent labels which are causing Version Handler to failed while uninstalling packages.
- Android Resolver: Fixed that the repo url injected into mainTemplate.gradle is incorrect when Unity is configured to export gradle project.
- Android Resolver: Limited to only create local Maven repo when the source repo contains ".srcaar" file.
- All: Described EDM4U analytics data usage in readme.
- All: Fixed compiler error when build with Unity 5.4 or below due to the usage of Rect.zero.
- All: Ignore cases when checking command line arguments.
- All: Make each MultiSelectWindow for different purposes to have its own unique window.
- All: Replace all dialog with DialogWindow which is implemented from EditorWindow.
- Package Manager Resolver: Clarify how manifest.json will be changed in Package Manager Resolver window.
- Android Resolver: Fixed an exception when repainting the Android resolution window in Unity 2019.3.x.
- Version Handler: Fixed exception when waiting for enabled editor DLLs to load.
- Android Resolver: Fixed regression when using a Custom Gradle Template on Windows.
- Version Handler: When waiting for newly enabled editor DLLs to load, ignore all DLLs that do not have a file-system location.
- Android Resolver: Fixed resolution when using a Custom Gradle Template with libraries stored in a local maven repository distributed with a plugin installed with the Unity Package Manager.
- All: The new packaging script when run on MacOS was generating a .unitypackage archive that could not be read by Unity on Windows. This release simply repackages the plugin with tar/gzip to fix the problem.
- Package Manager Resolver: Fixed spurious error message when resuming migration after installing a UPM package.
- Package Manager Resolver: Fixed an exception when resuming migration after installing a UPM package.
- Version Handler: Fixed alias traversal bug which caused problems when migrating from installed .unitypackage files to UPM packages.
- Version Handler: Fixed exception in manifest parsing when a manifest is detected with no aliases.
- Package Manager Resolver: Added a method to migrate Version Handler
managed packages installed via
.unitypackageto Unity Package Manager packages. This is initially used to migrate the External Dependency Manager to UPM.
- All: Verbose logging is now no longer automatically enabled in batch mode
across all components. Instead logging can be configured using each
component's verbose logging setting or by using the
-gvh_log_debugcommand line flag when starting Unity. - Version Handler: Sped up version handler updates when the app domain isn't reloaded.
- Version Handler: Fixed the display of the obsolete files clean up dialog when the asset database refreshes.
- Version Handler: Improved reliability of callback from the VersionHandler.UpdateCompleteMethods event when an asset database refresh occurs.
- Version Handler: Fixed duplicate exportPath labels when 'Assets/' is the root of paths assigned to files.
- Version Handler: Handle empty lines in manifest files.
- iOS Resolver: Removed the ability to configure the Xcode target a Cocoapod is added to.
- iOS Resolver: Reverted support for adding Cocoapods to multiple targets as it caused a regression (exception thrown during post-build step) in some versions of Unity.
- Android Resolver: Fixed caching of resolution state which was causing the resolver to always run when no dependencies had changed.
- Package Manager Resolver: Enabled auto-add by default.
- Fixed a bug when retrieving project settings. If a plugin was configured to fetch project settings, if a setting was fetched (e.g "foo") and this setting existed in the system settings but not the project settings the system value would override the default value leading to unexpected behavior.
- Fixed a warning when caching web request classes in Unity 5.6.
- Fixed measurement reporting in Unity 5.x.
- Version Handler: Fixed NullReferenceException when an asset doesn't have an AssetImporter.
- Added documentation to the built plugin.
- Package Manager Resolver: Added the Package Manager Resolver component that allows developers to easily boostrap Unity Package Manager (UPM) registry addition using unitypackage plugins.
- Version Handler: Added a window that allows plugins to managed by the Version Handler to be uninstalled.
- Version Handler: Added support for displaying installed plugins.
- Version Handler: Added support for moving files in plugins to their install locations (if the plugin has been configured to support this).
- iOS Resolver: Added the ability to configure the Xcode target a Cocoapod is added to.
- Fixed upgrade from version 1.2.137 and below after the plugin rename to EDM4U broke the upgrade process.
- Android Resolver: Worked around PlayerSettings.Android.targetSdkVersion returning empty names for some values in 2019.x.
- Version Handler: Fixed the display of the obsolete files clean up window.
- Version Handler: Fixed managed file check when assets are modified in the project after plugin import.
- Renamed package to External Package Manager for Unity (EDM4U).
We changed this to reflect what this plugin is doing today which is far more
than the original scope which just consisted of importing jar files from the
Android SDK maven repository.
Scripts that used to pull
play-services-resolver*.unitypackagewill now have to requestexternal-dependency-manager*.unitypackageinstead. We'll still be shipping aplay-services-resolver*_manifest.txtfile to handle upgrading from older versions of the plugin.
- All Components: Added reporting of usage so that we can remotely detect errors and target improvements.
- Android Resolver: Added support for *Dependencies.xml files in Unity Package Manager packages.
- iOS Resolver: Added support for *Dependencies.xml files in Unity Package Manager packages.
- Version Handler: Disabled attempts to disable asset metadata modification when assets are in a Unity Package Manager managed package.
- Android Resolver: Fixed OpenJDK path discovery in Unity 2019.3.1.
- All Components: Fixed stack overflow when loading project settings.
- All Components: Fixed an issue which caused project settings to be cleared when running in batch mode.
- All Components: Failure to save project settings will now report an error to the log rather than throwing an exception.
- Android Resolver: Worked around expansion of DIR_UNITYPROJECT on Windows breaking Gradle builds when used as part of a file URI.
- Android Resolver: mainTemplate.gradle is only written if it needs to be modified.
- Version Handler: Improved execution of events on the main thread in batch mode.
- Version Handler: Improved log level configuration at startup.
- Version Handler: Improved performance of class lookup in deferred method calls.
- Version Handler: Fixed rename to enable / disable for editor assets.
- iOS Resolver: Improved log level configuration at startup.
- Android Resolver: Improved local maven repo path reference in mainTemplate.gradle using DIR_UNITYPROJECT. DIR_UNITYPROJECT by Unity to point to the local filesystem path of the Unity project when Unity generates the Gradle project.
- iOS Resolver: Added support for modifying the Podfile before
pod installis executed.
- Version Handler: Fixed invalid classname error when calling
VersionHandler.UpdateVersionedAssets().
- iOS Resolver: Changed Cocoapod integration in Unity 2019.3+ to only add Pods to the UnityFramework target.
- iOS Resolver: Fixed Cocoapod project integration mode with Unity 2019.3+.
- Android Resolver: All Android Resolver settings File paths are now serialized with POSIX directory separators.
- Android Resolver: File paths are now serialized with POSIX directory separators.
- Android Resolver: Fixed resolution when the parent directory of a Unity
project contains a Gradle project (i.e
settings.gradlefile).
- All components: Silenced a warning about not being able to set the console encoding to UTF8.
- Android Resolver: Worked around broken AndroidSDKTools class in some versions of Unity.
- iOS Resolver: Fixed iOS target SDK version check
- Version Handler: Changed clean up obsolete files window so that it doesn't exceed the screen size.
- All components: Fixed regression with source control integration when using Unity 2019.1+.
- All components: Source control integration for project settings.
- Android Resolver: Removed AAR cache as it now makes little difference to incremental resolution performance.
- Android Resolver: Improved embedded resource management so that embedded resources should upgrade when the plugin is updated without restarting the Unity editor.
- Version Handler: Fixed InvokeMethod() and InvokeStaticMethod() when calling methods that have interface typed arguments.
- iOS Resolver: Worked around Unity not loading the iOS Resolver DLL as it referenced the Xcode extension in a public interface. The iOS Resolver DLL still references the Xcode extension internally and just handles missing type exceptions dynamically.
- Android Resolver: Fixed warning about missing Packages folder when loading XML dependencies files in versions of Unity without the package manager.
- Android Resolver: Fixed resolution window progress bar exceeding 100%.
- Android Resolver: If AndroidX is detected in the set of resolved libraries, the user will be prompted to enable the Jetifier.
- Android Resolver: Improved text splitting in text area windows.
- iOS Resolver: Added support for Unity's breaking changes to the Xcode API in 2019.3.+. Cocoapods are now added to build targets, Unity-iPhone and UnityFramework in Unity 2019.3+.
- Android Resolver: Added support for loading *Dependencies.xml files from Unity Package Manager packages.
- Android Resolver: Resolution window is now closed if resolution runs as a pre-build step.
- iOS Resolver: Added support for loading *Dependencies.xml files from Unity Package Manager packages.
- Android Resolver: Fixed generation of relative repo paths when using mainTemplate.gradle resolver.
- Android Resolver: Fixed copy of .srcaar to .aar files in repos embedded in a project when a project path has characters (e.g whitespace) that are escaped during conversion to URIs.
- Android Resolver: Fixed auto-resolution always running if the Android SDK is managed by Unity Hub.
- Android Resolver: Fixed error reported when using Jetifier integration in Unity 2018+ if the target SDK is set to "highest installed".
- Android Resolver: Added initial
Jetifier
integration which simplifies
migration
to Jetpack (AndroidX)
libraries in cases where all dependencies are managed by the Android
Resolver.
This can be enabled via the
Use Jetifieroption in theAssets > Play Services Resolver > Android Resolver > Settingsmenu. Caveats:- If your project contains legacy Android Support Library .jar and .aar
files, these files will need to be removed and replaced with references to
artifacts on Maven via
*Dependencies.xmlfiles so that the Jetifier can map them to Jetpack (AndroidX) libraries. For example, remove the filesupport-v4-27.0.2.jarand replace it with<androidPackage spec="com.android.support:support-v4:27.0.2"/>in a*Dependencies.xmlfile. - If your project contains .jar or .aar files that use the legacy Android
Support Libraries, these will need to be moved into a local Maven repo
See this guide
and then these files should be removed from your Unity project and instead
referenced via
*Dependencies.xmlfiles so that the Jetifier can patch them to reference the Jetpack lirbaries.
- If your project contains legacy Android Support Library .jar and .aar
files, these files will need to be removed and replaced with references to
artifacts on Maven via
- Android Resolver: Disabled version locking of com.android.support:multidex does not use the same versioning scheme as other legacy Android support libraries.
- Version Handler: Made Google.VersionHandler.dll's asset GUID stable across releases. This faciliates error-free import into projects where Google.VersionHandler.dll is moved from the default install location.
- Android Resolver: Fix copying of .srcaar to .aar files for mainTemplate.gradle resolution. PluginImporter configuration was previously not being applied to .aar files unless the Unity project was saved.
- Android Resolver: Fixed resolution of Android dependencies without version specifiers.
- Android Resolver: Fixed Maven repo not found warning in Android Resolver.
- Android Resolver: Fixed Android Player directory not found exception in Unity 2019.x when the Android Player isn't installed.
- Android Resolver: Fixed exception due to Unity 2019.3.0a4 removing x86 from the set of supported ABIs.
- Android Resolver: Added support for ABI stripping when using mainTemplate.gradle. This only works with AARs stored in repos on the local filesystem.
- Android Resolver: If local repos are moved, the plugin will search the project for matching directories in an attempt to correct the error.
- Version Handler: Files can be now targeted to multiple build targets using multiple "gvh_" asset labels.
- Android Resolver: "implementation" or "compile" are now added correctly to mainTemplate.gradle in Unity versions prior to 2019.
- Android Resolver: Added option to disable addition of dependencies to
mainTemplate.gradle.
See
Assets > Play Services Resolver > Android Resolver > Settings. - Android Resolver: Made paths to local maven repositories in mainTemplate.gradle relative to the Unity project when a project is not being exported.
- Android Resolver: Fixed builds with mainTemplate.gradle integration in Unity 2019.
- Android Resolver: Changed dependency inclusion in mainTemplate.gradle to use "implementation" or "compile" depending upon the version of Gradle included with Unity.
- Android Resolver: Gracefully handled exceptions if the console encoding can't be modified.
- Android Resolver: Now gracefully fails if the AndroidPlayer directory can't be found.
- Version Handler: Fixed invocation of methods with named arguments.
- Version Handler: Fixed occasional hang when the editor is compiling while activating plugins.
- Android Resolver: Fixed inclusion of some srcaar artifacts in builds with Gradle builds when using mainTemplate.gradle.
- Added links to documentation from menu.
- Android Resolver: Added option to auto-resolve Android libraries on build.
- Android Resolver: Added support for packaging specs of Android libraries.
- Android Resolver: Pop up a window when displaying Android dependencies.
- Android Resolver: Support for Unity 2019 Android SDK and JDK install locations
- Android Resolver: e-enable AAR explosion if internal builds are enabled.
- Android Resolver: Gracefully handle exceptions on file deletion.
- Android Resolver: Fixed Android Resolver log spam on load.
- Android Resolver: Fixed save of Android Resolver PromptBeforeAutoResolution setting.
- Android Resolver: Fixed AAR processing failure when an AAR without classes.jar is found.
- Android Resolver: Removed use of EditorUtility.DisplayProgressBar which was occasionally left displayed when resolution had completed.
- Version Handler: Fixed asset rename to disable when a disabled file exists.
- Version Handler: Fixed occasional hang on startup.
- Version Handler: Added support for enabling / disabling assets that do not support the PluginImporter, based upon build target selection.
- Android Resolver: Added support for the global specification of maven repos.
- iOS Resolver: Added support for the global specification of Cocoapod sources.
- iOS Resolver: Added support for development pods in Xcode project integration mode.
- iOS Resolver: Added support for source pods with resources in Xcode project integration mode.
- Android Resolver: Fixed reference to Java tool path in logs.
- Android and iOS Resolvers: Changed command line execution to emit a warning rather than throwing an exception and failing, when it is not possible to change the console input and output encoding to UTF-8.
- Android Resolver: Added menu option and API to delete resolved libraries.
- Android Resolver: Added menu option and API to log the repos and libraries currently included in the project.
- Android Resolver: If Plugins/Android/mainTemplate.gradle file is present and Gradle is selected as the build type, resolution will simply patch the file with Android dependencies specified by plugins in the project.
- Android Resolver: Changed Android ABI selection method from using whitelisted Unity versions to type availability. This fixes an exception on resolution in some versions of Unity 2017.4.
- Android Resolver: Whitelisted Unity 2017.4 and above with ARM64 support.
- Android Resolver: Fixed Java version check to work with Java SE 12 and above.
- Android Resolver: Fixed the text overflow on the Android Resolver prompt before initial run to fit inside the buttons for smaller screens.
- Android Resolver: Prompt the user before the resolver runs for the first time and allow the user to elect to disable from the prompt.
- Android Resolver: Change popup warning when resolver is disabled to be a console warning.
- Android Resolver: Fixed AAR processing sometimes failing on Windows due to file permissions.
- Android Resolver: Improved performance of project property polling.
- Version Handler: Fixed callback of VersionHandler.UpdateCompleteMethods when the update process is complete.
- iOS Resolver: Pod declaration properties can now be set via XML pod references. For example, this can enable pods for a subset of build configurations.
- iOS Resolver: Fixed incremental builds after local pods support caused regression in 1.2.96.
- Android Resolver: Reduced memory allocation for logic that monitors build settings when auto-resolution is enabled. If auto-resolution is disabled, almost all build settings are no longer polled for changes.
- Android Resolver: Fixed repacking of AARs to exclude .meta files.
- Android Resolver: Only perform auto-resolution on the first scene while building.
- Android Resolver: Fixed parsing of version ranges that include whitespace.
- iOS Resolver: Added support for local development pods.
- Version Handler: Fixed Version Handler failing to rename some files.
- Android Resolver: Fixed auto-resolution running in a loop in some scenarios.
- iOS Resolver: Added support for PODS_TARGET_SRCROOT in source Cocoapods.
- Android Resolver: Fixed removal of Android libraries on auto-resolution when
*Dependencies.xmlfiles are deleted.
- Android Resolver: Worked around auto-resolution hang on Windows if resolution starts before compilation is finished.
- Android Resolver: Fixed Android Resolution when the selected build target isn't Android.
- Added C# assembly symbols the plugin to simplify debugging bug reports.
- Android Resolver: Fixed transitive dependency selection of version locked packages.
- Fixed FileLoadException in ResolveUnityEditoriOSXcodeExtension an assembly can't be loaded.
- Improved reporting of resolution attempts and conflicts found in the Android Resolver.
- iOS Resolver now correctly handles sample code in CocoaPods. Previously it would add all sample code to the project when using project level integration.
- Android Resolver now correctly handles Gradle conflict resolution when the resolution results in a package that is compatible with all requested dependencies.
- Fixed Android Resolver "Processing AARs" dialog getting stuck in Unity 5.6.
- Fixed Android Resolver exception in OnPostProcessScene() when the Android platform isn't selected.
- Added support for synchronous resolution in the Android Resolver. PlayServicesResolver.ResolveSync() now performs resolution synchronously.
- Auto-resolution in the Android Resolver now results in synchronous resolution of Android dependencies before the Android application build starts via UnityEditor.Callbacks.PostProcessSceneAttribute.
- Fixed Android Resolver crash when the AndroidResolverDependencies.xml file can't be written.
- Reduced log spam when a conflicting Android library is pinned to a specific version.
- Fixed Android Resolver failures due to an in-accessible AAR / JAR explode cache file. If the cache can't be read / written the resolver now continues with reduced performance following recompilation / DLL reloads.
- Fixed incorrect version number in plugin manifest on install. This was a minor issue since the version handler rewrote the metadata after installation.
- Added support for alphanumeric versions in the Android Resolver.
- Fixed Android Resolver selection of latest duplicated library.
- Fixed Android Resolver conflict resolution when version locked and non-version locked dependencies are specified.
- Fixed Android Resolver conflict resolution when non-existent artifacts are referenced.
- Fixed editor error that would occur when when
PlayerSettings.Android.targetArchitectureswas set toAndroidArchitecture.All.
- Fixed project level settings incorrectly falling back to system wide settings when default property values were set.
- Fixed AndroidManifest.xml patching on Android Resolver load in Unity 2018.x.
- Added support for overriding conflicting dependencies.
- Android Resolver now supports Unity's 2018 ABI filter (i.e arm64-v8a).
- Reduced Android Resolver build option polling frequency.
- Disabled Android Resolver auto-resolution in batch mode. Users now need to explicitly kick off resolution through the API.
- All Android Resolver and Version Handler dialogs are now disabled in batch mode.
- Verbose logging for all plugins is now enabled by default in batch mode.
- Version Handler bootstrapper has been improved to no longer call UpdateComplete multiple times. However, since Unity can still reload the app domain after plugins have been enabled, users still need to store their plugin state to persistent storage to handle reloads.
- Android Resolver no longer incorrectly adds MANIFEST.MF files to AARs.
- Android Resolver auto-resolution jobs are now unscheduled when an explicit resolve job is started.
- Fixed variable replacement in AndroidManifest.xml files in the Android Resolver. Version 1.2.75 introduced a regression which caused all variable replacement to replace the entire property value rather than the component of the property that referenced a variable. For example, given "applicationId = com.my.app", "${applicationId}.foo" would be incorrectly expanded as "com.my.app" rather than "com.my.app.foo". This resulted in numerous issues for Android builds where content provider initialization would fail and services may not start.
- Gradle prebuild experimental feature has been removed from the Android Resolver. The feature has been broken for some time and added around 8MB to the plugin size.
- Added better support for execution of plugin components in batch mode. In batch mode UnityEditor.update is sometimes never called - like when a single method is executed - so the new job scheduler will execute all jobs synchronously from the main thread.
- Android Resolver now monitors the Android SDK path when auto-resolution is enabled and triggers resolution when the path is modified.
- Android auto-resolution is now delayed by 3 seconds when the following build
settings are changed:
- Target ABI.
- Gradle build vs. internal build.
- Project export.
- Added a progress bar display when AARs are being processed during Android resolution.
- Fixed incorrect Android package version selection when a mix of version-locked and non-version-locked packages are specified.
- Fixed non-deterministic Android package version selection to select the highest version of a specified package rather than the last package specification passed to the Gradle resolution script.
- Added workaround for broken AndroidManifest.xml variable replacement in Unity 2018.x. By default ${applicationId} variables will be replaced by the bundle ID in the Plugins/Android/AndroidManifest.xml file. The behavior can be disabled via the Android Resolver settings menu.
- Fixed spurious warning message about missing Android plugins directory on Windows.
- Fixed spurious warning message about missing Android plugins directory.
- Fixed resolution of Android dependencies when the
Assets/Plugins/Androiddirectory is named in a different case e.gAssets/plugins/Android.
- Fixed bitcode flag being ignored for iOS pods.
- Fixed escaping of local repository paths in Android Resolver.
- Added support for granular builds of Google Play Services.
- Improved support for iOS source-only pods in Unity 5.5 and below.
- Fixed Version Handler renaming of Linux libraries with hyphens in filenames. Previously, libraries named Foo-1.2.3.so were not being renamed to libFoo-1.2.3.so on Linux which could break native library loading on some versions of Unity.
- Fix CocoaPods casing in logs and comments.
- Fixed bug in download_artifacts.gradle (used by Android Resolver) which reported a failure if required artifacts already exist.
- Fixed iOS Resolver include search paths taking precedence over system headers when using project level resolution.
- Fixed iOS Resolver includes relative to library root, when using project level resolution.
- Improved error reporting when a file can't be moved to trash by the Version Handler.
- Fixed Android Resolver throwing NullReferenceException when the Android SDK path isn't set.
- Fixed Version Handler renaming files with underscores if the "Rename to Canonical Filenames" setting is enabled.
- Fixed Android Resolver reporting non-existent conflicting dependencies when Gradle build system is enabled.
- Added support for Maven / Ivy version specifications for Android packages.
- Added support for Android SNAPSHOT packages.
- Fixed Openjdk version check.
- Fixed non-deterministic Android package resolution when two packages contain an artifact with the same name.
- Fixed execution of Android Gradle resolution script when it's located in a path with whitespace.
- Removed legacy resolution method from Android Resolver. It is now only possible to use the Gradle or Gradle prebuild resolution methods.
- Updated Gradle wrapper to 4.2.1 to fix issues using Gradle with the latest Openjdk.
- Android Gradle resolution now also uses gradle.properties to pass parameters to Gradle in an attempt to workaround problems with command line argument parsing on Windows 10.
- Fixed Gradle artifact download with non-version locked artifacts.
- Changed iOS resolver to only load dependencies at build time.
- Force Android Resolution when the "Install Android Packages" setting changes.
- Fixed execution of command line tools on Windows when the path to the tool contains a single quote (apostrophe). In this case we fallback to executing the tool via the system shell.
- Changed Android Resolver "resolution complete" dialog so that it now displays failures.
- Android Resolver now detects conflicting libraries that it does not manage warning the user if they're newer than the managed libraries and prompting the user to clean them up if they're older or at the same version.
- Improved Android Resolver auto-resolution speed.
- Fixed bug in the Gradle Android Resolver which would result in resolution succeeding when some dependencies are not found.
- Changed Android Resolver's Gradle resolution to resolve conflicting dependencies across Google Play services and Android Support library packages.
- Changed iOS Resolver to execute the CocoaPods "pod" command via the shell by default. Some developers customize their shell environment to use custom ssh certs to access internal git repositories that host pods so executing "pod" via the shell will work for these scenarios. The drawback of executing "pod" via the shell could potentially cause users problems if they break their shell environment. Though users who customize their shell environments will be able to resolve these issues.
- Added option to disable the Gradle daemon in the Android Resolver. This daemon is now disabled by default as some users are getting into a state where multiple daemon instances are being spawned when changing dependencies which eventually results in Android resolution failing until all daemon processes are manually killed.
- Android resolution is now always executed if the user declines the update of their Android SDK. This ensure users can continue to use out of date Android SDK packages if they desire.
- Removed modulemap parsing in iOS Resolver. The framework *.modulemap did not need to be parsed by the iOS Resolver when injecting Cocoapods into a Xcode project. Simply adding a modular framework to a Xcode project results in Xcode's Clang parsing the associated modulemap and injecting any compile and link flags into the build process.
- Changed settings to be per-project by default.
- Added Google maven repository to fix GradlePrebuild resolution with Google components.
- Fixed Android Resolution failure with spaces in paths.
- Android and iOS dependencies can now be specified using *Dependencies.xml files. This is now the preferred method for registering dependencies, we may remove the API for dependency addition in future.
- Added "Reset to Defaults" button to each settings dialog to restore default settings.
- Android Resolver now validates the configured JDK is new enough to build recently released Android libraries.
- Fixed a bug that caused dependencies with the "LATEST" version specification to be ignored when using the Gradle mode of the Android Resolver.
- Fixed a race condition when running Android Resolution.
- Fixed Android Resolver logging if a PlayServicesSupport instance is created with no logging enabled before the Android Resolver is initialized.
- Fixed iOS resolver dialog in Unity 4.
- Fixed iOS Cocoapod Xcode project integration in Unity 4.
- GradlePrebuild Android resolver on Windows now correctly locates dependent data files.
- Improved Android package auto-resolution and fixed clean up of stale dependencies when using Gradle dependency resolution.
- Enabled autoresolution for Gradle Prebuild.
- Made the command line dialog windows have selectable text.
- Fixed incorrect "Android Settings" dialog disabled groups.
- Updated PlayServicesResolver android platform detection to use the package manager instead of the 'android' tool.
- UnityCompat reflection methods 'GetAndroidPlatform' and 'GetAndroidBuildToolsVersion' are now Obsolete due to dependence on the obsolete 'android' build tool.
- Fixed Gradle resolution in the Android Resolver when running PlayServicesResolver.Resolve() in parallel or spawning multiple resolutions before the previous resolve completed.
- Fixed Xcode project level settings not being applied by IOS Resolver when Xcode project pod integration is enabled.
- IOS Resolver's Xcode workspace pod integration is now disabled when Unity Cloud Build is detected. Unity Cloud Build does not follow the same build process as the Unity editor and fails to open the generated xcworkspace at this time.
- Moved Android Resolver Gradle Prebuild scripts into Google.JarResolver.dll. They are now extracted from the DLL when required.
- AARs / JARs are now cleaned up when switching the Android resolution strategy.
- Android Resolver now supports resolution with Gradle. This enables support for non-local artifacts.
- Android Resolver's Gradle Prebuild now uses Android build tools to determine the Android platform tools version rather than relying upon internal Unity APIs.
- Android Resolver's Gradle Prebuild now correctly strips binaries that are not required for the target ABI.
- Fixed an issue in VersionHandler where disabled targets are ignored if the "Any Platform" flag is set on a plugin DLL.
- Exposed GooglePlayServices.PlayServicesResolver.Resolve() so that it's possible for a script to be notified when AAR / Jar resolution is complete. This makes it easier to setup a project to build from the command line.
- VersionHandler.UpdateCompleteMethods allows a user to provide a list of methods to be called when VersionHandlerImpl has completed an update. This makes it easier to import a plugin and wait for VersionHandler to execute prior executing a build.
- VersionHandler will now rename Linux libraries so they can target Unity versions that require different file naming. Libraries need to be labelled gvh_linuxlibname-${basename} in order to be considered for renaming. e.g gvh_linuxlibname-MyLib will be named MyLib.so in Unity 5.5 and below and libMyLib.so in Unity 5.6 and above.
- Made VersionHandler bootstrap module more robust when calling static methods before the implementation DLL is loaded.
- Added a bootstrap module for VersionHandler so the implementation of the VersionHandler module can be versioned without resulting in a compile error when imported at different versions across multiple plugins.
- Added support for build target selection based upon .NET framework version in the VersionHandler. When applying either gvh_dotnet-3.5 or gvh_dotnet-4.5 labels to assets, the VersionHandler will only enable the asset for the specified set of build targets when the matching .NET framework version is selected in Unity 2017's project settings. This allows assets to be provided in a plugin that need to differ based upon .NET version.
- Force expansion of AARs with native components when using Unity 2017 with the internal build system. In contrast to Unity 5.x, Unity 2017's internal build system does not include native libraries included in AARs. Forcing expansion of AARs with native components generates an Ant / Eclipse project for each AAR which is correctly included by Unity 2017's internal build system.
- Fixed Cocoapods being installed when the build target isn't iOS.
- Added support for malformed AARs with missing classes.jar.
- Added support for the Android sdkmanager tool.
- Fixed non-shell command line execution (regression from Cocoapod installation patch).
- Added support for stdout / stderr redirection when executing commands in shell mode. This fixes CocoaPod tool installation when shell mode is enabled.
- Fixed incremental builds when additional sources are specified in the Podfile.
- Fixed a crash when importing Version Handler into Unity 4.7.x.
- Fixed an issue in the Jar Resolver which incorrectly notified event handlers of bundle ID changes when the currently selected (not active) build target changed in Unity 5.6 and above.
- Added option to control file renaming in Version Handler settings. Disabling file renaming (default option) significantly increases the speed of file version management operations with the downside that any files that are referenced directly by canonical filename rather than asset ID will no longer be valid.
- Improved logging in the Version Handler.
- Fixed an issue in the Version Handler which caused it to not re-enable plugins when re-importing a custom package with disabled version managed files.
- Fixed a bug with gradle prebuild resolver on windows.
- Fixed a bug in the iOS resolver with incremental builds.
- Fixed misdetection of Cocoapods support with Unity beta 5.6.
- Fix for googlesamples#48 Android dependency version number parsing when "-alpha" (etc.) are included in dependency (AAR / JAR) versions.
- Attempted to fix googlesamples#48 where a NullReferenceException could occur if a target file does not have a valid version string.
- Fixed Jar Resolver exploding and deleting AAR files it isn't managing.
- Added support for preserving Unity pods such as when GVR is enabled.
- Fixed auto-resolution when an Android application ID is modified.
- Fixed Unity version number parsing on machines with a locale that uses "," for decimal points.
- Fixed null reference exception if JDK path isn't set.
- Added warning when the Jar Resolver's background resolution is disabled.
- Fixed support of AARs with native libraries when using Gradle.
- Fixed extra repository paths when resolving dependencies.
- Added experimental Android resolution using Gradle. This alternative resolver supports proguard stripping with Unity's internal build system.
- Added Android support for single ABI builds when using AARs include native libraries.
- Disabled Android resolution on changes to all .cs and .js files. File patterns that are monitored for auto-resolution can be added using PlayServicesResolver.AddAutoResolutionFilePatterns().
- Added tracking of resolved AARs and JARs so they can be cleaned up if they're no longer referenced by a project.
- Added persistence of AAR / JAR version replacement for each Unity session.
- Added settings dialog to the iOS resolver.
- Integrated Cocoapod tool installation in the iOS resolver.
- Added option to run pod tool via the shell.
- Fixed build of some source Cocoapods (e.g Protobuf).
- VersionHandler no longer prompts to delete obsolete manifests.
- iOS resolver handles Cocoapod installation when using Ruby < 2.2.2.
- Added workaround for package version selection when including Google Play Services on Android.
- Fixed support for pods that reference static libraries.
- Fixed support for resource-only pods.
- Fixed re-explosion of AARs when the bundle ID is modified.
- Added support for Android Studio builds.
- Added support for native (C/C++) shared libraries in AARs.
- Fixed SDK manager path retrieval.
- Also, report stderr when it's not possible to run the "pod" tool.
- Handle exceptions thrown by Unity.Cecil on asset rename
- Fixed IOSResolver to handle PlayerSettings.iOS.targetOSVersionString
- Improved error reporting when "pod repo update" fails.
- Added detection of xml format xcode projects generated by old Cocoapods installations.
- Increased speed of JarResolver resolution.
- Fixed JarResolver caches getting out of sync with requested dependencies by removing the caches.
- Fixed JarResolver explode cache always being rewritten even when no dependencies change.
- Fixed VersionHandler build errors with Unity 5.5, due to the constantly changing BuildTarget enum.
- Added support for Unity configured JDK Path rather than requiring JAVA_HOME to be set in the Jar Resolver.
- Fixed IOSResolver errors when iOS support is not installed.
- Added fallback to "pod" executable search which queries the Ruby Gems package manager for the binary install location.
- Added crude support for source only Cocoapods to the IOSResolver.
- Automated resolution of out of date pod repositories.
- Fixed exception when reporting conflicting dependencies.
- Fixed issue working with Unity 5.5
- Fixed issue with PlayServicesResolver corrupting other iOS dependencies.
- Updated build script to use Unity distributed tools for building.
- Removed 1.2 Resolver and hardcoded whitelist of AARs to expand.
- Improved error reporting when the "jar" executable can't be found.
- Removed the need to set JAVA_HOME if "jar" is in the user's path.
- Fixed spurious copying of partially matching AARs.
- Changed resolver to only copy / expand when source AARs change.
- Auto-resolution of dependencies is now performed when the Android build target is selected.
- Expand AARs that contain manifests with variable expansion like ${applicationId}.
- Added optional logging in the JarResolverLib module.
- Integration with the Android SDK manager for dependencies that declare required Android SDK packages.
- Handles resolving dependencies when the artifacts are split across 2 repos.
- #4 Misdetecting version for versions like 1.2-alpha. These are now string compared if alphanumeric
- Removed resolver creation via reflection since it did not work all the time. Now a resolver needs to be loaded externally (which is existing behavior).
- Expose PlayServicesResolver properties to allow for script access.
- Explodes firebase-common and firebase-measurement aar files to support ${applicationId} substitution.
- #1 Spaces in project path not handled when exploding Aar file.
- #2 Script compilation error: TypeLoadException.
- Adds friendly alert when JAVA_HOME is not set on Windows platforms.
- Adds flag for disabling background resolution.
- Expands play-services-measurement and replaces ${applicationId} with the bundle Id.
- Fixes infinite loop of resolution triggered by resolution.