I’m experiencing an issue on macOS Tahoe (Developer Beta, July 2025) related to the new “Allow in Menu Bar” section in System Settings. After uninstalling the application Backdrop (developer: Cindori), the entry com.cindori.Backdrop.Wallpaper still appears in the list of apps allowed to show in the menu bar, even though: — The app and all its associated files have been fully deleted. — The LaunchAgents files in ~/Library/LaunchAgents and /Library/LaunchAgents have been removed. — Preferences have been deleted via defaults delete com.cindori.Backdrop and defaults delete com.cindori.Backdrop.Wallpaper. — The system has been restarted. It seems the “Allow in Menu Bar” section keeps phantom references to apps or agents even after complete cleanup. Could you please confirm if this is expected behavior (perhaps for future reactivation) or a bug? Is there any official method or recommended command to permanently remove such residual entries from this list? Thank you very much for your help and clarifications.

We made a purchase to join the Apple Developer Program, but we have been waiting for 5 days and have not received any response such as an approval or rejection. Are you experiencing the same issue as well?

I’m looking for iOS and Apple Watch users to help beta test ChoreFit, a fitness app that transforms everyday chores into measurable workouts using NEAT (Non-Exercise Activity Thermogenesis) science. What it does: • Tracks chores like vacuuming, mopping, and laundry as real workouts • Syncs with Apple Health for steps, heart rate, and calories • Lets you start or pause chores right from your Apple Watch • Adjusts effort based on body weight and optional weighted vests What I need from testers: • Install via TestFlight (link provided once approved) • Use the app during normal household tasks • Share feedback on usability, Apple Watch sync, and calorie accuracy If you’re interested in movement tracking, fitness analytics, or wearable integration, I’d love your help validating and refining this app before public release.

Hello, In my App.xcdatamodeld I have an entity called File. When I am building the project with Xcode, file FileEntity+CoreDataProperties.swift is generated. After upgrading Xcode to version 26.0 (17A324), I am getting the warning: Public import of 'CoreData' was not used in public declarations or inlinable code Any idea how to get rid of this warning since it's a generated file and I can't see any option to change it?

Guideline 2.3.1 - Performance The app contains hidden features. Specifically, we still noticed that your app includes code which causes it to behave differently during the review process regarding web game presentation and payment. It would be appropriate to ensure that all features and functions in the app are visible and fully accessible during review. Guideline 3.1.1 - Business - Payments - In-App Purchase The app allows users to purchase digital content natively or via a web view in the app using payment mechanisms other than in-app purchase. Apps cannot include in-app payment mechanisms other than in-app purchase. Apps on the United States storefront may also include buttons, external links, or other calls to action to direct users to payment mechanisms other than in-app purchase. We have been rejected three times due to hidden functions and issues with web payment and web games. However, in the last package we submitted for review, it was confirmed that the code related to web games was removed, and the code related to web interaction JS bridging payment calls was also removed Dear experts, we sincerely invite you to offer your valuable suggestions. If you have any experience of meeting us, please share with us. We would be extremely grateful

I’m building a Swift Playgrounds app (.swiftpm) in Xcode 26.2 and I consistently see this warning, even on brand-new Swift Playgrounds apps created from the default template: “Skipping duplicate build file in Compile Sources build phase: /Users/.../.swiftpm/Media.xcassets” Everything builds and runs normally and all images/assets appear correctly, so it seems like it’s just an annoying warning. I’ve checked for duplicates and don’t see the asset catalog listed twice, but the warning still appears whenever I add an asset catalog to any playground project in Xcode. Is this warning safe to ignore for submission, and it won’t affect Swift Student Challenge eligibility?

I am building my app for iPhone users generally, and realized that maybe I should have had the iPad in mind since I read somewhere that the submissions will be judged on iPad. Should I be testing and tweaking on iPad now or can it be somehow ran on iPhone?

When I try to create a post in Apple Support Community, it forces me to create a new account (for some supersmart reason because my apple account is apparently not enough). In this process, I am required to pick a new username and choose my communications preferences. The next screen? 403 Forbidden Error page.

アプリ開発を依頼して公開中ですが、 アプリ開発会社が倒産し、連絡もつかず、 アップル社への年間料金の支払いができません。 登録アカウントがわかりませんので、どうしたらいいでしょうか？ よろしくお願いいたします。

Hello. I need to develop for iOS 18. I've recently updated Xcode and it says I have to download ios 26 platform. I don't need it, but I can no longer build my existing projects against ios 18, even though Xcode says it's still installed and used 13 days ago. How to I remedy this?

Hello Apple Developer Community, I need some assistance with my account. I created a new developer account for a new project I am working on, and paid the apple developer fee. Everything was working fine for a few weeks, I was able to get my app on TestFlight and invite testers to it, as well as push updates and get feedback. The testers were family/business partners. As of a few days ago, I was locked out of my account. I first tried resetting my password, and was then met with an email claiming my account was locked with no additional information. I am trying to understand how I can either unlock my account, or transfer my existing app to a new account, so that I do not have to bother my users with downloading a new app. Additionally, I would like some help in understanding how I can safeguard myself from this issue in the future, especially given this would not be fun if my app were published. Could anyone please assist me, provide me with any advice, or point me to a place where I could get support? I spent 25 minutes on the phone with apple support, and was treated excellently as I've come to expect of Apple, but unfortunately was not given any help as the support did not have additional information. I'm hoping I'm asking in the right place, and can get some help! Thanks in advance, Fritz

Hello Everyone, I reviewed many previous year's submissions posted on swift's student's challenge distinguished winners section and noticed that most of them or all of them were designed and implemented for iOS devices only so is it a valid option to design our playground apps solely to run and function on macOS only?

Environment: macOS 26.3 (25D125) Terminal.app 2.15 (466) Apple Silicon Input method: Japanese (Romaji) - built-in Kotoeri Issue: Terminal.app crashes consistently when typing Japanese text using the built-in Japanese input method (Romaji) and the input line wraps beyond the terminal width. Steps to Reproduce: Open Terminal.app with default profile (Basic) Set terminal window width to ~80 columns Start typing Japanese text using macOS built-in Japanese input (Romaji) Continue typing until the text wraps to the next line Wait a few seconds after the wrap occurs Terminal.app crashes Key info from crash report: Crash thread name: (input method 992 com.apple.inputmethod.Kotoeri.RomajiTyping) ASI: BUG IN CLIENT OF LIBMALLOC: memory corruption of free block Exception: EXC_BREAKPOINT (SIGTRAP) Stack trace involves: IMKInputSession_Modern setMarkedText → SendTextInputEvent → NSTextInputContext The crash occurs in _xzm_xzone_malloc_freelist_outlined called from _CFRuntimeCreateInstance → __CFStringCreateImmutableFunnel3 → +[NSString stringWithUTF8String:] Notes: Does NOT occur with paste input, only with live IME typing Does NOT occur with ASCII-only input Reproducible multiple times per week with normal Japanese usage iTerm2 does not exhibit this issue The crash appears to be a use-after-free or buffer miscalculation in Terminal.app's handling of marked text (未確定文字列) during line wrapping Has anyone else experienced this? Any known workarounds other than switching to iTerm2?

Title says it all, so I get to 5 minutes left, and then the error message 'failed to prepare update' appears. I've done this for about a week now and the same thing happens. Does anyone have any insight to this problem?

So I downloaded and installed iOS26 on my iPhone 15 Pro and after that it does not want to boot anymore. It shows a battery with one red line. Which is weird because before it restarted it had 80% of the battery and I had the power cable connected at all time. Now I can't boot it up anymore. Not even with the volume button up, down, power button trick. Please help!

noticed that when I use PHPickerViewController in iOS26, preselectedAssetIdentifiers not working. It doesn't pre-select an image. This is the code snapshot how I use it with UIViewControllerRepresentable Same code works in iOS18 but not iOS26 func makeUIViewController(context: Context) -> UIViewController { var configuration = PHPickerConfiguration(photoLibrary: PHPhotoLibrary.shared()) configuration.filter = .images configuration.selectionLimit = 5 configuration.preselectedAssetIdentifiers = ["some id from previous selected results"] let imagePicker = PHPickerViewController.init(configuration: configuration) imagePicker.delegate = context.coordinator return imagePicker }

Hello everyone, on August 31st, all the apps in my personal developer account were suddenly expired and deleted, I have not received any response from Apple. My apps are in compliance with Apple's policies. I then uploaded a new version and sent it to the review team, but I received the following error "There was an error processing your request. Please try again later." I have contacted Apple via Email and Phone but no one cares about my problem. Has anyone had the same situation as me, I am really worried.

.fullScreenCover(isPresented: $isShow) { Button(action : { isPresented.toggle() }){ Text("Choose") } .familyActivityPicker( isPresented: $isPresented, selection: $selection) .onChange(of: selection){ value in } } In the official version of iOS 18, when I click the Done button of familyActivityPicker, the fullScreenCover pop-up box will disappear.

I'm trying to understand how UIDevice.current.identifierForVendor behaves when an iOS app is restored via iCloud onto a different physical device. Context I'm building an app that needs to detect whether it’s running on a newly restored device (for example, after the user transfers their iPhone via iCloud setup). To do this, I save the value of UIDevice.current.identifierForVendor?.uuidString in persistent storage (e.g., UserDefaults). The question If I install my app on Device A, store the identifierForVendor value, back up the device to iCloud, and then restore that backup onto Device B, will the restored app see the same identifierForVendor value, or a new one? More specifically: Does iCloud backup/restore preserve the underlying “vendor” ID across devices? Is the identifierForVendor tied only to the bundle identifier and vendor prefix, or also to the physical device hardware? If the user deletes all apps from the same vendor, then restores them from iCloud, is the ID reset? What I’ve found so far Apple’s docs say: “The value of this property is the same for apps that come from the same vendor running on the same device. If the user deletes all of that vendor’s apps from the device and then reinstalls one or more of them, the value may change.” However, it doesn’t explicitly mention what happens after iCloud restore onto a new device. Goal I want to know if it’s safe to use identifierForVendor to detect a new device context (e.g., trigger a refresh of a Firebase token when the user’s device changes). Environment iOS 17+ (latest) Swift / Capacitor app bridge Testing between iPhone 14 Pro → iPhone 15 Pro (iCloud restore)

With ios 26 the chapter images are not updating anymore. At first I thought this is carlay related but it also occures when the phone is connected only through USB or bluetooth to play a podcast. I tried Apple podcasts and other apps like Pocketcast or audible. Same problem. The phone shows the correct chapter image while my car shows the inital image all the time. Even tried a different car :-) I checked focus and settings but found nothing related. With ios18 everything works fine. Any ideas?