I had this problem before and my answer to your question based off of that would be to create a custom ViewModifier and use @ViewBuilder so you can handle the compilation error message. Something like this should work: struct DeviceAdaptedListStyle: ViewModifier { var isPhone: Bool { ... } @ViewBuilder func body(content: Content) -> some View { if isPhone { content.listStyle(.plain) } else { content.listStyle(.sidebar) } } } extension List { func deviceAdaptedListStyle() -> some View { modifier(DeviceAdaptedListStyle()) } } At the moment, there might be a better solution with Swift 5.5, but I haven't checked.

I believe the section headers in a list should be aligned with the content in the list rows. This has been updated in iOS 15 for SwiftUI to match how UITableView section headers were being aligned previously. If you still want the other style of header then, as of iOS 15 beta 4, you can apply the headerProminence modifier to a Section. Section("Section Header") { Text("Hello, World!") } .headerProminence(.increased) This will align the header text will the edge of the list. Note: section headers modified in this way may be changed in future betas to be correctly aligned.

You should use the popover modifier. This will show a sheet on iPhone and an overlaying view on iPad. Here’s an example: Button("Rules") { presentPopup = true } .popover(isPresented: $presentPopup, arrowEdge: .bottom) { Text("test") .frame(width: 100, height: 100) } Check out the documentation for more information on usage.

AttributedString needs to be initialised with the markdown parameter. So change the variable to this: var text = try AttributedString(markdown: "**Hello**, `world`! Visit our [website](https://www.capitalone.com).")

It seems that, after rereading the new documentation on alert(_:ispresented:actions:message:), you can just add the .keyboardShortcut(.defaultAction) modifier to one of the buttons in the alert's actions to make it the default action and therefore bold.

Are you using Xcode 13?

After seeing that my feedback report (FB8991275) has a potential fix in Xcode 13, I tried previewing on a device running iOS 15 beta 4 using Xcode 13 beta 4 and unfortunately I am getting the same error message, again. I really hope that this fix will be available in future betas or at least the official release of Xcode 13.

From the iOS & iPadOS 15 beta 4 release notes: Resolved in iOS & iPadOS 15 beta 4 AsyncImage in List no longer cancels image downloads prematurely. (78187465, 78727070)

Applying the .privacySensitive() modifier won’t actually redact the text, it just tells SwiftUI that the text is privacy sensitive. To actually redact the text, apply the .redacted(reason: .privacy) somewhere higher up in the view hierarchy. For example, in your case, you could add the .redacted(reason:) modifier to you’re VStack if you wanted to preview what it looks like. Check out these links about more on how to use this modifier: https://developer.apple.com/documentation/swiftui/text/privacysensitive(_:) https://developer.apple.com/documentation/swiftui/redactionreasons/privacy https://www.hackingwithswift.com/quick-start/swiftui/how-to-mark-content-as-private-using-privacysensitive

Do you mean a TabView with the tab view style of .page (PageTabViewStyle)? If so, it's currently not possible in SwiftUI (as of iOS 15 beta 5). You can, however, reach down into UIKit and modify some of its appearance API. Here's some examples of its usage: // All page dots have a colour of red UIPageControl.appearance().pageIndicatorTintColor = .systemRed // Only the current page's dot is green UIPageControl.appearance().currentPageIndicatorTintColor = .systemGreen // All page dots have a colour of indigo but the current page's dot is blue UIPageControl.appearance().currentPageIndicatorTintColor = .systemBlue UIPageControl.appearance().pageIndicatorTintColor = .systemIndigo Place this in the initialiser of your view. struct SomeView: View { init() { // modify appearance } var body: some View { … } }

This isn’t a new thing in SwiftUI. It’s more to do with Swift and structs. The error message is saying that it can’t find the variable room inside itself (as a property of the struct). You need to add this property called room to your ExtractedView and pass this in from your ContentView, like this: struct ExtractedView: View { let room: Room // now it knows what 'room' is   var body: some View { … } } In ContentView: List(rooms) { room in ExtractedView(room: room) // give the view the room it needs to show }

You need to add two alignment constraints to place the views in the centre of the screen. If you want to, you can place the two views inside a UIStackView to make positioning easier. To do this select the label and button, click the Embed In button in the bottom right of the screen (fifth from the left) and choose Stack View. You can modify how the stack view positions its containing views. To align this stack view, select it and click the Align button in the bottom right of the screen (second from the left) and add Horizontally in Container and Vertically in Container constraints. This should position the label and button in the centre of the device. If you don't want the label and button in a UIStackView you can always add constraints relative to each other. Hope this helps.

You can manually enable and disable searching and then link this up with your own keyboard shortcut. You just need to toggle the isSearching environment value. There is also a dismissSearch method in the environment if you prefer to dismiss the search like that.

I have tried this once more using Xcode 13 beta 5 using a device running iOS 15 beta 8 and it works. Thank you very much to those who got this working!

Resolved in iOS & iPadOS 15 beta 2 Buttons in toolbar items now respect custom styles or customizations to their labels. This means that you can customise the appearance of toolbar buttons however you like. If you wanted the destructive red style button, you can specify a role for the button, like this: Button(role: .destructive) { … } label: { … } NOTE: This will only work with iOS 15, macOS 12 and similar.