Hacker News Reader

HNHacker News

Top New Best Ask Show Jobs

Comment by 0xferruccio | Hacker News Reader

Full thread

0xferruccio·

I tried out SwiftUI a couple of months ago and it was buggy even when sticking to the standard Navigation components..

But now it seems like a lot of problems have been solved

https://stackoverflow.com/questions/59279176/navigationlink-...

View on HN

> even when sticking to the standard Navigation components.

The standard navigation components have always been the buggiest part of UIKit. Don't even get me started on how UISearchController and UINavigationController interact on iOS 13…I have an app that's been sitting on the back burner, with full dark mode support, but unreleased for over six months because I haven't taken the time to figure out why the search bar decides it wants to be above the large title.

Didn’t know this! Am very much an amateur with iOS development and thought that sticking with the Swift “happy path” would’ve been a good idea

It's gotten better, it will probably work if you're not doing anything complicated. My view is set up from a five-year old storyboard and is dual UINavigationViews with UISearchControllers inside a UISplitView inside a UITabViewController :/ I'd still suggest sticking to the happy path, the other ones are even worse…

Do you have more examples than just that single one?

I ask, because I've encountered a number of situations where I figured it's a bug, when in fact it was my lack of understanding this new framework.

I had this issue in the simulator but on my phone it seems fine. Not ideal obviously but it does work, I released a simple app with it earlier this year.

OMG you cannot know how many times some SwiftUI thing has worked fine on my iPhone but not on the simulator … that was simulating my iPhone model running my iOS version.

Reply on news.ycombinator.com