Use the formatting toolbar! if #available(iOS 26.0, *) { let blurEffect = UIBlurEffect(style: .systemUltraThinMaterial) appearance.backgroundEffect = blurEffect tabBar.directionalLayoutMargins = .zero tabBar.preservesSuperviewLayoutMargins = false appearance.backgroundColor = .clear tabBar.layer.allowsEdgeAntialiasing = true tabBar.clipsToBounds = false tabBar.isTranslucent = true } tabBar.standardAppearance = appearance

Don't use comments to respond; they don't mark the thread as being updated. Anyway, you'll definitely have to get in touch with Developer Support if the options aren't there for you.

When you say you unpaired the Watch, do you mean you actually unpaired it from the iPhone or unpaired it in the Devices & Simulators window in Xcode? I recently had a bunch of those errors, and the fix for me was to do the following. Note, this took about 12 hours overnight for it to "self-heal," so you may also have to try again in the morning. Unpair the Watch in Xcode, in the Devices & Simulators window. Click the + button in the bottom-left of that window. Your Watch will not be listed. Close the windows and quit Xcode. Re-launch Xcode. Re-open the Devices & Simulators window. If your Watch is not automatically listed as a disconnected device, click the + button again. If your device is listed and available to set up, click Next to do so. Your Watch should now work normally with Xcode. If your device is not listed, quit Xcode, wait about 12 hours, and try again. I don't know why it took so long, but I was sitting there trying to add it again for at least an hour, quitting Xcode and retrying, rebooting the Mac and retrying, to no avail. But the next morning, it just worked.

Not sure if this is how you do it, but in the "Detalles de la membresía" section, there should be a blue link that says (in English) "Update your information". It has a little + sign in a circle. When you click that a dialog box should appear with an option to convert to an individual account. If that option is there, click it and follow any on-screen instructions. If it's not there, then you may have to get in touch with Apple Developer Support via this page: https://developer.apple.com/contact/ and ask that your account be changed to an individual account. That's all I can do to help you, sorry. I've never had to do this myself.

As far as I understand Core Data - and who really understands it, really? - an entity will have an ObjC class generated for it, so you've just unfortunately used a name that Apple is now using for a class in one of their private frameworks on iOS 26. As you've seen, renaming your entity fixes the issue because your new entity's generated class no longer has the same name, and so the compiler isn't seeing two classes with the same name. As a general rule, avoid using names anywhere in your code that start with three capital letters, i.e. PSSegment. It's tempting to use your own name to name classes, and in your case perhaps you would name something HHSegment (because: HeezerHiker). Apple use this convention, so you should try and avoid it. For example, NSString == NS String == NextStep String. You could use something like HHEntitySegment, or the name of your app, i.e. MyAppSegment.

You can't downgrade from a later version of iOS to an earlier version. Think about it. Let's say there's a file that some process uses, and in iOS 18 it had three bits of data in it: A,B,C. iOS 26 added a fourth bit of data: D, so now that file has: A,B,C,D. If you were able to take your iOS 26 data and feed it back into iOS 18, iOS 18 would need to know exactly what iOS 26 did to the data in order for it to remove "D". iOS 18 doesn't know about iOS 26, but iOS 26 knows about iOS 18 because it knew that in that particular file it needed to add "D" in order for that file to continue working on that app in iOS 26. iOS 18 cannot use data files from iOS 26. The only way to do what you want is to install iOS 18 and restore from an iOS 18 backup that you took from before you upgraded to iOS 26. However, that backup clearly won't have anything you've done on the phone since you upgraded to iOS 26. However, I'm not even sure Apple are signing older versions of iOS now that iOS 26 is out, meaning you may not even be able to install iOS 18 anymore.

You have two profiles on here, then? So who's gaslighting who? You have highlighted some domains listed within the output of swcutil, and assumed some nefarious folks are adding thing s to your private device. Where's the proof? What's wrong with *.events.shazam.apple.com? Apple owns Shazam. What's wrong with a service forcom.apple.FaceTimeLinkTrampoline using the domain facetime.apple.com? As I said before, you are simply misunderstanding things. If you think otherwise, why not call Apple? Why not go into a store and ask them to check your phone and see what's going on? Or, how about asking another iPhone user to show you their swcutil output and see whether the output of the logs matches? If it does, go to ten more users, then a hundred, then a thousand. If such large numbers of people are experiencing this 'hack' into their devices then Apple surely has an issue on its hands... But right now, you are misunderstanding the output of a command, that's all.

These forums aren't the place for showing off your work.

Rather than just posting in the forums about this issue - and remember, in the forums you're mainly talking to other developers like you - you should raise a bug. You can do that here: https://feedbackassistant.apple.com/ Post the FB number here when you're done.

No one is rifling through your files on iCloud. iCloud Drive uses various storage systems in the background to store your data, one of which is likely AWS. Only you have access to the files you store on iCloud Drive. Nothing you have presented here offers any shred of evidence that someone is rifling through your files. You are simply reading some logs incorrectly. You're intelligent enough to run sysdiagnose (or some rubbish AI suggested you do this), but you can't read the logs properly? Stop being so paranoid. Oh, and can you tell us the exact site where you've been contacting Apple Support so we can determine whether it's a "spoofed site" or not? And the phone number you called that got you a "Siri operator"? (Why do these forums keep attracting this sort of nonsense post?)

We'd need to see some code to see whether you've done something wrong, or at the very least a GIF showing the issue in action. If supplying code, please use the formatting tools so that the code is readable.

Have you raised a Feedback report? If not, please do so at 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. Your question is more of a product support one, so I'd suggest you ask it over at the Apple Support Forums. Thanks.

This page should help you: https://support.apple.com/en-gb/102662

Again, these are the Developer Forums, where developers of third-party apps for Apple's platforms ask each other for hints and tips on coding. If you have a suggestion, you should raise it at: https://feedbackassistant.apple.com/