UTI stands for “Uniform Type Identifiers”.
It’s like the definition of a file type tying together files extensions, mime types and higher level UTIs. In iOS (and macOS also I guess) you have to provide UTI(s) to initialize the
UIDocumentMenuViewControllerclass, also known as the “iOS Document Picker”. This list will tell the system which type of files your Document Picker will be allowed to open.
This is all good and well unless you don’t know which UTI to use for the file type your looking for.
I was trying to import pem certificates into one of my apps and didn’t know which UTI to use for this task. Fear not, fair developer, Apple said ! Head to our official list of System Declared Uniform Type Identifiers.
Of course, no declared UTI covered my use case. Or so I thought …
Having wrestled with this issue for the better part of the day I have at last found this very useful site: UTI type browser.
It’s the UTI list that Apple should have provided. There are much more types available than the one listed in the official Apple documentation. Including the one I needed:
App Transport Security (ATS), introduced in iOS 9 and OS X v10.11, improves user security and privacy by requiring apps to use secure network connections over HTTPS. At WWDC 2016 we announced that apps submitted to the App Store will be required to support ATS at the end of the year. To give you additional time to prepare, this deadline has been extended and we will provide another update when a new deadline is confirmed.
This is disappointing for the developers who had put in the effort necessary to make their apps comply with ATS. However, I suspect that Apple realized that there are just too many edge cases to really enforce this rule as is.
Mark Gurman reporting for Bloomberg:
Mac fans shouldn’t hold their breath for radical new designs in 2017 though. Instead, the company is preparing modest updates: USB-C ports and a new Advanced Micro Devices Inc. graphics processor for the iMac, and minor bumps in processing power for the 12-inch MacBook and MacBook Pro. Cue the outrage.
Well, that was quick.
Tim Cook in an internal memo reported by Matthew Panzarino at TechCrunch:
The desktop is very strategic for us. It’s unique compared to the notebook because you can pack a lot more performance in a desktop — the largest screens, the most memory and storage, a greater variety of I/O, and fastest performance. So there are many different reasons why desktops are really important, and in some cases critical, to people.
The current generation iMac is the best desktop we have ever made and its beautiful Retina 5K display is the best desktop display in the world.
Some folks in the media have raised the question about whether we’re committed to desktops. If there’s any doubt about that with our teams, let me be very clear: we have great desktops in our roadmap. Nobody should worry about that.
Was it so hard, Apple ?
Just acknowledging that your desktop line is still alive ? In my opinion, a lot of virtual ink would have been saved about the new MacBook Pros if they had said it earlier.
Now, this doesn’t mean that we (“pro” users, whatever that means) are out of the woods the just yet. It may just be an iMac speed bump in the spring for all we know. But still, it feels much better than the void we’ve been living in for a long time.
On a related note, I thought a bit more about the end of the Apple branded monitors: I now think that it is sign that we will never see again (in the foreseable future at least) a screenless Apple desktop. It’s one thing for Apple to send its customers to LG for a secondary display used with a laptop. It a completly different one to release a brand new machine that cannot be used without an add-on sold by another company.
The Mac Pro and the Mac Mini won’t probably ever be updated again in their current form. Brace yourself for some kind of iMac Pro.
I just wanted to take advantage of one of the coolest looking feature of watchOS 3 : the auto unlocking of your mac.
Well, the first step is to enable 2 factors authentification for your iCloud account. My account was already on the 2 steps authorization scheme so that should be a piece of cake, right ?
Wrong, so f***ing wrong.
You first have to downgrade your account to go back to the classic protection by security questions. By doing so, macOS asked me to create a new user because I used my iCloud account to log into my mac and for some reason that was not possible anymore.
Okay … I guess ?
At this point I had no real choice anyway so let’s go ahead : create a new password and that’s it, you have your new user identical to the previous one (or so it seems, keep reading …).
Then upgrade your iCloud account to 2 factors auth : Oh boy ! There’s nothing that makes me like doing my taxes more than a good old fashioned self imposed Apple nightmare …
When you activate 2 factors auth you have to validate each device you use (iPhones, iPads, Macs) with a second factor. This second factor being (it’s the only option) a prompt that appears on one of your trusted devices. The problem being that each of my devices were then asking for a validation and that none of them was showing me the said prompt.
So what can you do ? After several reboots, logout / login again cycles … you give up. That’s for sure what I did. I reverted my iCloud account back to security by security questions (because of course the 2 steps verification scheme is not available anymore once you have upgraded to 2 factors auth).
And now, the kicker: remember my macOS account that seemed OK. Well it was not. The session password was now de-synchronized from the FileVault password that I have to provide at each reboot to decrypt my hard-drive. So each time I rebooted I had to enter the FileVault rescue key.
Had I not set a FileVault rescue key (which would have been stupid sure, but what if you’ve lost it ?) trying to unlock my Apple Mac with my Apple Watch through my Apple iCloud account would have nixed all my data.
Let that sink in.
So thanks Apple and next time would it be possible to … No, you know what, nevermind. It’s on me.
Next time I won’t even try.
subscribe via RSS