Since iOS 18 has a lot of “how did that take 18 releases”, I’ll throw an api quark that has driven me nuts since the first SDK: UIViewController.dismiss behaves differently based on the state of presentation. It dismisses self if it doesn’t have a presented VC, but if it does it dismisses that VC. And if it is *currently* dismissing a presented VC, presentedViewController will be non nil but it will dismiss self.
This api is bad and should be replaced. And it should have been 10 years ago.
David Beck :xcode: /
npub1x3…gnlv0
2024-06-22 21:00:07
Author Public Key
npub1x3l9d6qc25r7q4plwzhgfwuhea057gadg7pd4tx5x7k98g23jc6qagnlv0Published at
2024-06-22 21:00:07Event JSON
{
"id": "b3508fe1a5759f7b99c516f06f7c740902e84a4cc2840613495afcafb4ee969a",
"pubkey": "347e56e8185507e0543f70ae84bb97cf5f4f23ad4782daacd437ac53a1519634",
"created_at": 1719090007,
"kind": 1,
"tags": [
[
"proxy",
"https://tnku.co/users/david/statuses/112662282724458681",
"activitypub"
]
],
"content": "Since iOS 18 has a lot of “how did that take 18 releases”, I’ll throw an api quark that has driven me nuts since the first SDK: UIViewController.dismiss behaves differently based on the state of presentation. It dismisses self if it doesn’t have a presented VC, but if it does it dismisses that VC. And if it is *currently* dismissing a presented VC, presentedViewController will be non nil but it will dismiss self.\n\nThis api is bad and should be replaced. And it should have been 10 years ago.",
"sig": "fcb0ded63fd0b3933af65a56a847ef9b7f5004bac26f532336140f4445ef90483a7da4c49f6cc5586864d83e0a3e7cee4fd2e0a18da99c573345545f66957c3e"
}