TIL If you are experiencing poor performance with SwiftUI’s List + ForEach, you can enable the launch argument:

-LogForEachSlowPath YES

https://x.com/kyleswifter/status/1979849200222531959
#SwiftUI #layout #optimization

Me: waiting for Swift Assist
Swift team: “How about Swift… on Android?”
https://www.swift.org/blog/nightly-swift-sdk-for-android/

Apple quietly dropped a few nice App Store updates.

The biggest one — you can finally submit a new version, while another build is still under review. 🙌

Other small but welcome changes:
• Up to 70 custom product pages per app (each with unique keywords).
• Offer codes now work for all IAP types, replacing old promo codes by March 2026.

https://www.macrumors.com/2025/10/29/apple-developer-app-store-updates/
#AppStore

Nice reminder about how .task behaves when it depends on a property that can change — and why adding an id makes all the difference.
https://chris.eidhof.nl/post/swiftui-task-identity/
#SwiftUI

Recently had to animate a SwiftUI sheet resizing itself — sounds like a super basic thing, but the actual solution was anything but obvious.

If you ever need an animatable, auto-sized sheet, this write-up breaks down an approach. Might save you a couple of hours (and some sanity).

https://clive819.github.io/posts/animatable-auto-sized-to-fit-swiftui-sheet/
#SwiftUI #Layout

Every time Apple ships a “simpler” sync API, I hope this is the one where I won’t have to think too much. CKSyncEngine almost looks like it… until you read Christian Selig’s article.

It’s not a tutorial — it’s a list of things that will quietly break later if you trust the magic:

• saves resolve conflicts, deletes don’t;
• enums in synced models are a trap;
• engine state must be persisted;
• quota errors are still your problem.

The API is better, but architectural responsibility didn’t go anywhere. So it’s worth reading if you’re considering CKSyncEngine.

https://christianselig.com/2026/01/cksyncengine/

#iOS #CloudKit

As multi-module setups become more common, it helps to be precise about how imports work.

import Foo

• Swift 5: implicitly a public import (see public import Foo below), unless InternalImportsByDefault is explicitly enabled.
• Swift 6: a regular internal import — visible only inside the module and does not affect the public interface.

public import Foo

• Allows Foo types to be used in public / open API.
• Downstream modules gain access to Foo, but still have to explicitly write import Foo themselves.

@_exported import Foo

• Foo types become automatically available to any module importing yours.
• Useful for facade modules.

https://alexanderweiss.dev/blog/2026-01-16-exported-import-vs-public-import
#swift

Probably everyone is already tired of reading about Clawdbot. Too many posts, too much noise.
But this story is on a different level. Honestly, it reads like a Netflix script.

The short version:
• Anthropic complained about the Clawdbot name.
• The project rushed a rename.
• During that window, the account was taken over.
• Under the old name, fake tokens were pushed to the market.
• Within hours, FOMO kicked in on Solana and the token briefly hit a ~$16M market cap. 🫠

Not a bug — pure timing.

https://dev.to/sivarampg/from-clawdbot-to-moltbot-how-a-cd-crypto-scammers-and-10-seconds-of-chaos-took-down-the-4eck

#security #Clawdbot

TIL: UIScreenShotServiceDelegate exists since iOS 13. Found it only today. Somehow missed it for years.

It lets your app provide a custom Full Page representation — basically a PDF that the system uses when the user chooses that mode. Safari uses it for long pages. Apple Maps uses it to export a clean map, without UI chrome.

Feels like one of those UIKit features that quietly shipped and never got attention.