TIL: standalone app and AU behavior change if you have AUV3 enabled

#1

i spent almost an entire day trying to debug some auvaltool issues before i finally figured this out. i’m posting this with the hope it helps someone else out

au + standalone
if you have au and standalone enabled (but not auv3) then the component built from the au build is what logic / auvaltool will try to use.

au + auv3
if you have au and auv3 without standalone the behavior is identical to above - your component is what logic / auvaltool will try to use.

au + auv3 + standalone
if you have au and auv3 and standalone enabled and you happen to run the standalone build then the auv3 appex is what logic / auvaltool will try to us (so if you don’t run the standalone build the appex won’t get registered). if you don’t run the standalone app then your au component is what is used. even more confusing, if you run auvaltool with the -comp option it’ll use the au component.

now, back to debugging my auv3 sandbox issues.

3 Likes