Viktor Rutberg

The app I have been working on as a solo developer for the past 2½ years has recently been featured in the App Stores of South America, Southeast Asia, and now Canada! Woo!

https://apps.apple.com/us/story/id1879808653

How are people writing their UI tests for iOS these days? I've used KIF earlier with great results, running UI tests in-process greatly simplifies things. It feels dated through, and bringing in KIF now would feel like a risk. Any alternatives? #iosdev #ios

Is it just me, or has the quality in Swift/Xcode/Simulator had a terrible streak lately?

• Emojis broken on iOS simulator 26.3 runtimes
• Release builds broken in Swift 6.3
• Previews are broken on macOS 26.4

Here I am, a simple, humble and innocent man working as an iOS developer. Taking the time to patiently and carefully architect my app to leverage the power and effectiveness of SwiftUI previews to build my app faster.

And what happens? Apple makes SwiftUI previews unusable on macOS 26.4. 😡

PSA: There’s seems to be a regression in the Swift 6.3. compiler, causing crashes when running optimized code on device.

I stumbled upon it while testing this week’s app update, reverted to building with Xcode 26.3 for now.

Links:

https://github.com/swiftlang/swift/issues/87481
https://github.com/firebase/firebase-ios-sdk/issues/15974

Ugh, my app has been stuck in App Review for over a week now because the reviewer can’t find the Delete Account feature, even though it’s included in ‘Notes for App Review’, *and* I’ve replied to their two rejections telling them where to find this feature in the app.

@Cyberbeni@mastodon.art Of course, you are right! Initially I, somewhat naïvely, thought those two systems were more similar than what they are.

The sentiment around Combine tends to be that it’s stagnant, soon-to-be (or even de facto) deprecated, and that one should move away from it ASAP. But maybe that’s not completely right, if it’s successor seemingly doesn’t support all the same use cases.

I’ve been putting off migrating my Combine stuff to AsyncStream, simply because I know how the Combine stuff works (and it works well), but I thought I would start now.

I’m about to replace a CurrentValueSubject having multiple downstream subscribers with an AsyncStream. Am I missing something obvious, or is this difficult with AsyncStreams?

#iosdev #swift

Whisper these words to an iOS developer in their sleep and they’ll start having nightmares:

"SwiftUI, UIViewControllerRepresentable, safe area, UINavigationController, contentInsetAdjustmentBehavior, UIScrollView”

#iosdev

As a solo developer it can be hard to justify taking the time to deep dive into a bug report, but often times I feel like it’s still worth it. If just one user reported the bug, how many users experienced it without reporting it?

Even if I don’t manage to fix the bug, maybe I realize that I need more logging to fix it in the future, or I learn something which will help me fix it the next time a similar issue appears.

It seems like I finally found a working solution after a lot of back and forth with Codex. It just gave me different solutions that were broken in one way or another, before I eventually gave up and came up with a solution for myself (yay! AI! 😒).

1. Set tableView.contentInset to view.safeAreaInset in viewSafeAreaInsetsDidChange
2. Set tableView.contentOffset once in viewDidLayoutSubviews

Setting contentInsetAdjustmentBehavior = .never fixes the tap issue, but it also puts the table view content under the top safe area (under the navbar). So now I’m looking into implementing this manually instead. Sigh!

Trying to fix a bug which seems to be caused by this combination of factors:

* I’m presenting a `UIViewController` in a SwiftUI sheet using `UIViewControllerRepresentable`
* To get a navbar, the `UIViewControllerRepresentable` wraps the view controller in a UINavigationController
* The view controller has a `UITableView` with `contentInsetAdjustmentBehavior = .automatic`

The view looks correct when presented, but taps are offset by the height of the safe area, which is… not ideal.

@overenginerd@mastodon.social