Community Q&A

Welcome to Audiokinetic’s community-driven Q&A forum. This is the place where Wwise and Strata users help each other out. For direct help from our team, please use the Support Tickets page. To report a bug, use the Bug Report option in the Audiokinetic Launcher. (Note that Bug Reports submitted to the Q&A forum will be rejected. Using our dedicated Bug Report system ensures your report is seen by the right people and has the best chance of being fixed.)

To get the best answers quickly, follow these tips when posting a question:

  • Be Specific: What are you trying to achieve, or what specific issue are you running into?
  • Include Key Details: Include details like your Wwise and game engine versions, operating system, etc.
  • Explain What You've Tried: Let others know what troubleshooting steps you've already taken.
  • Focus on the Facts: Describe the technical facts of your issue. Focusing on the problem helps others find a solution quickly.

Integrating Wwise to Unity-project broke Unity Cloud Build for macOS

0 votes

I'm on a team developing a game in Unity and we decided to integrate Wwise to the project! We use the Unity Cloud Build service to make daily builds of the game.

 

We are currently developing for Windows and Mac. We have the following working:

Windows: Playing in Unity Editor with sound from Wwise

Windows: Building locally with sound from Wwise

Windows: Building with Unity Cloud Build with sound from Wwise

Mac: Playing in Unity Editor with sound from Wwise

Mac: Building locally with sound from Wwise

 

What doesn't work is:

Mac: Building with Unity Cloud Build with sound from Wwise

 

Cloud build tells that the build is succesfull, but when trying to open the build on Mac, we get the following error:

"Default Mac desktop Universal" is damaged and can’t be opened. You should move it to the Bin.

 

We didn't have the issue before integrating Wwise.

 

I noticed, that on the first build after integrating Wwise this line appeared in the build log:

63: [Unity] UnityEditor.OSXStandalone.CodeSigning.BundleSigner:LogSignErrorIfNeeded (UnityEditor.OSXStandalone.CodeSigning.SigningError) (at /Users/bokken/buildslave/unity/build/PlatformDependent/OSXPlayer/Extensions/Managed/CodeSigning/BundleSigner.cs:318)

Could be a lead.

I've also been looking around the internet and it might be related to this:

https://issuetracker.unity3d.com/issues/macos-build-is-damaged-and-cannot-be-opened-error-when-downloading-unity-build-from-internet

Could be a lead as well.

Any help would be highly appreciated, as we rely heavily on the Unity Cloud Build service! 

---

We use:

Unity 2020.3.0f1
Wwise Integration 2021.1.1.7601.2102

 

in General Discussion by Gizmo (170 points)

1 Answer

0 votes
Only way I could get it working was by setting notarization up in the build pipeline. That solved it for me :-)
by Gizmo (170 points)
Powered by Question2Answer
...