Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice
  3. Join us on November 16th, 2023, between 1 pm and 9 pm CET for Ask the Experts Online on Discord and on Unity Discussions.
    Dismiss Notice

Unity3D Command line Build not accessing libraries and updating Android Manifest

Discussion in 'Editor & General Support' started by sixmindan, Feb 12, 2015.

  1. sixmindan

    sixmindan

    Joined:
    Sep 9, 2014
    Posts:
    4
    I have a unity project with multiple android plugins.

    The plugins are placed in the recommended folders /Assets/Plugins/Android/NameOfPlugin and each have their own AndroidManifest.xml and .project file. I also have an AndroidManifest.xml in /Assets/Plugins/Android to ensure the default unity manifest is overridden.

    When building out a .apk from any of the dev machines in studio, the AndroidManifest is correctly compiled into a single .xml file containing all required activities. However, when building on a Mac Mini via commandline this does not happen. The AndroidManifest.xml is missing required code and the app doesn't work.

    This only seems to be the case for one of the projects I'm working on, the manifest is correctly compiled on test projects I've created.

    I have done fresh installs of everything, tried different configurations, loads of things but to no avail. Anyone have any ideas as to what might be going wrong?
     
  2. seaders

    seaders

    Joined:
    Oct 28, 2014
    Posts:
    29
    One of Dan's colleagues here, and after doing a straight up text diff on the two "Editor.log" files of Unity's editor, there was one glaring line that was missing from the broken builder,

    Code (csharp):
    1. DisplayProgressbar: Android Library Support
    Googling that lead me to http://answers.unity3d.com/questions/792979/android-library-support-build-issue.html who had already discovered the answer, which was damn near exactly the same as what we had suffered,

    We've just done the same ourselves, and it's solved the issue.