daw ( logic ) component problem
- 
 @yall yes i compiled plugin on m1 and xcode 10.3 
- 
 @arminh but how can I make my plugins compatible if I don't have a mac m1? 
- 
 @yall you don't need m1 to build plugins for this silicon. M1 use Rosseta 2 to handle intel based apps. 
- 
 @arminh so i don't understand my problem ... my vst works under catalina but not Bigsur. I will try again with mojave and xcode above version 10.1 to start. the notarization has been validated. I have a doubt about the id of the vst bundle which is different from that of the pkg but I see no solution at my level 
- 
 I come back here to try to understand. I therefore uploaded my mac to mojave. and xcode 10.3. l exports of my plugin are going successfully. .vst3 .vst. component I sign my plugin.ok I sign my pkg. okay I notarize the pkg. okay I receive the apple validation email ... ok I staple the pkg. okay I check the notarization ok the plugin is detected as validated in "logic". my beta tester cannot find my plugin in his list. Really, I do not understand. apple m1 bigsure so i tried it another way. notarize only the pkg, it doesn't work. notarize a .zip which contains the pkg. it still does not work. sending the .au or .vst3 file directly does not work. to tell the truth, at this stage I have no idea what to do. 
- 
 @yall Have they tried any other DAW? 
- 
 @d-healey yes ableton also. but still the same. 
- 
 
- 
 @d-healey I just read that. so i would have to export with xcode 12 to be able to output an any mac version? 
- 
 so i would have to export with xcode 12 to be able to output an any mac version? Why Xcode 12? 
- 
 @d-healey I just read that the universal binary export function was only available from xcode12.2. afterwards I read a little stupidly because I have the brain broken down. I am already happy to have accomplished my notarization  
- 
 @yall Maybe that's not the solution then since others here seem to have it working with BigSur using xcode 10... Ask your beta tester to try another DAW, like Reaper. 
- 
 @d-healey i am giving it a try right now with fl studio. I just saw in my xcode project, in the target, mac os 10.6 etaot selected? can that change something? 
- 
 @d-healey so good news, on the mac m1 and with fl studio my plugin opens successfully. So I conclude that logic is shit software ^^ seriously I do not understand what is wrong with this daw. fl studio reads, the. component and .vst3 without problem 
