Hi, I don't think you'll find much. Both error codes, 14090 and 9, mean 'authentication failed'. I'm no expert, but the man pages for directory services and pam might be of interest. However, with the wrong password, this is the expected behaviour. Try with a non existing username to see the difference, you should get like -14167 and 13, if that is correct, man dscl man pam are definitely of interest for you.

Hi, I have limited knowledge here, but I'v been working on Core Audio recently so: from my understanding, offline rendering outputs to a file, i.e. you process offline your audio, it goes super fast, to then play the file. Now, if you _really_want to hear the audio, disable manual rendering.

The message from Review + the Guidelines are very, very clear, I'm not here to bother you, but I when you ask if a 'warning message at the start is enough', it makes it seem like you didn't read what they said. What you have to do is to do as they say, because Apps on the AppStore are for everyone. Or you can see if the 'Enterprise Program' can work for you, because that program is made exactly for when only your staff should have the app, and no AppStore needed: https://developer.apple.com/programs/enterprise/

Hi, such a lovely issue "we grown so much we hit the limit!", félicitations! About the 'enterprise program': it can be a separate account, has to be if you already are in the non-enterprise program; it still has 100 slots for debugging? Specifically, you can't use that for the AppStore, picture that program made for putting special apps for all of an 100+ staff.. And stricto senso your questions: No you won't lose that ability (still present on your current, distinct, dev account), but yes it is strictly internal with quite some requirements from Apple to be eligible. From my understanding, this is the way to go, different accounts for different teams. I prefer to answer questions rather than unasked advice, but, when/if you go with another dev account, try to keep separated distribution and testing, and provide company email accounts for this purpose, like this you maintain control.

Did you sanity-check in System Settings if it's toggled on? What happens if you export the iPhone app 'direct release' and then launch the .ipa installer from the mac? What UTType is it? Do you happen to have another, maybe older, extension somewhere in your mac, including inside Derived Data or an .xcarchive? What happens if you do, in terminal? uttype --extension xxx --verbose xxx your uttype without the dot Is that correctly the uttype expected or is there a rogue one as well?

Apple didn't break anything, let's not forget that by definition we are dealing with unsupported types. I have similar issues as you, except me it works perfectly on the simulator, and not on my iphone 12, and I have been extensively trying out things. But before being at that issue, I had other ones, including this on macOS, where a quicklook issue happened to a user that shortly after happened to me as well, and I could pinpoint what it was: I had installed an app right before encountering the issue, an app the user had as well, and that app changed the UTI of the file extension. So for me, I just had to add that UTI to my extension's QLSupportedContentTypes. I know that is not your issue, however it might provide insight: in order for the other app to 'hijack' the UTI, it actually used 'Imported type' and not 'exported type', so you can try this instead?: Additionally, checking your app's info.plist, I see you declare 'Fuji Compressed RAW Image' as having two UTIs. From my understanding, the way to do that is to declare it twice, with a single UTI each time. Regarding the versions issues on macOS, do you understand loud and clear how QuickLook almost stubbornly looks for the extensions at the path it found it the first time? i.e. if you built and launched from /Applications, and then you build again and launch from /Derived-Datas, it's still going to fetch it from /Applications and if it has been deleted, it might get confused and act like there is no extension? Also, if you need to debug the actual extension, what you have to do is run the extension's from Xcode, but not with 'QuickLookSimulator' but rather with "Finder', there you'll get the debug messages. You might have to use osLog and set each variable to public in the string, if it comes out as private. If you fixed your issue, please tell, that's where I am at right now