We've noticed that our app is now immediately crashing on background on iOS 14 Beta 3 with the 0xdead10cc termination reason. This indicates (as per Technical Note TN2151 - https://developer.apple.com/library/archive/technotes/tn2151/_index.html) that the app held on to a file lock or sqlite database lock during suspension. However this crash didn't occur at all prior to beta 3. Did something change in iOS that might cause this? Stricter enforcement? This is a hard crash for us to debug with little than the technical note to go on and potentially an unknown change in iOS itself.

Hey guys! Was wondering if you guys knew where the macOS icons in BigSur are stored. I checked in the following places and pretty much the whole /System/Library folder: /System/Library/CoreServices/CoreTypes.bundle/Contents/Resources -- where they usually are Finder app in /System/Library/CoreServices/Finder.app Dock app in that same directory CoreTypes.bundle in /System/Volumes/<whatever your startup disk is named>/System/Library/CoreServices/CoreTypes.bundle/Contents/ I need those icons for stuff. Please let me know if you guys know where they are!

How does Search kit work for different languages? Does the text content in SKDoument need to match the user's language, or is there maybe a pre step where content is analysed and language detected by api. For instance, can a chinese user search english documents, or will there need to be a separate translation handled as well by us developers, to turned the document into text, or translating the query of the Chinese user to English?

setting CFProcessPath is essential when launching a java-based app which takes drag and drop events. Can anybody tell me where this is documented? It seems to be folklore at the moment.

I have an application that upon installation, registers a custom URL protocol (scheme) like foo:// using the lsregister command line tool. Recently I noticed that the custom URL protocol is missing after an upgrade of macOS (Catalina to Big Sur). It appears that the upgrade de-registers the custom URL protocol while my application is still installed as it was before the macOS upgrade.Yet, any application functionality depending on its custom URL protocol is broken. The only workaround seems to reinstall my application, or at minimum re-register the custom URL protocol manually. Is this expected behavior for macOS upgrades? Do applications need to re-register any custom URL protocol again after a macOS upgrade? Why are these not retained as one would expect?

With Xcode 12 the following lines of code had been working fine :      CFRunLoopSourceRef runloop = CFMessagePortCreateRunLoopSource(kCFAllocatorDefault, this->m_localPort, 0);     CFRunLoopAddSource(CFRunLoopGetCurrent(), runloop, kCFRunLoopCommonModes);     CFRunLoopRun(); Xcode 13 is basically causing this to crash at CFRunLoopRun with the following error : [CFData release]: message sent to deallocated instance 0x281013cf0 It looks like something got released earlier than it should have. This works fine with Xcode 12 though. I am assuming this should be a bug, but is there anything I can do to verify this or pin point what exactly is wrong.

I created a custom file type for my app as a package. However when I run the app and try to open a file it does not recognize it as the custom file type, but instead as a regular folder. I haven't changed my settings since I first setup the custom type, and only some of these files in Finder are showing properly. Do I need to do something in Xcode to change the rest of the files in Finder?

Hi, I'm the developer of a macOS application named Hopper Disassembler. I have updated my application so that it works properly under macOS Monterey. But I'm getting a warning when I first launch the application: "Hopper Disassembler needs to be updated. This app will not work with future versions of macOS..." Unfortunately, the "Learn More…" button does nothing, and I don't see any relevant message in the Console application. The application is a universal binary, containing both Apple Silicon and Intel 64 bit architectures. How can one find why this warning is triggered? Thank you!

I'm working on a full browser for a year and half during my free time and I'm quite ready for launch, the app is currently on TestFlight and tested by some friends and relatives. I plan to make the app publicly available for testing, but only after the app is basically ready. What I miss is the default browser implementation. I already prepared my app as described in https://developer.apple.com/documentation/xcode/preparing-your-app-to-be-the-default-browser-or-email-client and sent 3 mails to default-browser-requests at apple.com containing the account's email, team ID and app name. The first one was sent in August 2021 (4 months ago), second one in October and third one in December. I never got a reply. I also contacted Apple Devs Support and at least they told me they sent an email to the team in charge of these requests, but I waited for a month and still I don't have an entitlement. Anyone with a similar experience? Is there some other support page or email where can I ask for information?

I have a persistent "crash" with at least one of my apps, which appears to be a case of the app either quitting or being force-quit without generating a crash log. The app doesn't subscribe to any sudden termination compatibility or similar. I have a good friend who is a developer who is able to reproduce the issue within minutes, so I've captured a trove of information from him including a complete sysdiagnose. Unfortunately nothing is jumping out at me, and the only things that show up that seem like they might be related are keys like ApplicationWouldBeTerminatedByTAL and NSCanQuitQuietlyAndSafelyKey. I am kind of grasping at straws and would welcome any inspiration anybody can share. What is TAL and is it something the system could be imposing on my app? If there are circumstances where macOS will preemptively terminate a running app, what are they, and how can I figure out which one is causing the quits in these situatoins? I'd love to be able to reproduce the behavior on my own Mac. If it's something I can prevent, great, if it's not, it would be good to know how to distinguish it from a regular crash for reporting purposes. Thanks for any help!

Hi, I am wondering if the section a) Mac OS encodings for script code 0, smRoman miss Japanese at: http://unicode.org/Public/MAPPINGS/VENDORS/APPLE/Readme.txt Same thing here: https://developer.apple.com/documentation/coreservices/1399980-afp_text_encodings There is no mention about Shift-JIS when the platformID is 1, platEncID is 0 and the langage is 11 :  I am asking the question because I have this font (I do not own the font. It is purely a demonstration): https://mega.nz/file/S9ERDRpQ#bcPhS06kv-D5jt64aTNDbZVd6gZr6ZfJDYT91yYsoWk The font has this sfnt name:     <namerecord nameID="1" platformID="1" platEncID="0" langID="0xb">       FjÉCÅ[É}310     </namerecord> If I use mac_roman to decode this font name (which seems to be the choice when by default), I will not get the right result, but if I use the encoding mac Shift-JIS, I get Fjイーマ310. If my question is not clear, don't hesitate to get back to me PS: Sorry, I did not know what I should wrote in the tags section