Could not launch auvaltool internal error

[alana314]

When I try to open and build the AU in the demo IPlugEffect in Xcode 9.4.1 in OS X 10.13.6, the build succeeds but then I get "Could not launch auvaltool - internal error." When I try validating it in Logic, the validator crashes.

[kyr0]

I ran into the very same issue:

So I digged a little deeper and I found the reasons for it:

• auvaltool executable can't be found / or is not reachable to Xcode for execution (maybe security considerations)

• the schema is configured to debug auvaltool but it doesn't contain the correct debug symbols!

• the build step to build the AU in XCode is set up with dummy data to call auvaltool.

• Option A: Disable the "Run" task in Xcode and run auval in a terminal on your own like this with the correct arguments that match your plugin id's: auval -v aufx $PLUG_UNIQUE_ID $PLUG_MFR_ID, i.e.: auval -v aufx Lapa AHVI

• Option B: Fix the schema config in Xcode like this:

1) Open a terminal and run: cp /usr/bin/auval /Applications/auval. This will copy the binary of auval (auvaltool is only a symbolic link) -- and place it into a place your user can reach without any security limitation.

2) We gonna fix the schema config:

3) Take a look into your resource.h. Note the values of PLUG_UNIQUE_ID and PLUG_MFR_ID:

4) Then select the build target in the menu:

5) Go to: "Edit Scheme...":

6) Select "Run" and:

7) Disable the "Debug executable toggle"

8) Click on the combobox that says "auvaltool"-> Select: "Other..." and select the "auval" executable you just copied to /Applications

9) Now select "Run" -> Switch to "Arguments" tab:

10) Instead of -v aufx Ipef Acme, which is dummy data and totally wrong, put -v aufx $PLUG_UNIQUE_ID $PLUG_MFR_ID, i.e.: -v aufx Lapa AHVI

=> FINALLY, run the task again, and...

IT WORKS!

@olilarkin Maybe we can improve the duplicate.py by adding two more arguments to specify set the PLUG_UNIQUE_ID and PLUG_MFR_ID and replace them automatically in resource.h and the Xcode schema config. Maybe I could take a look at it and pull request. Because: If new users start using this project they even might think it doesn't work "at all" when the first thing that happens after clicking "Build" is an "Internal error" :))

[olilarkin]

thanks, there are some updates to the duplicate.py coming in iPlug2, with PLUG_UNIQUE_ID and PLUG_MFR_ID getting randomised on duplication. I didn't know you could get $PLUG_UNIQUE_ID $PLUG_MFR_ID in the auval args list.

[AliceRixte]

I'm sorry, I'm very new to all of this but can I build AU devices on Windows? I couldn't see a corresponding solution on VS17. You can smash my fingers if I'm a bit too bold

[olilarkin]

no. please use the wdl forum, not github issues for questions like this

[olilarkin]

closing this since it's not a bug