Yes, I know that workaround but that's not really a workaround as it still requires staying with the UIKit lifecycle. If you use the SwiftUI lifecycle and assign AppDelegate/SceneDelegates those related entry points are no longer called - hence the apparent lacking functionality to allow me to migrate some of my apps that rely on some of that data that is missing.

The problem only happens occasionally. The Identifiable uses a string that is a constant for each item that cannot change. The hash and == methods are about as simple as they can be. Am still baffled.

Actually, I realized that the for some reason the Generate Swift Asset Symbol Extensions was not enabled by default. Flipping that flag took care of accessing the colors via UIColor.myblue as an example.

I was looking for forecasts beyond 10 days out, not historical data.

That's for the information. It now makes it clear that I will not be able to use WeatherKit for my current purposes. I was hoping that the forecasts would become more almanac like when the requested dates are in the future past the next 10 days. I do see the SDK being very useful; just not for this particular app scenario.

I stand correctly. I can get some hourly weather data, but when I try to get daily forecasts using .daily(startDate: start, endDate: end)I get nothing back and no errors.

I am getting another warning in addition to the same one as before. 2022-08-16 11:26:06.756397-0700 ItsAlmostTime[851:215502] [AuthService] Failed to generate jwt token for: com.apple.weatherkit.authservice with error: Error Domain=WeatherDaemon.WDSJWTAuthenticatorService.Errors Code=1 "(null)"

Apple unified my App ID prefix for all my apps/extension - but that did not seem to help the situation. The only difference is now the "Code" is 1 instead of 0.

Looks like that cleared up, so I can use SharePreview to show an alternate image and text on the share sheet when it opens. Now I am trying to figure out how to get a custom image and a URL output to iMessage when selected.

I just tried Beta 3 of Xcode and iOS 16, same issue.

That is feedback, but a button should "feel" like other buttons especially the big ones with the long title text in them.

I plan on watching that and all the videos (I am such a nerd). I was going through the documentation that was released yesterday but did not see anything that aligned with the LargeContentViewer features. I do see when building a test app that the LargeContentViewer is definitely a think in SwiftUI because TabView uses it as expected.