This seems like an odd list to me. I think 1, 2, 3 and 17 are very valid. While Apple has been doing a better job documenting new features since around iOS 10, it's still frustrating knowing that there is so much old stuff that lacks good documentation.
5 is more of a niche complaint but I think it is still important. It's annoying when I have to recreate things that already exist in many of Apple's own apps because often it "feels" different to the native implementation. Things like the custom view controller transition when peeking/popping with 3D touch, photo galleries, the "drawer" container view controllers, the fancy action sheets in Music.app, etc would be nice IMO because it allows your app to feel more native.
7 will be solved soonTM, although it doesn't look like the Swift team will choose promises over other concurrency models.
8, 9: I haven't encountered any async functions that don't document which queue they call a callback on, nor any errors that don't also have a localised description so I can't comment on this. Perhaps these are more "XXX framework isn't in a good place" complaints???
For me it is more annoying when the documentation doesn't say what can cause an error to be thrown or what kinds of errors can be thrown.
10: It can be annoying that you can't catch exceptions in Swift but most of the time these are due to mistakes that you have made when working with frameworks and that you can't reasonably recover from, like inserting/deleting rows that don't exist, calling functions with nonsensical combinations of parameters, etc.
12: If you crash from nil unwrap failures then you need to go back and read the foundational Swift books that Apple put on the iBooks store. If you use 3rd party frameworks that crash your app then change them or, if they are open source, fix them. ^REEEEEEEEEEEE
13: This is subjective and I won't comment lest I summon cyniccynic :P
14: The crashing wouldn't happen if you unwrapped your optionals properly. Dealing with different floating point types can be annoying though.
15: It is sad that they don't support Vulkan, but this doesn't affect the majority of apps. Also I think that Metal came first so
16: This subjective also. I know a lot of people who don't like reactive programming at all. It's just not how Apple designed Cocoa Touch to be used IMO.