It's quite a subjective question. Have you heard any reason why you shouldn't update? You could always take a backup of your current device, then do the update. If you don't like it, restore from your backup.

There's a bunch of ways to do this. Let me explain a few ideas I've got... If your website is using some sort of Content Management System (CMS), then it likely already provides a JSON file that contains this information. You could download that file, interrogate the various parts of it and determine where the important information is held for what your app needs, then load the thumbnail images, headlines and preview text from there. If it doesn't use a CMS, someone somewhere (you) is always going to have to create this file of metadata. If I were you I'd have it as part of the website/hosting, and your app should download that file. I wouldn't put it in the app itself because you'd have to update the app - which is labour-intensive, and pointless. (We don't have to download a new copy of Apple's News app every time there's a new story.) What you would do with the JSON file downloaded from the website is take the relevant bits from it, then add the image, headline, preview text to an array of articles in the app, and display those in your view. I'd say sort it by article date descending, and limit how many you put in the view. When a user taps one of the articles, you would then download the full article from the website. It wouldn't make any sense to download the full article as part of the JSON file as the user might not view it. Be sure to implement error handling if you can't reach the website to download the data. And don't download data you already have, i.e. only download article data for articles after the most recent date in your list of articles. For example, if you have two articles already downloaded in the app, and they're dated last Monday and last Tuesday, if the JSON file now contains an article for today, you would only bother downloading today's article. If you're going to limit the number of articles shown your view, then your array can be a FIFO stack, i.e. first in first out. If you want to retain 20 articles then you would remove the oldest article from the array and add a new one into it. Because you're sorting the data in the view anyway there is no need to handling rotating the data in the array, i.e. no need to delete item 0 and move item 1 into slot 0, 2 into slot 1 etc. Hope this helps.

What is StandardHomeMovie? What is Movie? What is exampleMovie2? What is CustomTabSwitcher? What is SmallVerticalButton? What is PlayButton? Without this code we can't really help you. I could create a simple struct to cover each of those, but who's to say the issue isn't in one of those?

Have you raised a Feedback report? If not, please do so at https://www.apple.com/feedback/ then post the FB number here.

Beta releases generally include logs of debugging and various processes running in the background that can use up battery. I wouldn't install a beta on my primary device because I'd hit issues exactly like these.

I think both task and onAppear are executed before the view is displayed, so you can use either. A quick internet search suggests this page has some good examples: https://byby.dev/swiftui-task-vs-onappear

It's a beta. Who forced you to install it? Just uninstall it. Plug it into a computer and put it in DFU mode. You can search the internet for instructions. I hope you have a backup from iOS 17.x.

Have you tried using backticks? var `Type`: String

If you don't want to use .task as recommended by the Apple employee before me, then you might want to implement something like an .onFirstAppear so it's only executed once. Something like this should work: private struct OnFirstAppear: ViewModifier { let perform: () -> Void @State private var firstTime = true func body(content: Content) -> some View { content.onAppear { if firstTime { firstTime = false perform() } } } } extension View { func onFirstAppear(perform: @escaping () -> Void) -> some View { modifier(OnFirstAppear(perform: perform)) } } Use it as you would use .onAppear.

Have you raised a Feedback report? If not, please do so at https://www.apple.com/feedback/ then post the FB number here. In all cases, you must raise the bug first, then you can, if you like, inform us on here, but we're just third-party developers like you. We have no input into when Apple deal with issues, and the best way to let Apple know there's an issue is to tell Apple about it by raising a Feedback report.

Is your home a "new location"? I doubt it. What's the actual issue here?

What is the actual error text you're receiving? You say it's a "dimension" error, but it's really important to know what the actual error is because it might be saying your images are too large or too small. If they're too large you can simply crop them. If they're too small you could pad them out a little.

Have you tried debugging this in Xcode with your code? It's pretty difficult for us to figure out what's wrong while you sit there with the code...

Break this down a little for us: What is "auto launch"? And where are you turning it off? Where is music being displayed on your Watch, and when? Why would turning off something called "auto launch" stop Music being displayed somewhere on a Watch? These two things don't seem related. Also... These are the Developer Forums, where developers of apps for Apple's platforms ask each other for hints and tips on coding. These forums are NOT where Apple's actual developers chat about stuff. Your question is more of a product support one, so I'd suggest you ask it over at the Apple Support Forums. Thanks.

Have they ever connected to your phone? Did you see the connection dialog appear? Have you read the instructions in the AirPods Pro packaging that show you how to start pairing?