Your updateLocal() func has a sort descriptor with two of the same values: fetchRequest.sortDescriptors = [NSSortDescriptor(keyPath: \Project.name, ascending: true), NSSortDescriptor(keyPath: \Project.name, ascending: true)] - does this do anything in particular? Anyway, you're doing an awful lot work in what should be a simple Core Data update function. Have you tried retrieving from Core Data all the projects that need updating, doing your updates to the various bits, and then saving the context in one go?

They are permanently removed in favour of the new windowing. However, if you want them back I suggest you raise a feedback report requesting their return. It's unlikely to happen, but if enough people call for it, Apple might change their minds and find some way of implementing them again. https://feedbackassistant.apple.com/

Install macOS Sequoia onto the partition and get it setup minimally, then enable beta updates in that partition's System Settings, and go through the install.

You should probably raise this as a bug in the usual way. It won't really get progressed if it's only posted in these Developer Forums. You need to raise each issue you find separately at https://feedbackassistant.apple.com/ You can post the FB numbers here if you want, so that others can link to them.

You should probably raise this as a bug in the usual way. It won't really get progressed if it's only posted in these Developer Forums. You need to raise each issue you find separately at https://feedbackassistant.apple.com/ You can post the FB numbers here if you want, so that others can link to them.

"It is showing error or something" How about you tell us the exact error it's showing? We can't really help you without that crucial bit of information. Anyway, can't you just turn beta updates back on?

You should probably raise this as a bug in the usual way. It won't really get progressed if it's only posted in these Developer Forums. You need to raise each issue you find separately at https://feedbackassistant.apple.com/ You can post the FB numbers here if you want, so that others can link to them.

You should probably raise this as a bug in the usual way. It won't really get progressed if it's only posted in these Developer Forums. You need to raise each issue you find separately at https://feedbackassistant.apple.com/ You can post the FB numbers here if you want, so that others can link to them.

The app's specific purpose is offering customized content, and we need the users to register for that customization. If we can't offer the customized filtering, the app has no sense for us. Why can't you just show the news articles without someone registering? The USP is that your app allows the user to customise their news, and to do that they have to register, so just explain that in the app. Show all the news articles, and tell the user that if they register they can customise what they see. Explain how they can hide sports stories if they aren't interested in sports, or hide politics if they don't want to see politics stories. That seems quite simple to do. Personally, any app forcing me to register before I can see what the app looks and how it works is a definite no-no. It's a poor user experience.

"kindly solve the issue asap" -- bit rude. Anyway, you should probably raise this as a bug in the usual way. It won't really get progressed if it's only posted in these Developer Forums. You need to raise each issue you find separately at https://feedbackassistant.apple.com/ You can post the FB numbers here if you want, so that others can link to them.

You should probably raise this as a bug in the usual way. It won't really get progressed if it's only posted in these Developer Forums. You need to raise each issue you find separately at https://feedbackassistant.apple.com/ You can post the FB numbers here if you want, so that others can link to them.

There's really no need to post this three times. If you need to update your original post, you have a one-hour window in which to do so. If you're outside that window, just add a reply to the original post. Duplicate posts clutter the forums.

Closing apps is not necessary on iOS and hasn't been for years. When you exit an app, the app gets a few seconds to finish what it needs to do - save a game in progress, stop a timer etc. - and then the system suspends the app. It takes up no memory and processing power by sitting in the background. Some apps do run in the background, like Mail, Messages, and Music, because you want to be able to receive emails and messages without the app being in the foreground. Other apps can do this, too, but the main point stands - it is not necessary to 'kill' an application. By killing an app you actually use more power because when you relaunch it the app has to do its initial setup again. This overhead happens every time you launch the app from cold. Launching it from the background uses far less energy. So, killing an app actually uses more energy. There is no reason to close all apps in the background. As a final point, you're in the wrong place. 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/ but take note of what I've said above - your suggestion is without merit, sorry.

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

Right. You've installed a beta version of iOS 26 on your iPhone. There are going to be issues. If CarPlay is a definite requirement, then you should downgrade your iPhone back to iOS 18.