Any help will be greatly appreciated. Trying to build a calendar/planner app for public school teachers. Classes are held on multiple dates so there is a need for swiftdata to save multiple dates. There are lots of tutorials demonstrating a multidatepicker but none of the tutorials or videos save the dates, via swiftdata. My goal is to save multiple dates. Step 1 is to initialize mockdata; this is done a class called ToDo. var dates:Set = [] Step 2 is the view containing a multidatepicker and other essential code Step 3 is to save multiple dates using swiftdata. Lots of tutorials, code snippets and help using a single date. But after almost 2 weeks of researching youtube tutorials, and google searches, I have not found an answer on how to save multiple dates via swiftdata. Also, I don't know how how to initialize the array of for the mockdata. Here are some code snippets used but the initialization of the array of DateComponenets doesnt work. And saving multiple dates doesn't work either @MainActor @Model class ToDo { var dates:Set<DateComponents> = [] init(dates: Set<DateComponents> = []) { self.dates = dates } } //view struct DetailView: View { @State var dates: Set<DateComponents> = [] @Environment(\.modelContext) var modelContext @State var toDo: ToDo @State private var dates: Set<DateComponents> = [] MultiDatePicker("Dates", selection: $dates) .frame(height: 100) .onAppear() { dates = toDo.dates } Button("Save") { //move data from local variables to ToDo object toDo.dates = dates //save data modelContext.insert(toDo) } } } #Preview { DetailView(toDo: ToDo()) .modelContainer(for: ToDo.self, inMemory: true) }

Its normal to have connections to developer.apple.com on an device not in developer mode?

Hey everyone. Ever since installed OS26 (and 26.1 now) - whenever I fast play any video on 1.25x, 1.5x, 2x on the AppleTV - the audio gets massively distorted on HomePods. Be it on YouTube, Difuse, or any supporting app. I even tried mirroring from iPhone -same issue. Anyone else experiencing the same? I noticed no posts about troubleshooting.

Installer hangs during installation of Epson iProjection app on macOS 26 (Tahoe) When running the installer for Epson iProjection Ver.4.03 on macOS 26 (Tahoe) RC, the installation process hangs midway and becomes unresponsive. Run the installer for Epson iProjection Ver.4.03 from the following link: https://support.epson.net/setupnavi/?LG2=EN&OSC=WS&PINF=vpapp&MKN=EB-770Fi The installer hangs during the installation process and does not proceed. (Please refer to the attached screenshot for details.) The installation should complete successfully without hanging. <Version / Build> macOS 26 RC (25A353) The installation error log is as follows: RemotePlugin: Epson iProjection Ver.4.03 terminated with error: Error Domain=com.apple.ViewBridge Code=17 "(null)" UserInfo={com.apple.ViewBridge.error.hint=connection to view service became invalid -- benign unless unexpected, com.apple.ViewBridge.error.description=NSViewBridgeErrorDisconnection} Is this behavior expected due to changes introduced in macOS 26? Are there any recommended workarounds or mitigation steps?

I have an app with a small but devoted following. It has not been upgraded since 2022 and has been working very well. On iOS 26 it crashes almost at startup. After hooking up to Xcode and running I get this message in the console: objc[64686]: Class PSSegment is implemented in both /System/Library/PrivateFrameworks/PolarisGraph.framework/PolarisGraph (0x291ed9f78) and /private/var/containers/Bundle/Application/08486FCF-548A-467C-8BA3-D722734463FC/HikeTracker.app/HikeTracker.debug.dylib (0x101d309e8). This may cause spurious casting failures and mysterious crashes. One of the duplicates must be removed or renamed. PSSegment is the name of an entity in my Core Data managed object model. If I refactor it to P_Segment the app starts. PolarisGraph means nothing to me. The "PS" stands for Persistent Store, but in this case it seems that PolarisGraph is PSing in my sandbox. How can this happen? I'll attach the longer message that comes with the crash. error messages.txt

Hi, I'm here hoping for some help or advice in terms of a critical situation I'm currently facing. I want to change the copyright of an app, which was my previous app but now transferred to another company. In the Apple developer panel, is there anywhere that can change the copyright? Here is a quick summary of the app development, Software Vendor 1 developed the app, then transferred to Software Vendor 2, eventually the Client user(only paid for the app but don't have developer account) can use it. Now, I'm the Software Vendor 1 and has transferred the app to Software Vendor 2, but the copyright is still Software Vendor 1; and I want to ask Vendor 2 change the copyright to Client user directly as the Client user has bought the app. I’ve contacted Apple Support multiple times through mails. They just tell me to ask the Account Holder/Admin of the organization account that now owned the app to contact them in order to receive support. Then, I've asked Software Vendor 2 to contact Apple support, but have no response from Apple support after 1 week. My Case number is: 102708379460 This case is quite urgent for me, if anyone from the App Support team sees this post, or if any developers have experienced a similar situation and can offer advice, we would be truly grateful. Thank you in advance for your time and support.

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.

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.

Hi Ed Ford, thank you for your response. I tried to reply directly in the forum with the requested output, but I keep receiving an error message ("Your post couldn’t be saved. Please try again in a few minutes."). It seems I cannot currently post a follow-up reply. Just to notify you: I ran the command you suggested, but my shell reports zsh: command not found: devicectl. Thank you!

I tried to enroll some weeks ago, went thru the whole process, it eventually took by IDs, but now I'm stuck on "Enrollement not completed - You enrollment in the Apple Developper pogram could not be completed at this time." So, after 2 weeks, what's next ?

As l proceeded through the enrollment/membership. I found the price is fixed for US$99. At the end. What about Renewal. Is there any cost reduction for Apple Developers?

Some users of my app complain that it stops responding to touch after a while. The screen is still updating, and the app seems to be working normally otherwise. It just doesn't respond to any touches anymore. It is not a problem with the touchscreen itself, because the user is able to swipe up to get to the home screen, and then interact with other apps as normal. When re-opening my app, it is still unresponsive to touch. The only way to solve it, is to restart the app. Does anybody have a similar experience, and knows what could cause it? The app is based on UIKit, and still written in Objective-C, if it matters. The iOS version involved does not seem to matter, it happened with a couple of them.

Around October 17, our app was removed from the App Store, and we were later informed that our developer account would be terminated within 30 days. This was an unexpected and shocking notice for us. After carefully reviewing Apple’s Developer Guidelines, we conducted a thorough internal investigation and confirmed that we did, in fact, violate certain policies. However, we are unsure whether the Apple Review Team could give us an opportunity to make corrections—otherwise, our new apps will not be able to launch on the App Store in the future. The stated reason for our account termination was: “You provided fraudulent and/or false account information, documentation, or otherwise falsely represented yourself or your submitted app to Apple either during the account enrollment process or after the account was created.” After reviewing this issue, we identified two foolish and critical mistakes on our part: We registered our developer account using our Mainland China company, but used a Hong Kong company’s bank account for payments. (Both companies are under the same management, and we have submitted supporting documentation during our appeal.) Our official website, Privacy Policy, and Terms of Service also displayed the name of our Hong Kong company instead of the Mainland China entity used for registration. Despite these mistakes, we have continued to support our users through email and our Discord community, resolving most issues within 24 hours. We have never deceived our users or the Apple Review Team in any way. For us as developers, providing an excellent user experience has always been our top priority, and we have always aimed to follow Apple’s review and compliance standards closely. We sincerely hope that, given our situation, the Apple Review Team could grant us an opportunity to correct these issues. We will promptly register a new Hong Kong Apple Developer Account, and once our app is reinstated, we will migrate all relevant information to that new account to ensure full compliance moving forward.

Hello Apple Team, I love the existing keyboard shortcuts such as Control + Function + Left/Right Arrow which allow moving windows to the left or right half of the screen. It significantly improves window management and productivity. I would like to kindly request a similar feature to move windows across multiple monitors using a keyboard shortcut. This would be especially helpful for users with multi-monitor setups who want quick and seamless window transitions between displays without using the mouse. This enhancement could align with Apple's commitment to intuitive and efficient user experience, helping users manage their workspace more effectively. Thank you for considering this feature request!

so far the only issue I’m having since the update yesterday is my Bluetooth. Every time I try to use my Bluetooth headphones since the update, they either just stop working midway through playing a song or watching a video, etc., or they play a super high pitched noise that causes me to have to rip my headphones out of my ears.

In the public release of iOS 18.4.1 and iPadOS 18.4.1, external input support for keyboards and mice is critically degraded. This issue affects both Apple-branded and third-party HID-compliant devices, over both wired USB-C and Bluetooth. Tested Hardware: • iPhone 16 Pro Max (256GB) • iPad Pro (USB-C, latest gen), last gen iPad as well Affected Devices: • Apple Magic Mouse and Keys (wired USB-C/Bluetooth) • Redragon K580RGBPRO (Bluetooth/wired USB-C) • Razer Naga V2 Pro (Bluetooth/USB-C) Symptoms: • Severe keystroke delay and dropped input • Modifier keys (Shift, Command, Option) fail intermittently • Input degrades further with multiple HID devices connected • Mouse input via Bluetooth exhibits pointer lag and jitter • Occurs in all apps: Notes, Safari, Mail, text fields, password entries, etc. • Identical results using Apple USB-C cables Reproducibility: 100%. Clean boots, minimal background activity, and isolated environments (including Airplane Mode) do not resolve the issue. Identical behavior across both iPhone and iPad. Expected Behavior: All HID-compliant external input devices — particularly Apple-branded ones — should provide low-latency, reliable, and consistent input over both USB-C and Bluetooth, especially in a production iOS/iPadOS release. Actual Behavior: External keyboards and mice exhibit: • Lag • Dropped characters • Failed modifiers • Degraded mouse tracking Even with the latest hardware and clean configurations. Severity: Critical. This is a platform-level failure affecting I/O at the user interaction layer. Input reliability is non-negotiable — especially on $2000+ flagship devices using Apple’s own peripherals. Closing Note (for Apple engineering &amp; peer devs): This is not a beta regression — it’s a public release flaw that undermines iOS and iPadOS usability for power users, professionals, and accessibility communities alike. That Apple Magic Keyboard, Redragon, and Razer gear all fail equally and consistently should be a wake-up call. Apple: this needs to be escalated. Now. External input — one of the most basic subsystems in any OS — is broken on your highest-end devices.

iOS 18 System Bug Causes URL Scheme Failure A bug in iOS 18 causes URL Schemes to become invalid through the following steps, resulting in failure to open apps via URL Scheme. Reproduction Steps: Long-press the app icon Select "Require Face ID" Choose "Hide and Require Face ID" to hide the app Go to the App Library and locate the hidden app in the "Hidden" folder Uninstall the hidden app reinstalling the hidden app After reinstalling the app, all configured URL Schemes will become invalid, causing failure when attempting to open the app via URL Scheme. The issue appears to be that after uninstalling a hidden app and reinstalling it, the system fails to restore the app's URL Scheme functionality.

Hi, I have a ninth generation iPad updated to iPados 26 beta 3 but now it no longer updates to the latest version of iPados 26, what can I do?

Almost everytime, when I try to search apps in App library, the icons go invisible, o are showed for and instant to quickly go invisible.

After latest beta firmware update 11.4, the screen is non or less responsive. Right before the update everything was working like a charm. Tried unpairing, total reset as a new watch, but nothing solves the problem