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. Unite 2023 Registrations are now LIVE! We are thrilled to announce that Unite 2023 Registration is now live and open for all!
    Dismiss Notice
New Forum User Notice Unite 2023 Registrations are now LIVE!

Resolved Building on MacOS Fails

Discussion in 'Vivox (Voice & Text Chat)' started by YoungDeveloper, Mar 15, 2022.

Thread Status:
Not open for further replies.

  1. YoungDeveloper

    YoungDeveloper

    Joined:
    Jun 28, 2013
    Posts:
    63
    Unity version: 2020.3.18f1 LTS

    We are struggling bulilding the app for macos. Our building pipeline works perfectly when we remove vivox dependencies but problem suddenly comes up when they're included and used. Works perfectly on windows.It appears that libdyld.dylib tries to call some address out of memory and player fails to run, unfortunately I couldn't open .bundle files so I couldn't check where they are being used.

    Code (CSharp):
    1. libdyld.dylib`start:
    2.    0x7fff203a5f3c <+0>: nop
    3. ->  0x7fff203a5f3d <+1>: movl   %eax, %edi
    4.    0x7fff203a5f3f <+3>: callq  0x7fff203c2784            ; symbol stub for: exit
    5.    0x7fff203a5f44 <+8>: hlt

    we are using newest version of vivox unity package (5.14.1.uni.0 released on June 21, 2021 to be precise)Game is opening, unity logo is visible but shortly after that game crashes with mysterious low-level crash message.I tested it in Macbook Pro M1, also tried intel build under rosetta but it didn't help much.When running from editor I had problems with allowing plugins to run (I got libortp.bundle not allowed) this prompt was showing all the time no matter what I clicked like it wouldn't be signed, I had to kill unity. When I have overriden apple quarantine manually it finally worked from editor but the build is crashing. Let me know what info you might need to check it and I'll provide it.



     
    Last edited: Mar 15, 2022
    YoungDeveloper, Mar 15, 2022
    #1

  2. YoungDeveloper

    YoungDeveloper

    Joined:
    Jun 28, 2013
    Posts:
    63
    Still doesn't work, right now its a blocker for our macos build
     
    YoungDeveloper, Mar 17, 2022
    #2

  3. UnityKip

    UnityKip

    Unity Technologies

    Joined:
    Nov 15, 2021
    Posts:
    36
    Hi @YoungDeveloper

    Before we dive too far into troubleshooting, would you be able to update Vivox to the latest version? The version you have listed is from the Unity Asset Store which is nearly a year behind the version (15.1.170000) available through the Package Manager.

    To upgrade, please use the following steps:
    1. Remove the current Vivox version from your Project.
    2. Add "com.unity.services.vivox": "15.1.170000-pre.1" to your Project's manifest.json
    • You can also find these steps on your Unity Dashboard under Multiplayer -> Vivox -> About & Support -> Download the Package
    ​

    If this does not resolve the issue or you are unable to upgrade, I'd recommend that you open a service ticket for further assistance as we will need you to upload the crash logs and provide the low-level error message. This is also found on the Unity Dashboard under Help & Support -> File a Ticket -> Multiplayer -> Vivox.

    Based on what you've provided, I'd initially suspect an entitlement mismatch with our old package or an outdated security library in the older version of Vivox. Without upgrading we will likely need to see your code to try and reproduce as this does not seem to be a known issue with 5.14.1.uni.0.

    We'll keep an eye out for a ticket from you, but please update the thread if the upgrade is enough.

    Regards,
    -Kip
     
    UnityKip, Mar 17, 2022
    #3
    YoungDeveloper likes this.

  4. YoungDeveloper

    YoungDeveloper

    Joined:
    Jun 28, 2013
    Posts:
    63
    Hi @UnityKip

    Thank you for detailed explanation
    Import process and unity dashboard integration steps were very clear and understandable.

    Only thing what I noticed:
    When vovix package finished auto importing from manifest it also imported Newtonsoft.Json.10.0 library which was placed in Assets/Packages folder.

    But that library already exists internally in unity which gave out duplicate assembly error in editor.
    I manually delete newly imported Assets/Packages and there are no more error. Is this expected behavior ?

    We are now building macos shortly will post results here.
     
    Last edited: Mar 17, 2022
    YoungDeveloper, Mar 17, 2022
    #4

  5. YoungDeveloper

    YoungDeveloper

    Joined:
    Jun 28, 2013
    Posts:
    63
    YoungDeveloper, Mar 18, 2022
    #5

  6. UnityKip

    UnityKip

    Unity Technologies

    Joined:
    Nov 15, 2021
    Posts:
    36
    Hi @YoungDeveloper

    Thank you for following up and for the next-steps fix. Glad to hear that the upgrade fixed your issue!

    You may wish to review our iOS App Development documentation as it details several common issues we see that are similar to the microphone permission requirement you linked above.

    Please don't hesitate to open a new thread if you need further assistance and best of luck in your development!

    -Kip
     
    UnityKip, Mar 18, 2022
    #6
Thread Status:
Not open for further replies.