Post

Replies

Boosts

Views

Activity

Reply to I can’t complete assistant setup up in Reality Composer Pro 3 beta
By the way, the field for API key has a placeholder that says optional. However, at least for OpenAI, I don’t believe the API key is optional. I think it’s required, at least it was required for me when I tried to create a provider for OpenAI. I think I had to put the API key in before it actually worked. Can someone from Apple comment on API key field being optional or not for various API vendors?
Jun ’26
Reply to I can’t complete assistant setup up in Reality Composer Pro 3 beta
I've followed the steps for Add a model provider. I have added the correct values in each field of the dialog as best I understand based on latest ChatGPT instructions. I am adding OpenAI as the provider. I am able to create the provider, but it has a red dot saying not connected. I click the Connect button but nothing happens and the provider continues to show not connected. I will try a different provider, but anything else to check before I submit a bug ticket. Seems like the basics of creating an assistant should work without having to do a bug.
Jun ’26
Reply to Foundation Models (Detected Content Likely to be Unsafe) Error
I am working through the Apple Developer Foundations Models Code Along. Last week I successfully completed Chapter 1.6 and got the app to run with Generate Itenerary output. However, this week, I'm now getting a new error and the foundation model is now giving a console error that says "Safety guardrails were triggered. If this is unexpected, please use LanguageModelSession.logFeedbackAttachment(sentiment:issues:desiredOutput:) to export the feedback attachment and file a feedback report at https://feedbackassistant.apple.com."
Oct ’25
Reply to Navigation Title no longer showing for first Tab in iOS/iPadOS 26
The issue does not appear to be with the first tab, but with navigation title and navigation stack in a set of views in a TabView (iOS) or NavigationSplitView (iPadOS). I've added the following new content to the feedback issue: ⸻ SwiftUI .navigationTitle Bug Diagnosis — iOS/iPadOS 26.0 Issue Summary • The navigation title set using .navigationTitle("Directives") in DirectivesView fails to appear on iOS/iPadOS 26.0, even when following Apple’s current SwiftUI best practices. • The same code works as expected in earlier versions (e.g., iOS/iPadOS 18.5). • The issue persists for both iPhone and iPad targets. Diagnostic Steps Taken Modifier Placement and View Structure • Tested both attaching .navigationTitle and a .toolbar (with a visible button) directly to the immediate child of NavigationStack (ZStack), and to the NavigationStack itself. • No change: Navigation bar, title, and toolbar item remain absent in iOS/iPadOS 26.0. Content Minimization Test • Replaced the entire content of DirectivesView with just Text("Test") inside a NavigationStack, using .navigationTitle and .toolbar. • Result: Navigation bar and title are still missing, confirming that the issue is not related to content, layout, or subviews. Subview Analysis • Confirmed that all custom subviews (DirectivesLogoView, DirectivesHeaderView, DirectivesSignatureView) are simple SwiftUI views with no use of navigation containers/modifiers or safe area overlays. • No evidence of .navigationBarHidden(true) or nested navigation stacks. Background Image Diagnostic • Temporarily removed and then reintroduced the background image (Image("Starfield")) to ensure it was not affecting the navigation bar rendering. • No effect on the presence of the navigation title or bar. Toolbar Item Diagnostic • Added and then removed a visible .toolbar item to test if a toolbar presence would force the navigation bar/title to appear (as sometimes required in new SwiftUI). • Toolbar item did not affect the navigation bar or title presence in iOS/iPadOS 26.0. TabView Position Control Test • Swapped the position of DirectivesView in the parent TabView to check for index-related issues. • The navigation bar/title remains missing regardless of tab order, confirming the problem is specific to the view or navigation stack context. Key Conclusion • The navigation title and navigation bar are not rendered under any tested conditions in iOS/iPadOS 26.0 for this view hierarchy, even in the most minimal NavigationStack configuration. • This is a regression or unannounced behavioral change in SwiftUI on iOS/iPadOS 26.0, not caused by content, overlays, modifier placement, or subview implementation. Action Requested • Please clarify if there are new requirements for navigation bar/title visibility in root NavigationStack views in iOS/iPadOS 26.0, or confirm this is a regression. • Requesting a fix or documentation update, since the app’s existing navigation structure now fails to show basic navigation elements in the latest OS. ⸻ In addition: Summary of the Issue: • A minimal SwiftUI view (MinimalNavigationTitleBugView) was created to demonstrate the navigation title bug. • In the Xcode Canvas preview, the navigation title for this minimal view appears as expected. • In contrast, my production app’s view (DirectivesView) does not display the navigation title—neither in the Xcode Canvas preview nor when running the app in the simulator or on device (iOS/iPadOS 26.0). Additional Diagnostic Details: • The issue does not appear to be caused by my code: • Both minimal and production views use the standard SwiftUI navigation patterns (NavigationStack, .navigationTitle attached to the direct child). • All custom subviews are simple, do not use navigation modifiers, and do not overlay the navigation bar area. • No .navigationBarHidden(true), nested navigation stacks, or unusual global environment modifiers are used. • The bug persists even when all content is reduced to a single Text view. Conclusion: • The fact that the minimal view works in preview but the production view does not—even in preview—suggests this bug is likely triggered by app structure, view hierarchy, or a change/regression in SwiftUI’s navigation logic for complex root or tab-based views. Action Requested: • Please clarify whether there are any new requirements for root navigation bar/title visibility in iOS/iPadOS 26.0, or confirm this as a regression. Thank you for your attention! ⸻ I have attempted to reproduce this bug in a minimal project that uses a TabView and NavigationStack, but the issue does not appear in the Xcode Canvas preview or in that context. The navigation title bug only occurs in my full production app. This suggests that the issue is likely triggered by real-world app hierarchy, parent containers, or app-level configuration that does not exist in minimal or preview scenarios.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Jul ’25
Reply to Navigation Title no longer showing for first Tab in iOS/iPadOS 26
Update as of 6/26/25: Still same issue (No Navigation Title displayed on first tab in TabView and NavigationSplitView) when tried on iOS 26.0 Developer Beta 2 and iPadOS 26.0 Developer Beta 2, in Simulator and on device running 26.0 Developer Beta 2. More Info: iPhone 16 Pro Max Simulator 26.0, in Portrait, Navigation Title for first Tab view is blank. Turning iPhone 16 Pro Max Simulator 26.0, in Landscape, in-line navigation title appears as expected. iPhone 16e Simulator 26.0, in Portrait, Navigation Title for first Tab view is blank. Turning iPhone 16e Simulator 26.0, in Landscape, in-line navigation title appears as expected. iPad Pro 11-in Simulator 26.0, in Portrait, Navigation Title for first Tab view is blank. Turning iPad Pro 11-in Simulator 26.0, in Landscape, Navigation Title for first Tab view is blank.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Jun ’25
Reply to New Design - impact to color use in existing app SwiftUI View
As part of the 6/12/25 SwiftUI Group lab, Curt and Taylor spoke to this specifically related to use of color in liquid glass SwiftUI views and that use of color should be limited. However, they didn’t speak to how to put color back into List View outline disclosure carets that aren’t there in new iOS/iPad OS 26. I would still like to know if I can add color back into the carets. Here was my group lab question that was discussed: “I’ve noticed with the new design language, SwiftUI views appear to not use color as much. Example, color modifiers for List View items like carets. Is this intended and can developers introduce color back into SwiftUI view elements, if desired, like in iOS/iPadOS 18?”
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Jun ’25
Reply to I can’t complete assistant setup up in Reality Composer Pro 3 beta
By the way, the field for API key has a placeholder that says optional. However, at least for OpenAI, I don’t believe the API key is optional. I think it’s required, at least it was required for me when I tried to create a provider for OpenAI. I think I had to put the API key in before it actually worked. Can someone from Apple comment on API key field being optional or not for various API vendors?
Replies
Boosts
Views
Activity
Jun ’26
Reply to I can’t complete assistant setup up in Reality Composer Pro 3 beta
I was able text get OpenAI provider to work. The exact field entries for the url, API key and API Key Header were not easy to figure out. It took offline (from Apple documentation) to find out the correct expectations for the fields for OpenAI to allow a model assistant connection.
Replies
Boosts
Views
Activity
Jun ’26
Reply to I can’t complete assistant setup up in Reality Composer Pro 3 beta
By the way, I added a different provider (OpenRouter) and it worked. Not sure why OpenAI provider setup did not work (would not connect).
Replies
Boosts
Views
Activity
Jun ’26
Reply to I can’t complete assistant setup up in Reality Composer Pro 3 beta
I've followed the steps for Add a model provider. I have added the correct values in each field of the dialog as best I understand based on latest ChatGPT instructions. I am adding OpenAI as the provider. I am able to create the provider, but it has a red dot saying not connected. I click the Connect button but nothing happens and the provider continues to show not connected. I will try a different provider, but anything else to check before I submit a bug ticket. Seems like the basics of creating an assistant should work without having to do a bug.
Replies
Boosts
Views
Activity
Jun ’26
Reply to Foundation Models (Detected Content Likely to be Unsafe) Error
Rebooting my Mac and doing Build and Run again worked.
Replies
Boosts
Views
Activity
Oct ’25
Reply to Foundation Models (Detected Content Likely to be Unsafe) Error
I am working through the Apple Developer Foundations Models Code Along. Last week I successfully completed Chapter 1.6 and got the app to run with Generate Itenerary output. However, this week, I'm now getting a new error and the foundation model is now giving a console error that says "Safety guardrails were triggered. If this is unexpected, please use LanguageModelSession.logFeedbackAttachment(sentiment:issues:desiredOutput:) to export the feedback attachment and file a feedback report at https://feedbackassistant.apple.com."
Replies
Boosts
Views
Activity
Oct ’25
Reply to Navigation Title no longer showing for first Tab in iOS/iPadOS 26
Fixed DirectivesView navigation title issue by raising the ScrollView{} up one level in my VStack hierarchy so that all VStack views were encompassed by the ScrollView{}. This was not needed before and not sure why this had to be done for iOS/iPadOS 26 (what changed??), but it works now.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Jul ’25
Reply to Navigation Title no longer showing for first Tab in iOS/iPadOS 26
Still an issue with iOS/iPadOS 26.0 Developer Beta 4.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Jul ’25
Reply to Navigation Title no longer showing for first Tab in iOS/iPadOS 26
Still an issue with iOS/iPadOS 26.0 Developer Beta 3.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Jul ’25
Reply to Navigation Title no longer showing for first Tab in iOS/iPadOS 26
The issue does not appear to be with the first tab, but with navigation title and navigation stack in a set of views in a TabView (iOS) or NavigationSplitView (iPadOS). I've added the following new content to the feedback issue: ⸻ SwiftUI .navigationTitle Bug Diagnosis — iOS/iPadOS 26.0 Issue Summary • The navigation title set using .navigationTitle("Directives") in DirectivesView fails to appear on iOS/iPadOS 26.0, even when following Apple’s current SwiftUI best practices. • The same code works as expected in earlier versions (e.g., iOS/iPadOS 18.5). • The issue persists for both iPhone and iPad targets. Diagnostic Steps Taken Modifier Placement and View Structure • Tested both attaching .navigationTitle and a .toolbar (with a visible button) directly to the immediate child of NavigationStack (ZStack), and to the NavigationStack itself. • No change: Navigation bar, title, and toolbar item remain absent in iOS/iPadOS 26.0. Content Minimization Test • Replaced the entire content of DirectivesView with just Text("Test") inside a NavigationStack, using .navigationTitle and .toolbar. • Result: Navigation bar and title are still missing, confirming that the issue is not related to content, layout, or subviews. Subview Analysis • Confirmed that all custom subviews (DirectivesLogoView, DirectivesHeaderView, DirectivesSignatureView) are simple SwiftUI views with no use of navigation containers/modifiers or safe area overlays. • No evidence of .navigationBarHidden(true) or nested navigation stacks. Background Image Diagnostic • Temporarily removed and then reintroduced the background image (Image("Starfield")) to ensure it was not affecting the navigation bar rendering. • No effect on the presence of the navigation title or bar. Toolbar Item Diagnostic • Added and then removed a visible .toolbar item to test if a toolbar presence would force the navigation bar/title to appear (as sometimes required in new SwiftUI). • Toolbar item did not affect the navigation bar or title presence in iOS/iPadOS 26.0. TabView Position Control Test • Swapped the position of DirectivesView in the parent TabView to check for index-related issues. • The navigation bar/title remains missing regardless of tab order, confirming the problem is specific to the view or navigation stack context. Key Conclusion • The navigation title and navigation bar are not rendered under any tested conditions in iOS/iPadOS 26.0 for this view hierarchy, even in the most minimal NavigationStack configuration. • This is a regression or unannounced behavioral change in SwiftUI on iOS/iPadOS 26.0, not caused by content, overlays, modifier placement, or subview implementation. Action Requested • Please clarify if there are new requirements for navigation bar/title visibility in root NavigationStack views in iOS/iPadOS 26.0, or confirm this is a regression. • Requesting a fix or documentation update, since the app’s existing navigation structure now fails to show basic navigation elements in the latest OS. ⸻ In addition: Summary of the Issue: • A minimal SwiftUI view (MinimalNavigationTitleBugView) was created to demonstrate the navigation title bug. • In the Xcode Canvas preview, the navigation title for this minimal view appears as expected. • In contrast, my production app’s view (DirectivesView) does not display the navigation title—neither in the Xcode Canvas preview nor when running the app in the simulator or on device (iOS/iPadOS 26.0). Additional Diagnostic Details: • The issue does not appear to be caused by my code: • Both minimal and production views use the standard SwiftUI navigation patterns (NavigationStack, .navigationTitle attached to the direct child). • All custom subviews are simple, do not use navigation modifiers, and do not overlay the navigation bar area. • No .navigationBarHidden(true), nested navigation stacks, or unusual global environment modifiers are used. • The bug persists even when all content is reduced to a single Text view. Conclusion: • The fact that the minimal view works in preview but the production view does not—even in preview—suggests this bug is likely triggered by app structure, view hierarchy, or a change/regression in SwiftUI’s navigation logic for complex root or tab-based views. Action Requested: • Please clarify whether there are any new requirements for root navigation bar/title visibility in iOS/iPadOS 26.0, or confirm this as a regression. Thank you for your attention! ⸻ I have attempted to reproduce this bug in a minimal project that uses a TabView and NavigationStack, but the issue does not appear in the Xcode Canvas preview or in that context. The navigation title bug only occurs in my full production app. This suggests that the issue is likely triggered by real-world app hierarchy, parent containers, or app-level configuration that does not exist in minimal or preview scenarios.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Jul ’25
Reply to Navigation Title no longer showing for first Tab in iOS/iPadOS 26
Reference Feedback bug item FB17987650. I completed an extensive diagnostic and troubleshooting chat session with Xcode 26 Beta 2 Swift Assist AI Coding Assistant (ChatGPT) regarding this bug. Additional details that came out of this chat session that should be considered for this feedback FB17987650.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Jun ’25
Reply to Navigation Title no longer showing for first Tab in iOS/iPadOS 26
Also, this issue with the navigation title not appearing doesn’t happen at all on current App Store release production app running on iOS 18.5 and iPadOS 18.5 so this is a recent occurrence with the new iOS and iPadOS 26.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Jun ’25
Reply to Navigation Title no longer showing for first Tab in iOS/iPadOS 26
Update as of 6/26/25: Still same issue (No Navigation Title displayed on first tab in TabView and NavigationSplitView) when tried on iOS 26.0 Developer Beta 2 and iPadOS 26.0 Developer Beta 2, in Simulator and on device running 26.0 Developer Beta 2. More Info: iPhone 16 Pro Max Simulator 26.0, in Portrait, Navigation Title for first Tab view is blank. Turning iPhone 16 Pro Max Simulator 26.0, in Landscape, in-line navigation title appears as expected. iPhone 16e Simulator 26.0, in Portrait, Navigation Title for first Tab view is blank. Turning iPhone 16e Simulator 26.0, in Landscape, in-line navigation title appears as expected. iPad Pro 11-in Simulator 26.0, in Portrait, Navigation Title for first Tab view is blank. Turning iPad Pro 11-in Simulator 26.0, in Landscape, Navigation Title for first Tab view is blank.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Jun ’25
Reply to New Design - impact to color use in existing app SwiftUI View
As part of the 6/12/25 SwiftUI Group lab, Curt and Taylor spoke to this specifically related to use of color in liquid glass SwiftUI views and that use of color should be limited. However, they didn’t speak to how to put color back into List View outline disclosure carets that aren’t there in new iOS/iPad OS 26. I would still like to know if I can add color back into the carets. Here was my group lab question that was discussed: “I’ve noticed with the new design language, SwiftUI views appear to not use color as much. Example, color modifiers for List View items like carets. Is this intended and can developers introduce color back into SwiftUI view elements, if desired, like in iOS/iPadOS 18?”
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Jun ’25
Reply to Color of Outline Disclosure List Carets in visionOS SwiftUI View
Reference FB13820942
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Jun ’25