Archive for May 20, 2019

Monday, May 20, 2019

Google Pulls Huawei’s Android License

T.C. Sottek (Hacker News 3):

Following the US crackdown on Chinese technology companies, Google has cut off Huawei’s Android license, dealing a huge blow to the besieged phonemaker. Reuters first reported the news, and The Verge subsequently confirmed Google’s suspension of business with Huawei with a source familiar with the matter.


Speaking to Reuters, a Google spokesperson confirmed that “Google Play and the security protections from Google Play Protect will continue to function on existing Huawei devices.” So while existing Huawei phones around the world won’t be immediately impacted by the decision, the future of updates for those phones as well as any new phones Huawei would produce remains in question.

Horace Dediu:

Huawei is nearly the world’s biggest smartphone vendor. Their exclusion from licensed Android and fork away from Google is the biggest news in smartphones since, well, Android.

Update (2019-05-21): Ben Thompson:

Huawei’s preparation for this moment likely started last year when a similar ban was placed on the sale of American component to ZTE[…]

Update (2019-05-22): Tom Warren (tweet, Hacker News):

Chip designer ARM has suspended business with Huawei, threatening the Chinese company’s ability to create its own chips. BBC News reports that ARM employees have been instructed to halt “all active contracts, support entitlements, and any pending engagements” with Huawei due to the US trade ban. The US has banned any US companies from doing business with the Chinese telecom giant without permission from the American government, but ARM is based in the UK and owned by the Japanese SoftBank group.

ARM is concerned it is affected by the US ban, with an internal memo reportedly revealing that its chip designs include “US origin technology.” ARM develops some processor designs in Austin, Texas and San Jose, California, which could place it under the US restrictions.

Timery for Toggl

John Voorhees:

Time tracking helps me weigh the value of the time I spend on every project, identify inefficiencies in the way I work, and acts as an early warning system to avoid burnout.


I’m still using Toggl in a Fluid browser on my Mac, but since last summer, I’ve been using the beta of Joe Hribar’s Timery on iOS and loving it. In fact, Timery is so good that even when I’m at my Mac, I find myself turning to it to start and stop timers instead of the web app.


Timery has helped me make peace with time tracking. Where years ago, it was a tedious process of recording detailed notes by hand, now it’s a simple, streamlined process. Instead of being an interruption and something that fed an invoicing system, time tracking has become a tool that helps me work better than before.

I have been using Hours, which can optionally work completely on-device, without a Web service.

Previously: Timing 2 for Mac.

Beware iCloud Video Syncing

Tyler Hall (tweet):

Get home, back on WiFi, start uploading everything to iCloud and Google Photos. After an hour or two everything’s synced.

Problem: All videos, of any length, stutter, stall, and skip frames in both (macOS) and Google Photos on every Mac I try.


This is a core competency of iOS that should never, ever fucking break for any reason. Apple markets iPhone’s camera as a top selling point – if not THE selling point.

Lucky for me, I’m tech savvy enough to know about Image buried inside macOS’s Utilities folder. So I give it one last try using that to transfer the corrupted videos manually off my phone and into and Google Photos.

It works. My memories are safe.

Wow, I guess I need to check all our family videos now. It’s possible I’ve been backing up damaged versions, and the good copies would be lost if I pruned our iCloud Photo Library to save space. Hopefully they weren’t already lost when my wife upgraded her iPhone last year. This is not the sort of thing that can be recovered from a backup because iOS cloud backups don’t include the contents of the Photos library if you’re using cloud syncing.


Update (2019-07-08): Tyler Hall:

That’s right. I dragged photos from Finder into an empty album in and watched as they were imported and then subsequently deleted.

I did this five times with the same result before I finally thought to record the whole fiasco for posterity. No matter whether I dragged from Finder or used the “Import…” menu item - same thing.

The State of Apple’s Developer Documentation

Scott Anguish:

It appears that most of the old iOS conceptual documents have been moved to the documentation archive and are now unsupported.

Is there really no iOS Text Programming concepts? Or are the indexes just that bad?

That is more than a decade of work by dozens, just being abandoned.

I can’t even grasp how that’s any solution.

If this is the case every single iOS developer should be screaming from the rafters. It’s by far the stupidest move I’ve seen in a decade.

You can’t write apps without authoritative docs.

It’s bad enough the reference doc has reached the point it has.

It’s surprising how much of the documentation is marked as legacy, archived, not up-to-date, or was never written in the first place. At first I thought this was because of some sort of internal transition, but it’s been going on for years now and does not seem to be getting any better.

Steve Tibbett:

As far as I can tell, this is the only documentation on IAP receipt validation. This is part of a current system that’s making Apple billions of dollars. There are errors in it, and it’s “no longer being updated”.

Martin Pilkington:

Fun fact: when I was looking up docs for Help Books for my Appreciating AppKit post, one of the few Mac features already supported in Marzipan, it took ages to find as they’re only available in the documentation archive

Matt Stevens:

If you’re struggling to find an Apple developer document you know exists, it’s not just you.’s robots.txt disallows /library/archive/, where all of the old docs now live. Apple’s own “Search Documentation Archive”…doesn’t search the archive.


Update (2019-05-21): Adam Maxwell:

I remember the good old days when people were annoyed that you couldn’t figure out Cocoa bindings without the stuff mmalc posted on his personal website. That was nothing compared to when the doc browser turned into a lousy webpage instead of Cocoa views and Search Kit.

Randy Scovil:

I’m wondering how much has really disappeared. I used to point students there all the time for source code examples and now I find most any search for those comes up empty. Que?

Jonathan Fischer:

For what it’s worth, DuckDuckGo seems to be ignoring that robots.txt entry for /library/archive. I usually find what I’m looking for without much trouble:

Francisco Tolmasky:

Died Apple just not document AppKit anymore? I can’t find anything about NSWindowTab. Is all information just in like WWDC videos?

See also: Hacker News.


Sad but true. 10 years ago when I were starting to learn iOS development it was one of the best documentations I’ve ever worked with. And now it’s more like Microsoft’s in it’s dark age.

Update (2019-05-22): macshome:

One of my biggest issues with the new docs page is discoverability. And yes, I’ve filed radars on it.

Kyle Howells:

This is now my number one WWDC wishlist item.

Anything else is a bonus, but Apple’s documentation has fallen so far the knowledge about how the platform works is now being buried in archived documents, old WWDC videos and release notes.

Update (2019-05-28): Kyle Howells:

Apple’s developer documentation doesn’t show what class the method I’m looking at is for anywhere on the page.

Update (2019-05-30): Scott Anguish:

From comments on your post today “Apple’s docs turned downhill fast when they switched to automatically generating docs instead of using human-written, structured, and curated materials.”

Except that’s not what happened. It’s all human-written, structured, and curated.