search

AudioKit / AUv3-Example-App

Full App: iOS Standalone and AUv3 Plugin Example. Work in Progress.
MIT License
257 stars 44 forks source link

Silly BundleIdentifier question #5

Open amrmarzouk opened 3 years ago

amrmarzouk commented 3 years ago

My apologies for the silly question, total noob here.

  1. pod install from the folder
  2. Open the AU Plugin.xcworkspace

I know I need to put in Unique Bundle Identifiers but should I put in five different ones (three for the three targets under the AU Plugin, and two under AudioKit For IOS.xcodeproj) ?

I truly appreciate it.

aure commented 3 years ago

Sorry, I misunderstood your question.

emurray2 commented 2 years ago

My apologies for the silly question, total noob here.

1. pod install from the folder

2. Open the AU Plugin.xcworkspace

I know I need to put in Unique Bundle Identifiers but should I put in five different ones (three for the three targets under the AU Plugin, and two under AudioKit For IOS.xcodeproj) ?

I truly appreciate it.

The AudioKit For IOS.xcodeproj are just a way to import all the AudioKit dependencies. This has changed now to Swift Package Manager which makes things more simple. If you use the AudioKit Swift Package in your project, you won't need to worry about bundle id's for AudioKit. The reason they are included here is so the frameworks can be identified by their bundle id. Changing these bundle id's is not necessary.

For the AU Plugin, the important bundle id is the one for the app: io.audiokit.pluginExample. This is how Apple identifies your app on the App Store. The only requirement with an AUv3 is that the bundle id for the Audio Unit (AU Plugin AU in this case) needs to be prefixed with the App's bundle id. This is why the bundle id for the Audio Unit is: io.audiokit.pluginExample.pluginExampleAU.