We have an app that connects to an external device that we developed in-house that measures electroencephalography (EEG), as well as PPG and IMU. This is not a medical device and we have stated that many times but the app review process keeps rejecting the app for the same reason 1.4.1 - Safety physical harm because they say it is connecting to a medical device. We have submitted documentation for FCC certification for safety but we do not have FDA certification because it is not used for medical purposes - purely wellness. Despite several messages explaining it is not a medical device the response is always the same without actually addressing any of the supporting documents we have sent. Any help to find a way to explain to the Apple team that not all EEG devices are medical and in fact most are NOT FDA approved would be appreciated as it seems like whoever is reviewing the app doesn't understand that.

We have developed an accessory that supports Find My. When using the Find My app to set it up, it occasionally gets stuck at the final " setting up"" interface. The app just stays like that. We would like to know what could cause this situation and how to resolve it. Thanks a lot.

iOS 26.2 Beta 23C5044b Phone's battery reports 0% Health, leaving it on multiple chargers (high/low wattage) doesn't change anything. Icon changes to charging. Changed the battery with a high quality aftermarket of ~70% charge, same issue. Unable to remove beta or update to RC2 due to the 20% minimum required... not sure what to do.

where can i get apple's all device hardware vid and pid ?

as i want to tract activity of iphone user using core motion framework , guide me through .

Since 17.4 Dev Beta 2, I have been having Bluetooth issues. I had hoped it would have cleared up but even in 17.4.1 it continues. Airpod and Echo Auto are the only 2 audio devices I have. The audio will become chopping, rubber band or sound robotic and sometime completely disconnect. While driving it will occur on both audio devices. Sometimes I'm stopped at red light and the issue occurs. The phone is less than 3 feet from the device at all times. I have read forums and removed and readded the devices but that did not help. I really do not want to have to reset my phone since my 2FA apps do not recover in a restore. Anyone have any suggestions?

Is it mandatory to use classic Bluetooth (Bluetooth Classic) to connect game controllers that support Apple’s MFi games and Arcade games, or can game controllers be developed using only Bluetooth Low Energy (BLE) for such accessories?

New projects in Xcode do not include an Info.plist. Where do I put the IDs for Supported External Accessory Protocols?

Receiving "The disk you attached was not readable by this computer." for an external USB recorder that worked with MacOS 14 Aiworth voice recorder.

Hello! We currently require the development of an iOS system for encrypting and authorizing photos, videos, voice memos, or other files stored on our devices to a connected USB-C storage. The encrypted files can be accessed through authorization. We have already encrypted and authorized the files to be stored on the app's mobile storage, and cannot directly store them to USB-C (this requirement is based on the Apple camera RroRes, which uses external storage for direct storage). We are seeking technical support from Apple.

Apple intelligence isn’t working, it says i have it but that’s it’s also downloading. Whenever i do have it on none of the features work, what do i do

Hi everyone, I try to understand Matter Support and how to get the onboardingPayload from the commissionDevice func. I followed the docs from https://developer.apple.com/documentation/mattersupport/adding-matter-support-to-your-ecosystem I also added the Matter Extension, added the NSBonjourServices, included the Matter Extension and did .perform(). The UI shows up correctly and I can scan the QR-Code, which shows pair it to your ecosystem. I launched the extension via Xcode in my application, but the RequestHandler isn't triggering. Did I miss something? Can someone point me into the right direction please?

I have a 2019 iMac 5K with an Apple 2TB internal, which I've been using since June 2019. DriveDx says the drive is working correctly and has 94% of lifetime remaining. When I switched from Sonoma to Sequoia, I backed everything up several ways, reformatted the internal, installed 15.0 from a USB drive, copied all of my data back and then installed each app one by one. For years I generally ran Disk Utility every couple of weeks and never had any problems. Because I've had lots of software problems running Sequoia, I've tried just about every version of the OS--release, public beta and developer beta. Right now I'm running 15.3 beta 2. When I installed this version, I reformatted the internal drive, installed 15.3 beta 2 and restored my programs and data from Time Machine. After that I ran Disk Utility. At the top level, Apple SSD SM2048L..., showed no errors and neither did any of the drives below the top. But after a few days if I run Disk Utility, Container disk3 shows errors, as does the bottom Macintosh HD. See bellow. And this happens after every fresh install. Good and clean for a couple of days, then the errors in Disk Utility start showing up. These errors have apparently caused no problems, but I'd like to get them fixed. How do I do it as Disk Utility is not fixing them? And because I'm having these errors in DU is my internal going bad? I know Disk Utility shows it's performing repairs and the disk is OK afterward, but it's apparently not as I get the same result every time I run Disk Utility. Thank you for your help. /Users/imac4/Desktop/Disk Utility/Screenshot 2025-01-16 at 8.42.58 AM.jpg

My phone broke a little bit ago, with the screen either flashing green or it being green continuously. I asked somebody who would know and he said that the connection from the motherboard to the screen is messed up. It’s refurbished so that makes sense. Since then, the issue has gone away. it stopped a few days ago but I have insurance on it through a third party and I’m wondering if I should still make a claim.

I am working on an iOS application that relies on CoreMotion Attitude, and I need clarification regarding the behavior of reference frames. According to the documentation, when setting the attitude reference frame to CMAttitudeReferenceFrameXTrueNorthZVertical: The Z-axis of the reference frame is vertical (aligned with gravity). The X-axis of the reference frame points to the geographic North Pole (True North). When a device’s orientation matches this reference frame, the roll, pitch, and yaw values reported by CMAttitude should be (0,0,0). However, in my testing: When I align the device’s position with the CMAttitudeReferenceFrameXTrueNorthZVertical reference frame by orienting the screen (device Z-axis) upward and the right side (device X-axis) toward north, the yaw value reported by CMAttitude is 90 degrees instead of the expected 0 degrees. To have CMAttitude report yaw as 0, I must instead orient the top side (device Y-axis) toward north. This seems to contradict my understanding that the X-axis of the device should be aligned with True North, to have the device match the attitude reference frame and have roll, pitch, and yaw values reported by CMAttitude should be (0,0,0). What I'm missing? Thank you for your time and assistance.

We just updated our ATS to the latest 8.3.0 version and tried to run the iAP2 Session Test via BPA100 Bluetooth Analyzer and we are experiencing this EXC_BAD_INSTRUCTION. This same test still seems to work on ATS version 6. Please advise. Process: ATS [1782] Path: /private/var/folders/*/ATS.app/Contents/MacOS/ATS Identifier: com.apple.ATSMacApp Version: 8.3.0 (1826) Build Info: ATSMacApp-1826000000000000~2 (1A613) Code Type: X86-64 (Native) Parent Process: launchd [1] User ID: 501 Date/Time: 2025-01-27 11:05:21.1334 -0800 OS Version: macOS 15.2 (24C101) Report Version: 12 Bridge OS Version: 9.2 (22P2093) Anonymous UUID: 098E2BB5-CB98-CA1C-CEFE-188AF6EFE8CF Time Awake Since Boot: 9700 seconds System Integrity Protection: enabled Crashed Thread: 2 com.apple.ATSMacApp.FrontlineFrameworkInterface Exception Type: EXC_BAD_INSTRUCTION (SIGILL) Exception Codes: 0x0000000000000001, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 4 Illegal instruction: 4 Terminating Process: exc handler [1782]

Battery health reduced to 89 from 98 within 2 months on iPhone 15 Pro and Cycle Count is just 314. Is it the software update doing this?

For the "Required device capabilities" in my info.plist I have: iPhone Performance Gaming Tier iPad Minimum Performance M1 But a beta test just informed me they cannot install on iPhone 16 Pro Max due to "incompatible hardware" I need to limit to iPhone 15 or newer and M1 or newer. I read that iPhone Performance Gaming Tier also limits iPads to M1 here: https://developer.apple.com/forums/thread/737946 Perhaps I should only use "iPhone Performance Gaming Tier" and by using "iPad Minimum Performance M1" it is not allowing it to be installed on an iPhone? It would be very nice if I could see what devices are supported by the current settings.

So the battery level value is in accurate returns the battery percentage in multiple of 5 values e.g. battery percentage is 42 but the api returns it as 40. So please fix the issue if possible because i checked that the devices running iOS versions below 17 appear to be working fine.

Since tvOS 18.4 beta (22L5218l) i have the issue that When I turn off an Apple TV, the Apple TV and the connected TV turn off, but after a few seconds the devices start again. This never happened before. But now it is happening with 3 different Apple TV generations on 2 LG and 1 Telefunken TVs. All 3 Apple TV devices have been updated to tvOS 18.4 beta (22L5218l) and since then show this error.