These are the Developer Forums, where third-party developers ask each other for hints and tips on how to code their apps for Apple's platforms. Posting about bugs in these forums isn't going to progress them unless you also raise them as bugs in the usual place, which is not these Developer Forums. Apple's developers aren't sitting around reading these forums, waiting for things to fix. Please raise each bug separately at: https://feedbackassistant.apple.com/ You can post the FB numbers here if you want, so that others can link to them.

These are the Developer Forums, where third-party developers ask each other for hints and tips on how to code their apps for Apple's platforms. Posting bugs in these forums isn't going to progress them unless you also raise them as bugs in the usual place, which is not these Developer Forums. Apple's developers aren't sitting around reading these forums, waiting for things to fix. Please raise each bug separately at: https://feedbackassistant.apple.com/ You can post the FB numbers here if you want, so that others can link to them.

Well, what are you doing in 16.0.0 that works? Show us the code. It's very hard to help when you don't give us the information.

This is the most unreadable/least readable post I've ever seen on these forums. PLEASE use the code formatting options when you make a post. May I suggest you reply to this thread with the code properly formatted so we can read it? We might be able to help you out then.

I have Xcode 16.4 and exactly the same settings as you. Here's how it works: No files open: I've just single-clicked my payees file - this opens it in a new tab, but note that the tab's filename is in italics (I call this a temporary tab). This denotes that if you single-click or double-click any other file in the project tree, this one will be replaced. You can keep this file open in this tab by double-clicking the tab itself. Now, I've single-clicked the payload file. Because the payees file wasn't in a permanent tab the payload file replaced it: And here I've now double-clicked the lookups file. It opened in a new tab, and it replaced the payload tab because it was a temporary tab. Now I've double-clicked the notes file. It opened a new permanent tab of its own. And lastly, I've single-clicked the DataModel file, so it's in a temporary tab. So, the rules are: If the current tab has an italicised title, single-clicking will replace that tab with the clicked file. Single-click another file and it will replace it again. Think of this tab as a preview tab where you can just click to view a file but not have hundreds of tabs open just when you're trying to find a file. If the current tab's title is plain, single-clicking a new file opens a new tab in temporary mode. If the current tab's title is plain, doublie-clicking opens a new tab in permanent mode.

Have you raised a Feedback report? If not, please do so at https://feedbackassistant.apple.com/ then post the FB number here. Bug reports didn't get logged, triaged and acted upon if they're only posted in these Developer Forums. You're basically telling people who are just like you that there's an issue. We aren't Apple's employed developers.

Difficult to help without seeing any code, but that error generally means the View you're seeing the error in has no link back to the ApplicationData object that the View is trying to use. For example: // ApplicationData.swift @Observable class ApplicationData { var someInteger: Int = 1 } This creates an Observable object called ApplicationData. You can then use it with: // MainApp.swift @main struct MainApp: App { var body: some Scene { WindowGroup { let applicationData: ApplicationData = ApplicationData() ContentView() .environment(applicationData) } } } // ContentView.swift struct ContentView: View { @Environment(applicationData) var applicationData var body: some View { Text("someInteger = \(applicationData.someInteger)") } } The error you're receiving is suggesting you haven't added something like line 8. That's required to bind the object you instantiated (in MainApp in this example, which is the view's ancestor) to the object you want to use in the View, at line 15.

Have you asked Twilio whether they're using private API calls? If you remove the Twilio pod (and any relevant calls to it in your code) does it compile and validate?

These are the Developer Forums, where developers of third-party 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 new features. If you have a suggestion, you should raise it at: https://feedbackassistant.apple.com/

Your post isn't formatted correctly, and we can't actually see your screenshot. Would you mind replying to this thread, with better formatting? In the meantime, if you think this is serious enough to be a bug, raise it in the Feedback Assistant: https://feedbackassistant.apple.com/ then post the FB number here.

These are the Developer Forums, where developers of apps for Apple's platforms ask each other for hints and tips on coding. If you already have a case number, just contact Apple in the way you already have. No one on these forums can help you. We aren't employed by Apple; we're just random people from around the world writing apps for Apple's platforms.

@BillAlvord Not sure you really meant to put your actual private API key in your post... You might want to have that one destroyed and get another so others browsing these forums don't use it.

As @Claude31 says, the beta releases are not optimised. They contain extra processes that run in the background collecting data and performing extra logging so that Apple can tweak the software before release. This undoubtedly uses extra battery power. You shouldn't install the betas on your primary device. If you have a spare device - your previous iPhone, for example - try the beta on that, and only install the finalised general release on your main, primary devices.

You can get your app's id in App Store Connect. If you haven't already created the app in App Store Connect, do that first. Then, in the General > App Information section on the left, there's an Apple ID. number. Grab that number and create a URL like this: https://apps.apple.com/us/app/<app name>/id<your number here> for example: https://apps.apple.com/us/app/myapp/id1234567890 Then just share that with the other user, and that should take them to the app in their App Store.

You say "half" the features no longer work, which means the app still has some features that do work. You might have customers using those features, and if they don't require any services from your company and its servers then they can be left alone as they are. Or, you could update the app and slim it down so it contains only the features that still work. Yes, I see your app developer has left, but you can easily hire a short-term contractor to update your app to do this. You would also be able to pop up a splash screen explaining the changes. Most people have automatic app updates enabled so most of your users will be caught by this. This route would be a cleaner way to handle things, as the app wouldn't show features that don't work anymore, and users wouldn't have to skip round them while using the app. I guess it depends on whether you want to be nice to your existing customers, or don't really care. (I don't mean that in a bad way!)