I’m creating a new post because the situation has gone far beyond reasonable. My Apple Developer Program enrollment has been stuck in “Pending” status for almost a month. During this time, I have sent around 10 emails to Apple Developer Program Support. Result: ZERO REPLISES. NO EXPLANATIONS NO UPDATES. NO HELP. If you are experiencing the same issue — or have faced it before — please leave a comment or upvote this thread so it gets visibility. At this point, this seems to be the only way to get Apple’s attention. Apple, this situation needs to be addressed.

With macOS Tahoe, Launchpad has been replaced by an App Library–style mode within Spotlight. While the alleged intention is UX consistency across the Apple ecosystem, the result is both a catastrophic usability regression and a radical break in consistency with iOS and iPadOS. Predefined App Library categorization is functionally incoherent: On iOS and now macOS, Apple’s predefined App Library categories place apps with seemingly identical functionality into unrelated groups—for example, 3D scanning tools scattered across Education, Utilities, and Productivity. Instead of making apps easier to find, this effectively creates a labyrinth that users must traverse to locate apps whose names and icons they may not recall. However Apple defines its app categories, they are not only inconsistent but also hopelessly inadequate for the long tail of real-world applications and user workflows. Loss of user control: Launchpad enabled users to group and organize applications according to their workflows. This aligns with Apple’s own Human Interface Guidelines, which emphasize user control, discoverability, and predictable behavior. The new Spotlight interface removes that flexibility, locking users into predefined categories that both impede and mislead—and cannot be overridden. Consistency across platforms is broken: If the goal was to unify iOS, iPadOS, and macOS, this approach actually undermines consistency. On iOS and iPadOS, users can still rely on a customizable Home Screen—a Launchpad-like experience—as their primary way of launching apps. In Tahoe, that option has been removed. macOS now forces users to depend exclusively on Spotlight with App Library categories, while eliminating the very feature that was consistent across platforms. Catastrophic impact on my workflow: As an interdisciplinary artist working in 2D, 3D, and time-based media, as well as coding, I make extensive use of a constantly changing array of AI tools and experiment with many new apps and web services, which I often turn into Web Apps. I cannot possibly recall the names of every native and web app on my system. I need predictable access to groups of related tools. Tahoe’s new auto-categories split those apps apart arbitrarily, slowing me down and interrupting established workflows, forcing me to navigate the aforementioned labyrinth just to find what I need. Proposal: A constructive way forward High-level objective: Simply restore Launchpad—or restore the ability to customize app categories/folders and manually assign apps to them, overriding or augmenting the predefined categories. This ensures users can launch apps according to their workflow, without needing to remember exact names or icons. Possible solutions: Allow manual subfolders within Applications, represented hierarchically in Spotlight. Provide a fullscreen Launchpad-like organizer (with uninstall via long-click, etc.), either as a replacement or toggleable option. Retain Apple’s auto-categories for those who prefer them, but let users override or augment them with their own. In summary: Tahoe eliminates a working, consistent paradigm (Launchpad/Home Screen) and forces reliance on an App Library system that categorizes poorly and cannot be customized. This is both a step backwards in functionality and a break in cross-platform consistency. A constructive solution is to restore Launchpad—or at least restore the ability for users to organize apps in ways that fit their workflows.

After installing macOS Tahoe26.0 beta5 (25A5338b) or beta4, a memory and disk leak appears, likely caused by Spotlight indexing. The mds_stores process consumes up to 60 GB of RAM, while disk writes continue until an additional 50 GB is filled. Once the maximum is reached, the system frees the space and the cycle repeats, leading to severe memory leakage. In the available space, system data occupies as much as 150 GB. System Versions Affected: macOS Tahoe26.0 beta5 (25A5338b) and beta4. Reproduction Steps: Occurs immediately after booting up, with no additional user actions. Workaround: Booting into Safe Mode prevents the issue from occurring. Possible Cause: A bug in Spotlight indexing. In Safe Mode, Launchpad cannot search for applications, and no other issues have been observed so far. This strongly suggests that Spotlight indexing is the root cause. Potentially Affected Software: Developer-related tools such as Node.js, Maven, Vue.js, etc. It is possible that Spotlight is indexing developer project dependency directories (e.g., node_modules), which contain a large number of small files that do not require indexing, leading to this problem.

I noticed the water lock feature isn’t in the control center after updating to WatchOS 26

https://developer.apple.com/documentation/appstoreservernotifications/app-store-server-notifications-changelog#June-10-2024 ONE_TIME_CHARGE notify type running in a sandbox environment for almost a year, the feature is not yet available for production environment. The notification is already available in Google subscriptions. Our services often miss orders because of the absence of this notification. Can you give us an approximate time range?

Updated iPhone to 26 beta 2, everything is ok but battery, battery is changed, not original. My phone can't charge higher than 1% and turns off every 5 minutes, even connecting to wireless charger and cable at the same time don't work, restored iPhone thru iTunes.I hope I will be able to install new beta without any problems because loving the new design,hoping for the best. Thanks.

I set iOS 26 to install overnight, put my iPhone 16 Pro on the MagSafe charger, watched it charge just fine, and went to sleep. When I woke up the iPhone showed the “plug into power” dead battery screen. I took it off MagSafe and put it back on. A half hour later the phone was warm but still wouldn’t power on, just showed the battery screen with a little red in it. I took it off MagSafe and plugged it into my iPad charging brick with USB cable to give it more power, still it did not turn on. I tried holding all the buttons to try to force a restart but didn’t work. For anyone else encountering this, do this to enter DFU mode and restore it. I had to do it a few times before I got the timing right. Plug into your Mac and open Finder (or apparently a PC with Apple Devices or iTunes) Press and quickly release volume up Press and quickly release volume down Press and hold right side button When the battery disappears and screen goes black, hold volume down and continue holding side button After a couple seconds release the side button and continue holding volume down A prompt to allow connecting to the iPhone should appear after a couple seconds, click Allow, and it’ll say the iPhone entered DFU mode - proceed to restore the firmware

Hello everyone! I'm a newly graduated Computer Engineer living in Türkiye. I've been developing my skills in the iOS field for a while now. But sometimes I get lost and don't know what to do. I've just joined this community and have a request for you. I'd be very grateful if you could share your own advice, experiences you've had along the way, and how you successfully overcame them. I'm open to all kinds of positive or negative feedback. Self-improvement is paramount to me.

I've been trying to add my bank info to my account on AppStore connect, but nothing seems to work. Even searching for my bank does not work for me. Even tried searching for any other bank does not work. Keeps giving error messages. Anyone else experiencing this issue?

Hello, I'm having a serious problem registering for the Apple Developer Program, and I can't resolve it. I applied over two weeks ago, but I still haven't received an activation email. I've also tried using different credit cards, suspecting there might be a problem with my payment method. The main issues are as follows: My order/registration remains in the "processing" status, I haven't received an activation email, Apple Developer Program support isn't responding. I've already sent over seven emails to support, but haven't received any response or updates. Has anyone else encountered a similar situation?

Hello I was building my submission for contest and I noticed that my app built and ran fine on Xcode but didn't even build on swift playground, so should I be concerned about this, and where do the judges finally run and test our submitted playground is it in swift playground app or Xcode ??

Both Apple and third-party apps in CarPlay are not displaying properly after updating to iOS 26 public beta two. I submitted feedback, wondering if anybody else had this problem and have solved it. The only apps that appear to be working normally are map apps like Apple Maps, Google Maps and Waze. The others show only background, but if you tap on the touchscreen it will perform an action as if the tile/link is there, but invisible

What OS will a Swift Student Challenge submission run on? I want to use iOS 26 features but the version history for Swift Playground doesn’t show it being updated past the iOS 17.5 SDK. So, can I still use features from the iOS 26 SDK?

My app uses Foundation Models and Apple Pencil. The app runs great through Xcode; however, due to Apple Pencil support, it has to be run on a physical device. However, Swift Playgrounds on iPad doesn't support iOS 26. I was just wondering if this is something that can be mentioned in submission notes. eg. The app needs to be compiled in Xcode but run on a physical device.” Or should we expect iPadOS 26 support for Swift Playgrounds by the time of submission? Thank you!

Area: Software Update Type of Feedback: Application Bug Description Device: iPhone 13 Pro running iOS 26 Build environment: Xcode 16.4 Problem description: When a text field has secureTextEntry = YES and Password Autofill / Passkeys is active, the autofill panel is not included in the rect reported from the keyboard notifications (UIKeyboardFrameEndUserInfoKey or others). As a result, when calculating the offset to move the screen up and reveal the hidden input field, the field is not displayed correctly because the reported keyboard height is smaller than the actual visible height. Observed behavior: This only occurs on devices running iOS 26 built with Xcode 16.4. On previous versions of iOS, with the same settings (secureTextEntry and Autofill active), the rect correctly includes the autofill panel height, and the UI works as expected. I tested with both UIKeyboardDidShowNotification and UIKeyboardWillChangeFrameNotification, and in both cases the behavior is the same: the height is incorrect (smaller than expected with the autofill panel). What I expect / questions: That UIKeyboardFrameEndUserInfoKey (or the related notification) correctly reports the total area covered by the keyboard, including any password autofill panel, when secureTextEntry is active. That the new behavior in iOS 26 be documented if this omission is intentional, or otherwise considered a bug if it is not. If there is any official workaround suggested by Apple for developers affected by this issue while a fix is provided. Thank you for your support.

Hello everyone, I have already submitted my app playground for the Swift Student Challenge. After submission I noticed a few things I would like to improve and fix. Is it possible to withdraw my current submission and then immediately resubmit an updated version? Any clarification (especially from Apple staff or anyone who has done this before) would be very helpful. Thank you!

I am looking through the rules and terms and it just says Xcode submissions will be run on a simulator. Does this mean Mac Catalyst or can it be run on a iPad VM? Or more so should we specify in the comments on where to run it. Thank you!

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

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?

I've paid - and have the confirmation of subscription email. But when I try to enroll both on my iphone and macbook air - I get errors. on the iphone said could not complete enrollment. on the macbook it said "not available in your area" I am in australia and it should work. Does anyone know how to fix the enrollment bugs?