Posts

Post not yet marked as solved
1 Replies
I use to have my Sections (with header) within a List View that was within a NavigationView. Since NavigationView is now deprecated, I've transitioned to using NavigationStack. No other changes to code, but now my section headers don't have a triangle to show/hide the section content...i.e. the section is now longer collapsible. Your code above doesn't show what your ForEach statements are wrapped in. Are they within a List?
Post not yet marked as solved
1 Replies
I've recently started an app where the content view uses this type of hierarchical list view (with children). I'm able to successfully display the hierarchical list in the content view, and when I tap an item in the hierarchy, I'm successfully able to navigate to a detail view for that tapped item. I'm also able to edit one of the tapped item properties in the detail view using a TextEditor view. However, when I click save in the detail view, the changed property will only be saved if it was the parent list item row that I tapped in the content view. If it was a child list item in the content view, the save does not work. I think I may have a problem in my save code logic and I'm trying to investigate.
Post marked as solved
10 Replies
I talked with Apple about this during a lab session at WWDC21. They had me create a feedback ticket. Here is the Feedback: FB9156589
Post not yet marked as solved
4 Replies
Apple has some excellent SwiftUI and UIKit tutorials on the developer website. The tutorials allow you to work through the specific app creation projects that teach you the various technologies for SwiftUI and UIKit. SwiftUI Tutorials iOS App Dev Tutorials
Post not yet marked as solved
2 Replies
I'm having a similar problem but with an independent watch app using Swift UI. The live preview in Xcode shows a back button on the detail screen and it allows me to return to the parent (content view) screen. However, when I run the same app on the watch simulator and on an actual Apple Watch Series 6, the back button doesn't appear and I can't navigate back to the parent view.
Post not yet marked as solved
7 Replies
Thank you very much! If I’m already logged into my GitHub account through Xcode using a password, do I have to log out and delete that account entry in Xcode and then create a new GitHub account and login with the token or can I just log out of the current GitHub account in Xcode preferences and then log back in with the new access token?
Post not yet marked as solved
7 Replies
So how can I create that authentication token and then how do I set up my login in Xcode to GitHub to use that token instead of a password which GitHub is deprecating?
Post marked as solved
1 Replies
I think after talking to Apple engineers in a 1-on-1 lab, and seeing the response from  in this other forum question - https://developer.apple.com/forums/thread/650776?answerId=615249022#615249022, I feel my questions have been answered.
Post not yet marked as solved
1 Replies
Well, I tried creating a new test project using Xcode 12 Beta and a Watch Only template for watchOS, and, except for the HostingController entry point being replaced by the App.swift entry point and the ExtensionDelegate.swift file being removed, it appears the new project is still a WatchKit app project. The project still has multiple targets including WatchKit App and WatchKit Extension targets. Therefore, I'm still not sure what additional benefit I'd gain starting with a Xcode 12 Beta 100% SwiftUI project template. Any insights would be welcome.
Post marked as solved
2 Replies
Well, I tried creating a new test project using Xcode 12 Beta and a Watch Only template for watchOS, and, except for the HostingController entry point being replaced by the App.swift entry point and the ExtensionDelegate.swift file being removed, it appears the new project is still a WatchKit app project. The project still has multiple targets including WatchKit App and WatchKit Extension targets. Therefore, it appears dealing with updating watch complications uses most/all of the same APIs that are used for the non-100% SwiftUI project template project from Xcode 11.
Post marked as solved
3 Replies
Ok. Since this is a watch only app and I don’t need to sync data with other devices, it sounds like using CloudKit is not necessary and I can use Core Data for local on-watch data persistence. What is the latest and greatest information I can reference for using Core Data for my situation (Xcode 12 beta, watch only watchOS 7 app, SwiftUI)? Is there a WWDC20 video session that covers my situation? Example code?
Post marked as solved
112 Replies
I also highly recommend the following resources: App Development with Swift - https://books.apple.com/us/book/app-development-with-swift/id1465002990 Apple’s SwiftUi Tutorial - https://developer.apple.com/tutorials/swiftui/ Udemy iOS App Development, Swift, and SwiftUI courses. I like the courses by Mark Price of Devslopes, Nick Walter, and Dr. Angela Yu of the London App Brewery.
Post not yet marked as solved
4 Replies
From what I understood from the session video, a window is a type of scene.
Post not yet marked as solved
3 Replies
I do understand that jacket and pins have been provided to SSC winners, as of now. However, I’m hoping Apple will make them available to broader WWDC20 community at some point. Do you know for sure Apple will not do this?
Post marked as solved
5 Replies
Had a good 1-on-1 lab session with DTS this morning. They gave me a couple of different options to fix this. It’s gonna take some work so I have to decide which approach to use. One of the approaches is to use some of the new Xcode 12 Beta APIs for iOS 14 to replace my current approach to my detail view controller and instead use an advanced collection view that might make things much simpler and let the collection view API handle all the spacing.