A long time Mac developer that also Always Needs a Hug. Insighting your binaries. An automatous Reality Marble. Cotidie Morimur
Jun 8, 2022 • 5 tweets • 2 min read
Despite what this tweet implies, this “new iOS update” has not been released and won’t be available until the fall. Falling back to the far more insecure, spoofable, and hijackable SMS is *not* the answer.
iOS 16 also comes with a new Safety Check feature that allows you to immediately purge all auth tokens if you’re in an abusive relationship and/or suspect stalking.
Here’s Johnathan with what’s new in notarization for Max apps. developer.apple.com/wwdc22/10109
Main new news is that notarization submissions via altool and via the app distribution workflow for non-Mac App Store apps in Xcode 13.x and earlier are deprecated (and slower) and are walking into the sunset in Fall of *2023*
Jun 7, 2022 • 4 tweets • 1 min read
Finally! Been waiting for this. It’s the power of opaque types that allows you to muss about in the core guts without making existing users incompatible.
When you vend a concrete struct dependent on memory layout via an API, you will be punished by the struct.
All hail the Opaque One!
Feb 17, 2022 • 10 tweets • 3 min read
Force Unit Access, what this “flush to permanent storage, not disk cache”command is called, is ignored by the majority of drive types (either through lying firmware or a bridge).
It’s not enabled by default in most kernels (Linux, Windows) due to synchronous writes being slow.
Force Unit Access is also a deep layering violation as the OS tries to skip the drive controller firmware’s write optimization and directly modify permanent storage.
Jun 7, 2021 • 6 tweets • 2 min read
I’d been meaning to discuss the features in the altool command line tool used for notarization that were new to Xcode 12.5, and it seems like I’ve smacked against a deadline.
So here’s a thread of some new stuff in Xcode 12.5’s altool 4.047.1207 for use with notarization et fam
The first reminder, if you use:
With any altool invocation, you do NOT need to specify --username, as it’s embedded in the Keychain item.
Jun 6, 2021 • 4 tweets • 2 min read
Sometimes I like to recommend people watch one thing after another to note the juxtapositions, contrasts, or that headcanon puts two stories in the same universe.
For example, watch Stargate SG-1 S3E21, Crystal Skull, then immediately watch with Indiana Jones 4. Same story.
This time, I’d recommend watching the anime GATE (tv.apple.com/us/show/gate/u…) followed by 86 (tv.apple.com/us/show/86-eig…). GATE has an extremely nationalistic plot that deifies the Japan Self-Defense Forces (JSDF) while 86 discusses racism & war and broaches Unit 731.
Apr 1, 2020 • 14 tweets • 6 min read
This is a tweetstorm discussing the new features of altool 4.01 (included with Xcode 11.4), changes to the notarization documentation, and a change to notary service requirements, with the far majority coming directly from user requests
We’ll start with altool 4.01.
1/13
If you used `xcrun altool --store-password-in-keychain-item` you no longer have to supply the --username option when authenticating with --password “@keychain:<item name>” as the username is now grabbed from the keychain item.
This should make scripting easier for organizations.
Jul 3, 2019 • 9 tweets • 3 min read
Xcode 11.0b3 includes a major update to altool (used for notarization), altool 4.0, with some awesome new features. I’d like to discuss some of the new feature here in this thread.
Questions and other feedback are welcome! 1/9(?)
First, altool actually has a man page now (man altool) accessible after new Xcode 11b3 is installed.
altool supports a new --verbose argument that’s my type of verbose (it’s overly verbose to the MAX!) that’s useful in debugging issues, filing radars, and watching progress.
