Скачать или смотреть Resolving Build Failed Error in Unity Due to Duplicate Classes

Learn how to fix Unity build errors caused by duplicate classes in Google Play Services libraries by following these practical steps.
---
This video is based on the question https://stackoverflow.com/q/73671891/ asked by the user 'Panso' ( https://stackoverflow.com/u/19964681/ ) and on the answer https://stackoverflow.com/a/73679436/ provided by the user 'YogeshBen' ( https://stackoverflow.com/u/11209506/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Why I can't build my project why this error?

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Fixing Build Failed Errors in Unity: Resolving Duplicate Classes

If you've been developing games using Unity, you may have encountered frustrating build errors that can halt your progress. One common issue arises when building your project for Android, resulting in a FAILURE: Build failed with an exception message. This guide will explore the underlying cause of these errors and provide a step-by-step guide to effectively resolve the problem.

Understanding the Problem

The error logs show that your project is experiencing class duplication caused by conflicting versions of the Google Play Services libraries. Specifically, the error indicates that two libraries contain the same classes:

com.google.android.gms.play-services-games-v2-17.0.0

com.google.android.gms.play-services-games-21.0.0

This overlap leads to confusion in the build process, as the compiler cannot determine which version of the class to use, ultimately resulting in a build failure.

Steps to Resolve the Error

1. Identify the Duplicate Libraries

Before we take action, it's essential to pinpoint the conflicting libraries. The error message gives us a clear indication of the libraries in question. By identifying these conflicts, we can move forward with a targeted solution.

2. Disable the Conflicting Library

The simplest and most effective solution is to disable the older library version that is causing the conflict. In this case, you'll want to disable com.google.android.gms.play-services-games-v2-17.0.0. Here’s how to do this:

Open your Unity project.

Navigate to your project settings and locate the Player Settings for Android.

Check your Dependencies. You can typically find this under the Assets folder or the Plugins directory.

Disable or Remove the conflicted library (com.google.android.gms.play-services-games-v2-17.0.0). You can do this in the build settings or the Gradle build files where the dependencies are listed.

Ensure that the remaining library (com.google.android.gms.play-services-games-21.0.0) is correctly referenced.

3. Rebuild the Project

Once you have removed the conflicting library:

Attempt to rebuild your project. Go to File - Build Settings - and click on Build or Build and Run.

4. Verify Success and Test

If the build completes without errors, congratulations! You've successfully resolved the conflict. However, it's essential to test your application thoroughly to ensure that everything works smoothly, particularly since you were experiencing crashes previously.

Conclusion

Building projects in Unity can be a challenging endeavor when faced with compiler errors and class duplication issues, particularly when dealing with external libraries like Google Play Services. By following the outlined steps and disabling the conflicting library, you should be able to resolve the build failure and get back to creating amazing games. Remember to thoroughly test your project after making such changes to ensure everything runs as intended.

If you continue to face issues or have questions, don't hesitate to seek help from online communities or forums dedicated to Unity development. Happy coding!