Every now and then I get this very frustrating message on Feedback Assistant. For instance, in FB14696726 I reported an issue with the App Store Connect API. 4 weeks later, I got a reply, asking among other things for a „correlation key and Charles log“. I immediately replied saying that I didn‘t know what those are, and they replied After reviewing your feedback, it is unclear what the exact issue is. I pointed out that I had asked a question which was left unanswered, and they replied explaining what the correlation key is. Then I asked again what the Charles log is. They replied The Apple Developer website provides access to a range of videos covering various topics on using and developing with Apple technologies. You can find these videos on our Development Videos page: http://developer.apple.com/videos. I opened the link and searched for „Charles“ but there were no results, so I asked to kindly point me to the video answering my question. They replied 3 months later (today): Following up on our last message, we believe this issue is either resolved or not reproducible with the information provided and will now consider this report closed internally. This Feedback will no longer be monitored, and incoming messages will not be reviewed. This is not the first time I ask for clarification and get back a message basically telling me that „we won‘t answer any questions you may have and won‘t hear anything you still may have to say about this issue“. They didn‘t even ask me to verify if the issue is resolved or not, like they sometimes do. No, they just shut the door in my face. I just wanted to share this frustrating experience. Perhaps an Apple engineer wants to say something about it or a developer has had a similar experience?

Description When starting the iOS simulators on macOS-15 intel image, the following assertion happens: The same issue not showing for macOS 15-arm64 image. Here is the issue details: https://github.com/actions/runner-images/issues/10925 raised by multiple users. AVPIdentity: AppleVirtualPlatformHostKey.mm:234: Assert: platformExpert, value: 0 AVPIdentity: AppleVirtualPlatformHostKey.mm:234: Failed to get AppleVirtualPlatformARMPE service. The Simulators worked fine the day before the above issue was posted. What changed? Did something update?

Hey guys, my application has the following error: Issue Description The app exhibited one or more bugs that would negatively impact App Store users. Bug description: the "Entrar" button in the login screen was unresponsive. Review device details: Device type: iPad Air (5th generation) OS version: iOS 18.1.1 The problem is that the test is already done on the emulator and I cannot reproduce this error in any way. I've tried everything. Is there any way to restrict access to the iPad? Could anyone help me please?

I have make an app for company's employee and released the application in app store in private by providing organisation ID and the application is showing ready for distribution in my developer account. But after this I can't understand how to get the application or the link to have the application for use. And also I already contact to the apple team via mail but from them there is no response. How to procced further?

My builds failed today with this error: Unsupported SDK or Xcode version. Your app was built with an SDK or version of Xcode that isn’t supported. Although you can use beta versions of SDKs and Xcode to build and upload apps to App Store Connect, you need to use the latest Release Candidates (RC) for SDKs and Xcode to submit the app. For details on currently supported SDKs and versions of Xcode, visit: https://developer.apple.com/news/releases. The thing is, I have Xcode Cloud configured to use the latest release. There is a separate configuration for "Latest beta or release", so why is it using the Xcode 16.2 Beta 3 build? This is clearly a beta. If you're going to give me an option to use the latest release, then it should do what it says.

Using the native email ios mail app iPhone 16 pro. When an email arrives the phone will ding or vibrate, but the message notification doesn't appear on lock screen. If you touch the screen from dim to wake then scroll up, the email notification does appear. If the phone is open the notification also appears at the top of screen as it's meant to do. This started yesterday with iOS 18.2 beta 1. It was not resolved with the new update.

Hello, After upgrading to iPad OS 18.1, Rest Finger To Open not working on my device - which is an 9th-generation iPad (10.2 inch) - anymore, now I have to actually press the Home button, only then I can unlock the screen with Touch ID. It was fine on iPad OS 17, where I just need to rest my finger on the Touch ID (or Home button) and it would unlock the device right away, no need to press. I'm sure all the required settings have been checked (please check out the screenshots). Not sure if anyone else is facing this. Hope it's not only me. Please take a look at this and fix it if it's a genuine issue. Thank you.

I encountered a crash in iOS 17 related to CLBackgroundActivitySession, which appears to be due to misleading guidance in an Apple’s WWDC video. Crash sample code: https://github.com/steve-ham/AppleLocationCrash Simplified Reproduction Steps: 1. Open the GitHub sample app. 2. Archive and export (Distribute App -> Custom -> (Release Testing, Enterprise, or Debugging) -> Export). 3. Open the app. 4. Tap enableBackgroundLocation -> select Allow While Using App on the system popup. 5. Tap disableBackgroundLocation. 6. Go to the iOS home screen. 7. Wait for 10 seconds. 8. Reopen the app -> crash occurs. The crash happens because setting CLBackgroundActivitySession to nil does not end the session, despite Apple’s guidance suggesting it should. Below is the exact quote from WWDC 2023, which explicitly states that both calling invalidate() or letting the object get destroyed (i.e., setting to nil) would end the session: WWDC 2023 Discover Streamlined Location Updates (https://developer.apple.com/videos/play/wwdc2023/10180/) “Before starting the updates, you should instantiate a CLBackgroundActivitySession object to start a new session. Note, we are assigning the session to self.backgroundActivity, which is a property and not to a local variable. And this is important because if we used a local variable, then when it goes out of scope, the object it holds would be deallocated, invalidating the session and potentially ending your app’s access to location. Then when we want to end our session, we can do that by sending the invalidate message or by letting the object be destroyed.” I’ve submitted this to Apple for resolution but wanted to share this with the community. This misguidance has caused issues in my app’s release. If Apple could reply to confirm or provide clarification, it would be greatly appreciated. P.S. Even a minimal implementation in viewDidLoad triggers the crash: let session = CLBackgroundActivitySession() print("session (session)")

Hello all, I’ve had the iOS 18 beta since it’s been available, but recently when I updated to iOS 18.2 beta 2 I’ve been experiencing random crashes and frozen screens. I can’t seem to find any common reason for it, as it’s seemingly random. My screen will turn black and show the loading icon like I’ve run out of battery before the screen turns back on showing the Lock Screen. I’ve experienced crashes anywhere from 1-5 times daily for roughly 3-5 days, though the screen has only frozen once and gone completely unresponsive for a solid minute. When it froze I attempted to power off the phone, but all buttons were y responsive as well. After around a minute had passed, the screen went black and it crashed before returning to the Lock Screen and working otherwise fine afterwards. Has anyone else experienced this, or know a potential reason this is happening ?

The interactiveDismissDisabled() function in SwiftUI's Sheet no longer works as expected in iOS 18.1 (22B83). It was working as expected until iOS 18.0.1. Are there any other users experiencing the same issue? struct ContentView: View { @State private var openSheet = false var body: some View { NavigationStack { Button("Open") { openSheet = true } .sheet(isPresented: $openSheet) { SheetView() } } } } struct SheetView: View { @Environment(\.dismiss) private var dismiss var body: some View { NavigationStack { Text("This is the Sheet") .toolbar { ToolbarItem(placement: .cancellationAction) { Button("Cancel") { dismiss() } } } .interactiveDismissDisabled() } } } Supplementary information: In iOS 18.1, even Apple's native Journal app allows users to swipe-to-dismiss the sheet when creating a new entry. Previously, a confirmation dialog would be displayed, but this is no longer the case.​​​​​​​​​​​​​​​​

I remember a long time ago seeing a website that would show every single piece of feedback sent to Apple, not showing the sender. The website looked old but still working. Dies anyone know what it is? Thank you

The current setup restricts the access to the dock from the external monitors, requiring me to switch back to the MacBook screen. This process is inefficient for my workflow as it involves scrolling through multiple monitors, consuming valuable time.

I tend to remember that it is not possible to get a status update for a FB Ticket as long as you are not the one (or part of the team) who created the ticket (for obvious privacy and confidentiality reasons). And based on what I'm reading from some posts in the forum, it's not unusual that a FB ticket declared to be a duplicate of another ticket is not updated when the original ticket is either fixed or closed. So what is the recommendation to be informed about the status of a problem when you know that a FB ticket was already filed by another party (and it's obvious your ticket will be marked to be a duplicate)? File a FB ticket on the same topic with a reference to the original FB ticket and pray? N.B. : this is not a case listed in the https://developer.apple.com/bug-reporting/ page.

If you create a cookie and add to the WKWebViewConfiguration the completionHandler returns 'Cookies synced' suggesting cookie was added with success. However, upon inspection of app in Safari the cookie is not there. This is broken in iOS 18 beta and works in previous versions without issue. Did Apple change the WKWebView API and break this feature? code snippet: NSDictionary* settings = self.commandDelegate.settings; WKWebViewConfiguration* configuration = [self createConfigurationFromSettings:settings]; configuration.userContentController = userContentController; NSMutableDictionary *cookieProperties = [NSMutableDictionary dictionary]; [cookieProperties setObject:@"foo" forKey:NSHTTPCookieName]; [cookieProperties setObject:@"bar" forKey:NSHTTPCookieValue]; [cookieProperties setObject:@"mydomain.com" forKey:NSHTTPCookieDomain]; [cookieProperties setObject:@"mydomain.com" forKey:NSHTTPCookieOriginURL]; [cookieProperties setObject:@"/" forKey:NSHTTPCookiePath]; NSHTTPCookie *cookie = [NSHTTPCookie cookieWithProperties:cookieProperties]; [configuration.websiteDataStore.httpCookieStore setCookie:cookie completionHandler:^{NSLog(@"Cookies synced");}]; WKWebView* wkWebView = [[WKWebView alloc] initWithFrame:self.engineWebView.frame configuration:configuration];

Hello, We are currently using Hub which uses CYPD3125 PD chip, It is used to connect with both Android and iOS devices. While our device works seamlessly with Android devices, we are encountering an issue when connecting to iOS devices, specifically the iPad Pro. Issue Description: The Powerpack/Hub is intended to handle Power Delivery (PD) communications. When connected to an Android device, the PD packets are exchanged correctly, and the device functions as expected. However, when connected to an iPad Pro, we observe abnormal PD packet exchanges which lead to malfunctioning of the Powerpack/Hub. Observations: Attached is a snapshot of the PD packets we captured while troubleshooting the issue in a scenario where the AC power adapter was initially connected. After a few seconds, we removed the plug, waited for a few seconds, and then plugged in the AC power again. This was the scenario when we captured the PD packets, as seen in the snapshot. The packets appear to be different when compared to those captured with an Android device. Below is the screenshot of the PD packet capture with Apple device: Below is the screenshot of the PD packet capture with Android device: Technical Observations: Initial Connection: The connection initiates but does not follow the expected PD communication sequence. Packet Structure: In the capture, the iPad Pro shows a series of PD Msg types including Src Cap, Req, and Accept, but there are also unexpected messages such as Hard Reset and Soft Reset that disrupt the communication. Timing Issues: The timestamps show irregular intervals between packets when connected to the iPad Pro, suggesting possible timing synchronization issues. Unexpected Resets: The capture shows a Hard Reset event at packet 9, which is not observed in the Android device captures. This suggests the iPad Pro might be detecting an error and attempting to reset the connection. Steps Taken: Verified the firmware and hardware implementation of the Powerpack/Hub. Ensured compliance with USB PD standards. Tested with multiple iPad Pro units to rule out device-specific issues. Additional Details: We have also tested with iPad Air and observed the same issue. The tests were conducted on both iOS version 16 and 17. We are attaching a USB PD capture with an Android device where it is working fine as expected. The PD packets were captured in a scenario where the AC power adapter was initially connected. After a few seconds, we removed the plug, waited for a few seconds, and then plugged in the AC power again. This was the scenario when we captured the PD packets, as seen in the snapshot. Despite these steps, the issue persists. We seek guidance on any issues or peculiarities with iOS devices and USB PD communication. Thanks

How to report a bug says "With Feedback Assistant available on iPhone, iPad, Mac, and the web, it’s easy to report issues you encounter". The Feedback Assistant User Guide says "Tell Apple about your experience with beta or seed releases". Is Feedback Assistant only intended for reporting bugs in beta software? A year ago I reported a bug in Xcode 14 and now I'm being asked to verify this issue with Xcode 16 Beta 3. I'm not a beta tester and I don't want to install beta software. How should I proceed?

When you do broader mathematical terms it keeps saying “coefficient missing in unit term” even though I wrote the formula perfectly.

Hello, I am writing to seek urgent assistance with a long-standing issue regarding my Apple Developer account. For nearly two years, I have had funds accumulated in my account from app sales, but I have been unable to access them. Despite numerous attempts to contact Apple Support via email and other channels, I have not received any response or assistance. The funds have remained in my account, and every time I try to reach out for help, my requests go unanswered. This has been a frustrating experience, and I am at a loss on how to proceed further to resolve this matter. Can someone from the Apple Developer Support team please help me with this issue or guide me on how to speak with a representative over the phone? Your assistance in resolving this matter promptly would be greatly appreciated. Thank you for your attention to this matter. Best regards, Nitzan. Y&N AI Solutions (which is by now already closed)

I have two feedback issues under Sequoia that are fairly major features. FB14105190: iPhone Mirroring shows only a white rectangle. FB13888947: VisionOS Mirroring drops connections after seconds. Both these issues are features I use (VisionOS Mirroring) or would use (the other) if I could. On a suggestion from a colleague I booted in Safe Mode and the issues went away and everything worked as it should. I've sent this upline to Feedback. But am curious what I can do to diagnose this further. Maybe locate a culprit. In the olden days, the extension parade let you know what was loaded. My kextstatus shows nothing different. Is there anything else I can explore to find this? Thanks.

Yesterday night, I opened the feedback app, but it kicked me out. When I reopened it, I had to sign back in, but it got stuck on a continuous loading screen. I tried swiping it from the background and reopening it multiple times, but it kept loading indefinitely. I waited for 1 minute, then 3 minutes, but it never stopped. This morning, I checked again to see if my reports had been opened, but the app was still loading.