Man does not live by coordinators alone! 🧐
If the #Coordinator is akin to a classic #UINavigationController, then the full-screen view becomes our #UIViewController. 🚀
To identify such a specific view, I simply refer to it as a PageView. 📄
#DevDiary #BuildInPublic #SwiftUI
If the #Coordinator is akin to a classic #UINavigationController, then the full-screen view becomes our #UIViewController. 🚀
To identify such a specific view, I simply refer to it as a PageView. 📄
#DevDiary #BuildInPublic #SwiftUI
December 17, 2025 at 12:32 PM
Man does not live by coordinators alone! 🧐
If the #Coordinator is akin to a classic #UINavigationController, then the full-screen view becomes our #UIViewController. 🚀
To identify such a specific view, I simply refer to it as a PageView. 📄
#DevDiary #BuildInPublic #SwiftUI
If the #Coordinator is akin to a classic #UINavigationController, then the full-screen view becomes our #UIViewController. 🚀
To identify such a specific view, I simply refer to it as a PageView. 📄
#DevDiary #BuildInPublic #SwiftUI
The #Coordinator will be responsible solely for the navigation layer. 🧭
Think of it like our old #UIKit friend, UINavigationController! 🚶♂️
I'm experimenting with different #ViewModifiers to enhance the code's readability. ✨
#SwiftUI #Swift #DevDiary
Think of it like our old #UIKit friend, UINavigationController! 🚶♂️
I'm experimenting with different #ViewModifiers to enhance the code's readability. ✨
#SwiftUI #Swift #DevDiary
December 16, 2025 at 1:17 PM
The #Coordinator will be responsible solely for the navigation layer. 🧭
Think of it like our old #UIKit friend, UINavigationController! 🚶♂️
I'm experimenting with different #ViewModifiers to enhance the code's readability. ✨
#SwiftUI #Swift #DevDiary
Think of it like our old #UIKit friend, UINavigationController! 🚶♂️
I'm experimenting with different #ViewModifiers to enhance the code's readability. ✨
#SwiftUI #Swift #DevDiary
なにかCatalystは表示するUIViewControllerを自前のUINavigationControllerに入れないと挙動がおかしくなるし、iOSはUINavigationControllerの生成を任せないと挙動がおかしくなる気がする…🤔
November 8, 2025 at 12:44 PM
なにかCatalystは表示するUIViewControllerを自前のUINavigationControllerに入れないと挙動がおかしくなるし、iOSはUINavigationControllerの生成を任せないと挙動がおかしくなる気がする…🤔
For our new navigation pattern, we're not using TabView or NavigationStack – instead, a UINavigationController wrapped in UIViewControllerRepresentable manages all view presentation. When you switch tabs, we replace its viewControllers array using a custom crossfade transition.
October 16, 2025 at 5:04 PM
For our new navigation pattern, we're not using TabView or NavigationStack – instead, a UINavigationController wrapped in UIViewControllerRepresentable manages all view presentation. When you switch tabs, we replace its viewControllers array using a custom crossfade transition.
Ok, I did not expect the migration to be soo swift (no pun intended). Wrapped my UISearchController into UINavigationController and have search functionality in place. Tomorrow tackling bookmarks tab! Let's get this thing #iOS26 ready! #Apple #Swift #SwiftUI #buildinpublic #liquidglass
October 15, 2025 at 8:02 PM
Ok, I did not expect the migration to be soo swift (no pun intended). Wrapped my UISearchController into UINavigationController and have search functionality in place. Tomorrow tackling bookmarks tab! Let's get this thing #iOS26 ready! #Apple #Swift #SwiftUI #buildinpublic #liquidglass
今回のMIDI Recorderのマイナーアップデートは見た目はほぼ変わらないですが、内部的にUINavigationControllerを自前で実装したので、結構大変でした。
同じコードをKQ Dixie 26にも採用予定です。
同じコードをKQ Dixie 26にも採用予定です。
October 8, 2025 at 10:38 AM
今回のMIDI Recorderのマイナーアップデートは見た目はほぼ変わらないですが、内部的にUINavigationControllerを自前で実装したので、結構大変でした。
同じコードをKQ Dixie 26にも採用予定です。
同じコードをKQ Dixie 26にも採用予定です。
A workaround, if you're running into this one in your apps and are down to the wire. Wrap your primary content in an additional container UINavigationController. This may introduce other issues on older OSes, from my testing, but it's better than nothing
Thanks for the help! […]
Thanks for the help! […]
Original post on mastodon.social
mastodon.social
August 27, 2025 at 8:24 AM
A workaround, if you're running into this one in your apps and are down to the wire. Wrap your primary content in an additional container UINavigationController. This may introduce other issues on older OSes, from my testing, but it's better than nothing
Thanks for the help! […]
Thanks for the help! […]
Spent most of today stumped by a UINavigationController heisenbug that I'm starting to think might just end me
August 26, 2025 at 4:52 PM
Spent most of today stumped by a UINavigationController heisenbug that I'm starting to think might just end me
FB19905057 — Unrelated child UINavigationController overrides root split view controller's sidebar heirarchy and navigation bar on resize from regular to compact
This one will prevent me from shipping Pastel on iOS 26 until I find a solution 🤷♂️
This one will prevent me from shipping Pastel on iOS 26 until I find a solution 🤷♂️
August 26, 2025 at 12:14 PM
FB19905057 — Unrelated child UINavigationController overrides root split view controller's sidebar heirarchy and navigation bar on resize from regular to compact
This one will prevent me from shipping Pastel on iOS 26 until I find a solution 🤷♂️
This one will prevent me from shipping Pastel on iOS 26 until I find a solution 🤷♂️
FB19450443 — [Catalyst] Regression: when a UINavigationController is added to a non-window-root UITabBarController, tab bar is hidden permanently (iPad Idiom)
Weird edge cases here I come!
Weird edge cases here I come!
August 7, 2025 at 11:26 PM
FB19450443 — [Catalyst] Regression: when a UINavigationController is added to a non-window-root UITabBarController, tab bar is hidden permanently (iPad Idiom)
Weird edge cases here I come!
Weird edge cases here I come!
If you run into this one, it looks like the wrapping UINavigationController on a sidebar is indeed created, but somewhere later in the process after it's been added to the window. It used to be immediately when adding the view controller to the split controller. Not sure where the best place to […]
Original post on mastodon.social
mastodon.social
August 7, 2025 at 10:15 AM
If you run into this one, it looks like the wrapping UINavigationController on a sidebar is indeed created, but somewhere later in the process after it's been added to the window. It used to be immediately when adding the view controller to the split controller. Not sure where the best place to […]
FB19432138 — When contained in UISplitViewController sidebar, UINavigationController bottom toolbar is permanently hidden
August 7, 2025 at 10:03 AM
FB19432138 — When contained in UISplitViewController sidebar, UINavigationController bottom toolbar is permanently hidden
It's a couple of years old now, but I'm surprised how limited iPad's customizable toolbar API is. It only works for centered item groups, and only if your navigation item is set to editor or browser mode, not the default UINavigationController style. It also […]
[Original post on mastodon.social]
[Original post on mastodon.social]
August 1, 2025 at 11:20 AM
It's a couple of years old now, but I'm surprised how limited iPad's customizable toolbar API is. It only works for centered item groups, and only if your navigation item is set to editor or browser mode, not the default UINavigationController style. It also […]
[Original post on mastodon.social]
[Original post on mastodon.social]
:(
Why is FloatingBarContainerView Private API :(
It appears if you're using standalone UINavigationBars, you can't get the automatic UISearchBar hosting inside the navigation bar or pinned to the bottom of the display without using a full UINavigationController.
You *can* shove it in a […]
Why is FloatingBarContainerView Private API :(
It appears if you're using standalone UINavigationBars, you can't get the automatic UISearchBar hosting inside the navigation bar or pinned to the bottom of the display without using a full UINavigationController.
You *can* shove it in a […]
Original post on mastodon.social
mastodon.social
June 26, 2025 at 2:18 PM
:(
Why is FloatingBarContainerView Private API :(
It appears if you're using standalone UINavigationBars, you can't get the automatic UISearchBar hosting inside the navigation bar or pinned to the bottom of the display without using a full UINavigationController.
You *can* shove it in a […]
Why is FloatingBarContainerView Private API :(
It appears if you're using standalone UINavigationBars, you can't get the automatic UISearchBar hosting inside the navigation bar or pinned to the bottom of the display without using a full UINavigationController.
You *can* shove it in a […]
There's only a UINavigationController in UIKit.
June 23, 2025 at 7:24 AM
There's only a UINavigationController in UIKit.
Seems like Apple is all in on UINavigationItemBackButtonDisplayModeMinimal in iOS 26
June 14, 2025 at 3:51 PM
Seems like Apple is all in on UINavigationItemBackButtonDisplayModeMinimal in iOS 26
UINavigationController → NavigationStack
January 29, 2025 at 12:57 PM
UINavigationController → NavigationStack
Yeah it's a UINavigationController that has a rootViewController of a UIHostingController that hosts a SwiftUI View, which renders a NavigationLink inside a List. I am setting the environment at the root of the SwiftUI view.
January 23, 2025 at 10:21 PM
Yeah it's a UINavigationController that has a rootViewController of a UIHostingController that hosts a SwiftUI View, which renders a NavigationLink inside a List. I am setting the environment at the root of the SwiftUI view.
Yeah I've seen that before, though I feel like it's less common these days (?).
I wonder if it's required in this case because it's inside a UIKit/UINavigationController stack?
I wonder if it's required in this case because it's inside a UIKit/UINavigationController stack?
January 23, 2025 at 9:53 PM
Yeah I've seen that before, though I feel like it's less common these days (?).
I wonder if it's required in this case because it's inside a UIKit/UINavigationController stack?
I wonder if it's required in this case because it's inside a UIKit/UINavigationController stack?
So when does this problem happen?
I bisected my commits and found no code change to blame. Rather, it seems to happen the first time the card containing the WebView is presented.
This makes me suspect an issue with either React Navigation, UINavigationController, or React Native WebView.
I bisected my commits and found no code change to blame. Rather, it seems to happen the first time the card containing the WebView is presented.
This makes me suspect an issue with either React Navigation, UINavigationController, or React Native WebView.
December 29, 2024 at 7:47 AM
So when does this problem happen?
I bisected my commits and found no code change to blame. Rather, it seems to happen the first time the card containing the WebView is presented.
This makes me suspect an issue with either React Navigation, UINavigationController, or React Native WebView.
I bisected my commits and found no code change to blame. Rather, it seems to happen the first time the card containing the WebView is presented.
This makes me suspect an issue with either React Navigation, UINavigationController, or React Native WebView.
UINavigationController must be the most cursed component in all of iOS.
December 5, 2024 at 9:59 AM
UINavigationController must be the most cursed component in all of iOS.
amendment: it takes over the parent UINavigationController, which can then lead to similar
struggling to proceed here - with a SwiftUI sheet as a base, a UIPageViewController within, and a UIHostingController for pages, gesture recognizers conflict and break scrolling in unique and fascinating ways
struggling to proceed here - with a SwiftUI sheet as a base, a UIPageViewController within, and a UIHostingController for pages, gesture recognizers conflict and break scrolling in unique and fascinating ways
May 3, 2024 at 5:23 PM
amendment: it takes over the parent UINavigationController, which can then lead to similar
struggling to proceed here - with a SwiftUI sheet as a base, a UIPageViewController within, and a UIHostingController for pages, gesture recognizers conflict and break scrolling in unique and fascinating ways
struggling to proceed here - with a SwiftUI sheet as a base, a UIPageViewController within, and a UIHostingController for pages, gesture recognizers conflict and break scrolling in unique and fascinating ways
Container View にとある UIViewController をセットし、Container View を閉じると セットされていた UIViewController もちゃんと deinit される
でもセットするのを UINavigationController にすると、Container View を閉じたときに UINavigationController やその rootViewController が deinit されない…
なんでだ… 何か見落としているのか……？
でもセットするのを UINavigationController にすると、Container View を閉じたときに UINavigationController やその rootViewController が deinit されない…
なんでだ… 何か見落としているのか……？
January 16, 2024 at 3:23 PM
Container View にとある UIViewController をセットし、Container View を閉じると セットされていた UIViewController もちゃんと deinit される
でもセットするのを UINavigationController にすると、Container View を閉じたときに UINavigationController やその rootViewController が deinit されない…
なんでだ… 何か見落としているのか……？
でもセットするのを UINavigationController にすると、Container View を閉じたときに UINavigationController やその rootViewController が deinit されない…
なんでだ… 何か見落としているのか……？
Do you know if Compose on iOS uses native components like UITableView, UINavigationController, UISwitch etc. underneath?
November 3, 2023 at 4:07 PM
Do you know if Compose on iOS uses native components like UITableView, UINavigationController, UISwitch etc. underneath?
I don't mind other languages, if something is written like the Xamarin stuff in C#, or Kotlin, then great, but I don't like it when multi-platform frameworks don't use the native components like UISwitch, UINavigationController, UITableView etc. but reimplement some things that only look like them…
October 27, 2023 at 3:36 PM
I don't mind other languages, if something is written like the Xamarin stuff in C#, or Kotlin, then great, but I don't like it when multi-platform frameworks don't use the native components like UISwitch, UINavigationController, UITableView etc. but reimplement some things that only look like them…