Account Locked

The removal of Launchpad from macOS has cost me a huge amount of wasted time. It is quite baffling why Apple's engineering team thought this was necessary. There is no scenario in which Apple's few predefined categories could possibly ever address the long tail of real world application categories and user workflows. This is a point I make in depth below. Also, I am now encountering a bug preventing me from searching for apps by name, even if I could remember the name of my 250+ native and web apps, so I have no other choice but to scroll through over 250 icons to find the app I'm looking for. I honestly do not understand what the rationale was for this change by Apple. Vital functionality that I relied on with minute-to-minute frequency was replaced with a fundamentally broken one that costs me minutes where it previously took seconds to find apps. In fact it should be obvious that predefined app categories could not possibly address real world use cases and and that forcing users into them would break more

Adding just com.apple.Sharing.AirDropUI allowed me to receive an Airdrop from someone other than my own account

Are you able to reproduce and generate a sysdiagnose? Would like to take a look at whats occurring. Attached that to a feedback ticket and include a screen recording, your sandbox Apple Account, physical location and details to what transaction and product you were attempting to test a refund in sandbox with. https://developer.apple.com/bug-reporting/profiles-and-logs/?platform=ios http://feedbackassistant.apple.com Once you file, share the FB# here and we can take a look.

@MikeDMh Thank you for filing a bug report. Your bug has been closed as a duplicate. That's okay as duplicate bugs are used as an indicator of developer interest (so, don't worry, your bug report matters). Looking at the original bug report it remains open and under investigation. Please continue to test your software in release and pre-release versions of system software made available to you through your developer.apple.com account to see if the problem has been resolved. For beta pre-release versions of system software, please see https://developer.apple.com/download/.

Thanks y'all! Ed, I'll try running the system trace tomorrow morning (I'm in New York City, so it's the end of the day for me). Kevin: Everything found was largely addressed in macOS 10.14 (Mojave). Ah! Good to know that my information is kinda out of date :) Unfortunately, comparisons between different systems are extremely tricky due to fundamental design differences.” One of macOS’s fundamental design choices is that its goal is to responsive NOT fast.” In other words, the system’s ability to quickly react to the user’s actions is MORE important than the total time it takes to complete any given operation. In the I/O system, that means restricting I/O memory commitments more than Linux, both to reserve memory for other purposes and to reduce the chance that the system will have to stall waiting for memory to be flushed to disk. Understood! Makes a lot of sense given the common, respective usages of Linux vs. macOS! Are you calling fsync or are you doing fcntl(F_FULLFSYNC)? The second call will be significa

Let me start with the comparison here: Similar performance issues were reported in the past by a former Mercurial maintainer: https://gregoryszorc.com/blog/2018/10/29/global-kernel-locks-in-apfs/. Unfortunately, there are some fairly significant flaws in the analysis there. Picking one of his data points: $ time ./slow-readdir.py -l 12 ~/src/firefox ran 12 walks across 12 processes in 172.209s real 2m52.470s user 1m54.053s sys 23m42.808s Based on his overall article, I believe he thinks that test took ~23m when in fact it took ~3m. That is, the actual test time was: ...in 172.209s -> ~2.52 -> real 2m52.470s In general, that's what real means in most time tests -> how long did this test actually take. In terms of the difference in system time, that appears to have been due to an accounting issue in the kernel. Per the investigation that was done on the bug, this particular test script ended up having multiple threads blocked in the kernel (waiting on work to complete) and the kernel included

The app ID is in the team account. I did have a wildcard app ID, but deleting it didn't fix this. I am using automatic code signing, but how do I know which certificates in Keychain Access are invalid? I've got both certificates and private keys in there. Some Apple Distribution, some say Apple Development, one says Developer ID Application. I don't want to delete anything essential, so please advice which one(s) to delete.

Here's some things to try: login to developer.apple.com and check and see if com.os.hub.mth2 inadvertently was registered in your personal account instead of your developer account. If it was, delete it from your personal account. Login to developer.apple.com and check and see if you have a wildcard app id registered in your account. If you do, delete it. If you're using automatic code signing you can delete the invalid certificates in the Keychain Access app. Xcode will download the correct certificates next time you run a build. If that doesn't help, consider opening a support incident so I can take a look at the settings on your machine. https://developer.apple.com/support/technical/