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!)

The latest updates of what? iOS 18 or iOS 26? Which version is causing an issue? Information like this is really important. It's like saying, "My car has a problem." People are naturally going to ask what's wrong with your car. Just, please, provide more relevant information in future so we don't have to ask. If it's iOS 26 Developer beta, then you must know that the betas include various processes that that are not present in the public releases. These processes run in the background to log things, record system issues etc. In short, the betas run more processes than the final version runs, and it is expected that your phone will run more processes, which in turn means it may run hotter and your battery life may be adversely affected. If you feel it's unusual, then feel free to raise an issue in the usual way, by raising a feedback report at: https://feedbackassistant.apple.com/ and post the FB number here. Remember to provide relevant information. As an aside, regarding the tags you added to your post, is "Developer Forums" really relevant to your post? Are you saying there's an issue with the forums? No, you aren't, so please don't use the wrong tags.

Is the option to do so still in the menus? If so, you can use the keyboard shortcuts > App Shortcuts in System Settings to add a keyboard combination to execute that menu command.

Can you simplify this sentence, please? It currently doesn't make much sense to me: But only when the app is opened after it was minimised by pressing digital crown, it didn't fetch data. It might help for you to log something to the console to show what the scenePhase is now, and every time the scenePhase changes (you already have the .onChange to do that part). Print out the phase, and the count of items in iOSAppConnector.items. Then, run through every possible scenario, e.g. while the app is open an on the screen, when it's been opened and is now in the background etc. You'll be able to see what you did to make the scenePhase change, and may see what you have to do to correct the issue.

@Manuelinh0 What happens in Software Update? Is anything listed for update, but it fails to install, or is nothing listed to install? Can you turn off developer beta updates, and turn them back on? You could try wiping it and putting it back to iPadOS 18, then enabling developer betas again?

Two things: Have you tried other headphones? If so, do they exhibit the same issue? If so, then yes it's an issue. If not, then it's your headphones. Secondly, if it's an issue in the software, raise it in the usual way, via the Feedback Assistant: https://feedbackassistant.apple.com/ so Apple know about it, then post the FB number here.