My client has provided me with admin access to the Apple Developer console. However, when I log in, I am prompted to enroll in the Apple Developer Program. Should I proceed with the enrollment myself, or does the client need to complete the enrollment from their own account?

OS macOS 15.4.1 What steps will reproduce the problem? (0) Make sure you have other third-party browsers on your computer, and that their names start with a letter before "M", for me it is Arc browser. (1) Install a previous version of Edge Mac Canary (it can be downloaded from official web site:https://www.microsoft.com/en-us/edge/download/insider?cc=1&cs=426423789&form=MA13FJ). If you don't have an older version, you can download and save the current version, and then try the below steps after a day or two. (2) Eject the DMG from the Finder Sidebar. (3) Switch to the System Settings panel, set the "Default web browser" as Edge Mac Canary just installed. (4) Click a URL link from Notes, it will open in Edge Mac Canary. (5) Navigate to "Settings"->"About Microsoft Edge" in Edge and wait for the update information to show that update is complete (it will auto update to the latest version). (6) Check current result of "Default web browser" in System Settings again. What is the expected result? The "Default web browser" should still be Edge Canary. What happens instead? The "Default web browser" in System Settings will change to Arc. But this time, when you click the link from Notes, it will open in Safari, which means that "Default web browser is shown as Arc, but it is actually Safari. It is worth noting that if you start Edge Mac in step (3) and then set it as Default Browser in the "edge://settings/defaultBrowser" page, this problem will not occur after the update is completed. Chrome Mac has the same issue. Other Please see the video (https://youtu.be/ymWAanLqz1Y) for more details.

I have filed 27 bug reports against macOS using Feedback Assistant and none have had any sort of follow-up. I'm wondering if anyone at Apple looks at these reports? A few of these involve accessibility features that are not working (for example: speak announcements doesn't work -- and yes, my feedback is much more detailed than "doesn't work"). I would have thought issues with accessibility would be a high priority for Apple to fix quickly. Another report is that Grapher uses black text on dark gray making it very difficult to see the formula you enter. This should be a one-line code fix. These two, and 25 other bug reports have seemingly been ignored. Several of these reports indicate more than 10 similar reports, yet go unfixed. Leading me back to my opening question -- does anyone at Apple read these reports? I'd like to think I'm helping Apple to deliver a more perfect product but I feel like I'm wasting my time writing detailed bug reports. Is there another way to bring these to Apple's attention?

Hi, my fusion drive is not recognized with the latest tahoe developer beta. is it official or it's a bug ? it works when I reboot into previous verion of macOS. APFS Containers (6 found) | +-- Container disk3 AD9B43A5-66E7-4696-8183-8FD75230DAD2 | ==================================================== | APFS Container Reference: disk3 | Size (Capacity Ceiling): 994662584320 B (994.7 GB) | Capacity In Use By Volumes: 899491840000 B (899.5 GB) (90.4% used) | Capacity Not Allocated: 95170744320 B (95.2 GB) (9.6% free) | | | +-< Physical Store disk0s2 8183A70B-64A7-434E-85A4-5FA40F692BC9 | | ----------------------------------------------------------- | | APFS Physical Store Disk: disk0s2 | | Size: 994662584320 B (994.7 GB) | | | +-> Volume disk3s1 295CC2B7-EFA6-4706-8A6F-4C8FDC455857 | | --------------------------------------------------- | | APFS Volume Disk (Role): disk3s1 (System) | | Name: Macintosh HD (Case-insensitive) | | Mount Point: Not Mounted | | Capacity Consumed: 12576616448 B (12.6 GB) | | Sealed: Yes | | FileVault: Yes (Unlocked) | | Encrypted: No | | | | | Snapshot: 9B660F16-30C2-4B5E-911A-5B6250626C0C | | Snapshot Disk: disk3s1s1 | | Snapshot Mount Point: / | | Snapshot Sealed: Yes | | | +-> Volume disk3s2 766CF320-F93A-42D0-9660-F48E5B6C3B1A | | --------------------------------------------------- | | APFS Volume Disk (Role): disk3s2 (Preboot) | | Name: Preboot (Case-insensitive) | | Mount Point: /System/Volumes/Preboot | | Capacity Consumed: 7744360448 B (7.7 GB) | | Sealed: No | | FileVault: No | | | +-> Volume disk3s3 2A8ABBAC-435B-493E-A1AE-2DCCE5966207 | | --------------------------------------------------- | | APFS Volume Disk (Role): disk3s3 (Recovery) | | Name: Recovery (Case-insensitive) | | Mount Point: Not Mounted | | Capacity Consumed: 1165090816 B (1.2 GB) | | Sealed: No | | FileVault: No | | | +-> Volume disk3s5 5339AAF8-3765-458A-AB1F-930AFD53CAA3 | | --------------------------------------------------- | | APFS Volume Disk (Role): disk3s5 (Data) | | Name: Macintosh HD - Data (Case-insensitive) | | Mount Point: /System/Volumes/Data | | Capacity Consumed: 875640164352 B (875.6 GB) | | Sealed: No | | FileVault: Yes (Unlocked) | | | +-> Volume disk3s6 99818862-6CC2-4805-9C96-5837D666543F | --------------------------------------------------- | APFS Volume Disk (Role): disk3s6 (VM) | Name: VM (Case-insensitive) | Mount Point: /System/Volumes/VM | Capacity Consumed: 2147524608 B (2.1 GB) | Sealed: No | FileVault: No | +-- Container ERROR -69808 | ====================== | APFS Container Reference: disk5 | Size (Capacity Ceiling): ERROR -69620 | Capacity In Use By Volumes: ERROR -69620 | Capacity Not Allocated: ERROR -69620 | | | +-< Physical Store disk4 (No UUID) | | ------------------------------ | | APFS Physical Store Disk: disk4 | | Size: 3200631791616 B (3.2 TB) | | | +-> No Volumes | +-- Container disk7 B400D344-9D63-4168-BA45-3883D02FF515 | ==================================================== | APFS Container Reference: disk7 | Size (Capacity Ceiling): 499793244160 B (499.8 GB) | Capacity In Use By Volumes: 40511234048 B (40.5 GB) (8.1% used) | Capacity Not Allocated: 459282010112 B (459.3 GB) (91.9% free) | | | +-< Physical Store disk6s2 9458DABF-09A9-4A8A-A5A1-EF5B0FBD82FC | | ----------------------------------------------------------- | | APFS Physical Store Disk: disk6s2 | | Size: 499793244160 B (499.8 GB) | | | +-> Volume disk7s1 2F2C63B5-69D1-4F8E-B720-1B72B743E752 | --------------------------------------------------- | APFS Volume Disk (Role): disk7s1 (No specific role) | Name: Icy (Case-insensitive) | Mount Point: /Volumes/Icy | Capacity Consumed: 40350416896 B (40.4 GB) | Sealed: No | FileVault: No | +-- Container ERROR -69808 ====================== APFS Container Reference: disk9 Size (Capacity Ceiling): ERROR -69620 Capacity In Use By Volumes: ERROR -69620 Capacity Not Allocated: ERROR -69620 | +-< Physical Store disk8 (No UUID) | ------------------------------ | APFS Physical Store Disk: disk8 | Size: 22000969973760 B (22.0 TB) | +-> No Volumes

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?

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.

Inhouse distributions apps stopped working after upgrading to version to iOS 18.1.x My issue all is inhouse distributions apps, when I open the application it will force stop. stopped working after upgrading to version 18.1.1. This has happened on multiple iPhones. Some users able use the application on same OS version but application is not working on newly downloaded device. iPhone, then updated to version 18.1.1, they app would not work. We deleted the app and the Enterprise App trust was gone. Then we installed a new version of the app. The phone did not prompt us to trust the Enterprise app again and the app it would open for a second then close. I believe when the app was deleted the Enterprise App was deleted, it’s not actually deleting certificates, because re-installation is not asking to trust certificate again.

Buenos dias: tengo el ultimo iphone 16 plus y desde que hice la ultima actualizacion no me deja desviar las llamadas. Me queda todo el tiempo en procesando.

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 ?

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.

Hello, why is apple won’t adding Just-In-Time compiler to ”Emulators” in the app store. And/or hypervisor for newer devices. i feel like UTM (which is a PC Emulator) or other Apps that emulate need JIT to work properly, and will consume significantly less battery to emulate/virtualize, And will have a noticeably better performance than just not enabling JIT, and by the way jit is already being used on iPadOS/iOS 18.3/18.3.1 and newer/older version of that so being enabled by the choice of the developer of the App is more convenient than doing it with tools. and by the why apple wont let emulators on iPads and newer iPhones do hypervisor, it’s better than JIT but requires a good cpu, like making it available to people with newer/powerful devices, hypervisor is better than JIT by a lot and removing it in iPadOS/iOS 18.4 was an unnecessary choice?, becuase it had a better potential in virtualization instead of emulating, and I feel like enabling it In M1-M2 iPads and A14-18pro and newer devices is just better from having it disabled, to unlock the fullest potential of the iPad it needs to have a app or something to do instead of just running high graphics games/or Apps.

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!

Hello everyone. Can I download ios 17 on a regular iphone x, not an xs, but an x? How can I do this using the developer program?

We plan to use signals emitted from iBeacon to perform region detection in an app currently under development. We would like to know if region detection (didEnterRegion) can be performed when the app is in certain states. Region detection must be performed reliably. Is it possible to perform region detection in all of the following situations? • When the app is in the foreground • When the app is in the background • When the app is force-closed • When the smartphone is in sleep mode • When the smartphone is restarted Translated with DeepL.com (free version)

Content written a day earlier and saved, is today only showing partially. It seems the software did not save the content completely.

I have been trying to make phone calls using the Phone app on my MacBook Air. The calls will go through with absolutely no problem. If it's a service that needs touch-tone phone prompts, the tones do not register with the automated system. I have also just noticed that when a call rings on my computer (and it IS ringing), there is no way to answer it. I am running Tahoe Beta 26.1 Any thoughts?

Zoom is crashing when clicking the chat button. I am using iOS 26.1. I have already powered down and reinstalled the app.

Hi I experience this problem after update to the newest developer beta software on my iphone 17 pro: blackmagic camera said "storage full" although it is not final cut camera said "close and open the app again" It still works with prores (not raw). Anyone has the same problem as mine? I did try uninstall and reinstall the app and also restart the phone, try using different external ssd drive but nothing works.

We're sending the spcData payload to our fairplay key server (version 5.1) with the base64 encoded string of our fairPlay.cer that was downloaded from our developer portal and we're getting a spcVersionErr (-42580) for the spc version. The value that is being received by the key server seems to be 813827283 when it should be either 1 (base_constants.SPCVersion.v1.rawValue) or 2 (base_constant.SPCVersion.v2.rawValue). We're assuming we're encoding the fairplay.cer incorrectly. Any insight from anybody would be appreciated.