You’re right! Definitely difficult to work with scrollviews and space elements and layout. I went through a lot of iterations of what I wanted to do for look and feel and decided I wanted to place my text label subviews using code rather than stacks and auto layout. I will try to give you a public link to my project on github as soon as I can.

My github repository is private. I’m not sure how to provide you access and still keep the repository private. I’m a novice and not very experienced working in github except through Xcode source control features.

Thanks!

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.

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?

From what I understood from the session video, a window is a type of scene.

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.

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?

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.

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.

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.

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?

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?

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.

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