Hello the community, how are you? Since few days, this messages displays as an error into my code: "The compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions" Since all these days, I'm not able to solve this problem. My app is almost done and the code is good. But I don't find where the problem is from. Here's the block where the message appears: var body: some View { //The compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions VStack { TextField("Search invoices...", text: $searchText) .padding(10) .background(Color.gray.opacity(0.1)) .cornerRadius(10) .padding(.horizontal) HStack { ForEach(BillFilter.allCases) { filter in Button(action: { selectedFilter = filter }) { Text(filter.rawValue) .padding() .background(selectedFilter == filter ? Color.accentColor : Color.gray.opacity(0.2)) .foregroundColor(selectedFilter == filter ? .white : .black) .cornerRadius(8) } } All the best,

Hello, I need some assistance with changing my Dev Forum username. I am no longer associated with the company/organization that my username is presenting

Hi, friends! I have a Keynote file, in which I create design for macOS applications settings and system settings, that I use and which are installed on my Mac. I like to record my settings so that every time I reinstall the system or an application I can open my file and set it up exactly the way I want. It's like a user manual, only it looks nice with Mac design elements. And I do it in a presentation (Keynote). I also use a Sketch for the design. I want to turn all this into an app for myself, using Swift Playground. Does anyone know how to, for example, add a macOS Dock icon from a Sketch to Swift Playground?

We are experiencing networking issues in our iOS application when it is built with Xcode 16 or later. Our app includes a video conferencing feature that works reliably when built with Xcode 15 or earlier — we can sustain hour-long video sessions without interruption. However, when the app is built using Xcode 16 or higher, network connections drop after 2–3 minutes during a session. This triggers an auto-reconnect, which succeeds, but the connection drops again after another 2–3 minutes. This loop continues indefinitely. Key Details: The issue only occurs in TestFlight builds. When running the app via Xcode debugger, the issue does not occur. The issue is consistently reproducible in TestFlight builds created with Xcode 16 or later. TestFlight builds created with Xcode 15 do not exhibit this issue. All the videoconferencing runs on C and C++ code What We’ve Tried: Reviewed Xcode 16+ release notes but found no relevant changes or deprecations. Verified app configuration and entitlements. Confirmed that no app-side changes occurred between the working and broken builds. Request: We’re seeking guidance on what changes in Xcode 16+ could be affecting networking behavior in release/TestFlight builds. Any insight into relevant build settings, compiler changes, or runtime behavior differences would be greatly appreciated. Thank you in advance for your assistance.

Looking for advice: I've been automatically rejected from Apple's Developer Program without an explanation. Hi everyone, It seems I’ve hit a brick wall, so I’m reaching out to see if anyone here has experienced something similar to this or has any advice or resources to share. I recently attempted to enroll in the Apple Developer Program, but my application was immediately denied after submission. Within one second of submitting my driver’s license, the app stated that Apple was unable to verify my identity and that I needed to reach out to Developer Support for further assistance. When I first contacted Developer Support for clarification, the representative was happy to help. After being taken off hold, she said she couldn't offer any more information, but assured me that I'd later receive an email with further details related to my account and next steps. However, instead of steps to resolve the issue, I received a denial email repeating the same message about being unable to verify my identity (screenshot attached). I’ve since spoken to multiple representatives and supervisors, and, while everyone was initially polite and understanding, it changed after I was taken off hold. Here’s what I’ve been told: The decision is final, and there is no possibility of escalation or appeal. The supervisors themselves, despite being the final decision makers, have no access to the specific reason for applicants’ denial and, thus, could not provide any additional details. I was also invited to join Apple's “Xcode program,” which I found out just means they’ll allow me to buy Xcode from the app store and use it without a developer account (I already do that). Every time a support representative reread the sentence about being “unable to verify [my] identity,” I responded by offering to provide additional forms of identification. However, that offer was never addressed. The last senior advisor I spoke with stated to me over the phone that: She was the highest authority on the matter. There was absolutely no way to escalate the issue further; it was 100% impossible. She physically did not have access to the reason for my denial. Neither she nor anyone else at Apple was able to offer further assistance. I asked this senior advisor to send me an email with the above points in writing, which she said she would do. However, the email I received was a virtual copy-paste of the email from the first support representative, stating the same few sentences verbatim. This has left me deeply confused, especially as no specific reason for denial has been shared, and since I was explicitly denied any opportunity to address (or even get information on) potential issues. I’d like to ask this community: Has anyone else experienced this sort of immediate rejection and/or a refusal to disclose the reason for that rejection? Are there specific guidelines or policies I may have unknowingly violated that I should review? If so, what could be the reason why they’re being withheld from me? Are there any resources or alternative channels I can explore to resolve this issue? I’m so thoroughly confused, and I’m genuinely at a loss with how to move forward. I appreciate any insight or guidance from this community. Thanks so much for taking the time to read! Best regards, David

Hello Apple Support, I’m facing an issue with Background Fetch in my React Native project. When I click on Simulate Background Fetch in Xcode, everything works as expected on the iOS Simulator—background tasks run smoothly, and data is fetched without issues. However, on a real device, the app goes to the background but doesn’t execute any of the scheduled background tasks, and it also remains in the background without terminating. Here’s some additional context: React Native Project: I’m using React Native to develop this app, and the background tasks involve: Getting User Location: Fetching the user’s location in the background. API Calls: Calling an API to fetch necessary information based on the user’s location. Scheduling Notifications and Alarms: Scheduling notifications and alarms based on the API response data. Simulator vs. Real Device: In the iOS Simulator, all these background tasks trigger and function correctly when I simulate Background Fetch. On the real device, however, none of these tasks are triggered when I try to simulate Background Fetch. The app only moves to the background without performing any tasks or getting terminated. Device and Configuration Details: iOS Version: 17 Device Model: Iphone xs, Iphone 11, iphone 7 Background Modes: Background Fetch is enabled in Capabilities, and I’ve set the fetch interval to the minimum for testing. I’ve verified that all configurations are correctly set, and I’ve tried restarting the device and Xcode, but the issue persists. Is there something specific about Background Fetch that could prevent it from functioning as expected on physical devices? Any guidance on troubleshooting or additional steps would be highly appreciated. Thank you!

It's maddening. I just opened a file and now it's gone because I had the audacity to open another file. I've learned that I can double click the tab of the first file to make it a permanent tab... but, of course, I'll need to do that every time I ever open any file ever, and if I close that file and come back to it later I'm going to be constantly having to double click tabs just to make Xcode stop replacing my tabs for me. It's nuts. It's driving me insane. Please. Is there any way to just DISABLE the temporary tabs behavior? I don't find it helpful in any way and I find it to be destructive to my development workflows.

Hi there! I made a mistake while create a request for enrolment, could you please explain me how to call out this enrolment?

I did a git rebase and was successful. I'm getting an error 'Failed to load container for document at url: file:///Users/collinsmuthomi/Documents/postbankiOSNewNew/Postbank.xcodeproj'

It used to work for me (a few months, maybe a year ago). Right now when I run it there is no output (even though I granted it Bluetooth Capture permissions and have working RFCOMM communication in my program). Versions: PacketLogger 2024.03.18 (2024.03.18d1) Sequoia 15.4.1 M2 chip

I developed (with AI help) using Xcode an app for myself. It logged certain places visited on a list, with photos and notes. It worked, but after a few days my iPhone can't launch it. What do I have to do to get this to last? I didn't think I needed to pay as this is purely for me.

My app which requires a crucial update, I have over 40 user emails saying the app is broken after the new macOS update, I patched the issue and submitted to appstore. it's been a week all I see is, app "In Review" I tried submitting expedited review and I just get 502 error. I am very close to migrating off App Store and distributing it on my own.

I bought the membership almost 2 days ago and have heard no response since. Is this normal and how long can i expect to wait. I need this urgently.

I encountered this issue with an app I'm writing that accepts arguments. With some troubleshooting I've determined that this is an inherent behaviour in how Xcode 16 compiles SwiftUI apps and how macOS 15 launches them. The issue: Launching the app as open /Applications/AppName.app --args --arg1 --arg2 --arg3 etc should allow the app to process the arguments as CommandLine.arguments and this is still the case. How the app sees arguments is unchanged and doesn't matter if you use CommandLine.arguments or swift argument parser or don't have arguments at all. This will affect any SwiftUI app as I'll demonstrate below. The problem is that if you use a mix of arguments as --arg value pairs or --arg as a flag, then depending on the order the arguments are provides, the app won't launch properly. The icon will appear in the dock but no window appears until you click the icon in the dock. (BTW, having "Application is agent (UIElement)" set to YES in the Info.plist makes this task rather difficult.) In testing if you use all flags, it's fine. if the flags are in pairs, it's fine. if you have one flag and then a --arg value pair, you will see the issue. If you reverse the order so the flag is after then it works fine. How to replicate: On macOS 15 and Xcode 16 Open Xcode Create a new macOS App (called demoapp in my example) Select SwiftUI as the interface Build That it. Don't add anything and just build the boilerplate hello world app that Xcode makes for you. Once that's built, cd to your /Build/Products/Debug/ directory in terminal and try the following (this happens if you build for release as well): note, the app window will display when you click the icon in the dock, just not on initial launch # three single arguments open ./demoapp.app --args --foo --bar --baz # App window displays as expected # one single argument, one arg value pair open ./demoapp.app --args --foo --bar baz # The app window will not appear. # same arguments as before but the single argument is after the arg value pair open ./demoapp.app --args --bar baz --foo # App window displays as expected # arg[1] without `-` or `--` prefix open ./demoapp.app --args foo --bar --baz # The app window will not appear. # arg[1] and arg [2] without prefix open ./demoapp.app --args foo bar --baz # The app window will not appear. # single - in front of the first two arguments open ./demoapp.app --args -foo -bar baz # The app window will not appear. # single - in front of the first three arguments open ./demoapp.app --args -foo -bar -baz bob # App window displays as expected No idea what is going on but I suspect macOS does some pre-processing before launching the app, for example you can do stuff like open /Applications/SomeApp.app --args -AppleLanguages '(de)' to run using a specific language. I presume the OS is pre-processing arguments before launching the app proper. If I compile the app using Xcode 15.4 then this issue is not present. Also Apps compiled with Xcode 16 do not exhibit the issue on macOS 14 or earlier. It's a specific Xcode 16, macOS 15 thing in the way the app is compiled that makes it behave this way. I hope I've explained it correctly, but it's very easy to replicate. I filed a feedback for it (under a different apple account), FB15577018. Any insight into what's going on here would be helpful. Also if there's any compiler flags I could be setting. In my actual project, I'm not making any other changes. The same code compiled under Xcode 16 (.0 or .1RC) behaves differently to Xcode 15.4.

I am not able to use the Debug Memory Graph tool as well as Leaks instrument inside Xcode to debug my project. I'm running my project on physical iOS device on running 18.3 version and I tested the project on two different MacBooks running Xcode 16.3 and 16.1. On both the same problem persists. I have also reinstalled the project on the device and tried restarting all devices and cleared DerivedData. Nothing helped. Clicking "Show details" shows such output: Domain: DTLeaksService Code: -1 User Info: { DVTErrorCreationDateKey = "2025-05-07 06:30:53 +0000"; DVTRadarComponentKey = 637311; } -- Event Metadata: com.apple.dt.memory_graph_capture : { "debugSession_coalescedState" = 2; "debugSession_isSynthetic" = 0; "debugSession_state" = 2; "device_identifier" = "00008110-0009448221A3801E"; "device_isCoreDevice" = 1; "device_model" = "iPhone14,4"; "device_osBuild" = "18.4 (22E240)"; "device_platform" = "com.apple.platform.iphoneos"; "device_thinningType" = "iPhone14,4"; "dvt_coredevice_version" = "397.24"; "dvt_coresimulator_version" = "987.2"; "dvt_mobiledevice_version" = "1784.102.1"; "launchSession_schemeCommand" = Run; "launchSession_state" = 2; "launchSession_targetArch" = arm64; "memgraphDebugger_duration_ms" = 3050; "memgraphDebugger_precedingCount" = 1; "memgraphDebugger_status" = "-1"; "param_debugger_attachToExtensions" = 0; "param_debugger_attachToXPC" = 1; "param_debugger_type" = 3; "param_destination_isProxy" = 0; "param_destination_platform" = "com.apple.platform.iphoneos"; "param_diag_113575882_enable" = 0; "param_diag_MainThreadChecker_stopOnIssue" = 0; "param_diag_MallocStackLogging_enableDuringAttach" = 0; "param_diag_MallocStackLogging_enableForXPC" = 1; "param_diag_allowLocationSimulation" = 1; "param_diag_checker_tpc_enable" = 1; "param_diag_gpu_frameCapture_enable" = 3; "param_diag_gpu_shaderValidation_enable" = 0; "param_diag_gpu_validation_enable" = 0; "param_diag_guardMalloc_enable" = 0; "param_diag_memoryGraphOnResourceException" = 0; "param_diag_mtc_enable" = 1; "param_diag_queueDebugging_enable" = 1; "param_diag_runtimeProfile_generate" = 0; "param_diag_sanitizer_asan_enable" = 0; "param_diag_sanitizer_tsan_enable" = 0; "param_diag_sanitizer_tsan_stopOnIssue" = 0; "param_diag_sanitizer_ubsan_enable" = 0; "param_diag_sanitizer_ubsan_stopOnIssue" = 0; "param_diag_showNonLocalizedStrings" = 0; "param_diag_viewDebugging_enabled" = 1; "param_diag_viewDebugging_insertDylibOnLaunch" = 1; "param_install_style" = 2; "param_launcher_UID" = 2; "param_launcher_allowDeviceSensorReplayData" = 0; "param_launcher_kind" = 0; "param_launcher_style" = 99; "param_launcher_substyle" = 0; "param_runnable_appExtensionHostRunMode" = 0; "param_runnable_productType" = "com.apple.product-type.application"; "param_structuredConsoleMode" = 1; "param_testing_launchedForTesting" = 0; "param_testing_suppressSimulatorApp" = 0; "param_testing_usingCLI" = 0; "sdk_canonicalName" = "iphoneos18.1"; "sdk_osVersion" = "18.1"; "sdk_variant" = iphoneos; } -- System Information macOS Version 14.5 (Build 23F79) Xcode 16.1 (23503) (Build 16B40) Timestamp: 2025-05-07T08:30:53+02:00 Here are my active scheme settings:

Hello everyone, I’m running into an issue when logging into my Apple Developer account on the official site. After entering my Apple ID and password, I immediately see: too many verification codes sent At this point I should receive a 6-digit 2FA code via SMS to my trusted phone number, but nothing ever arrives. I’ve waited from one to seven days and tried again, but I still get the same error and still no SMS. I’ve double-checked that: My trusted phone number is correct in my Apple ID settings. My carrier isn’t blocking or rate-limiting SMS messages. Steps to reproduce: Go to developer.apple.com and click “Sign In.” Enter Apple ID and password. Submit credentials → immediately see “too many verification codes sent.” No SMS arrives. Retrying doesn’t help. Expected behavior: Apple sends a new 6-digit 2FA SMS to my trusted number. After entering it, I can complete the login flow. Actual behavior: I receive the “too many verification codes sent” message instantly. I never get the SMS code, even after waiting or retrying. Has anyone else experienced this on the standard Developer portal? Is there a way to clear the “too many verification codes sent” flag or otherwise force delivery of the 2FA SMS? Any advice would be greatly appreciated! Thank you!

Hello everyone, I’m running into an issue when logging into my Apple Developer account on the official site. After entering my Apple ID and password, I immediately see: too many verification codes sent At this point I should receive a 6-digit 2FA code via SMS to my trusted phone number, but nothing ever arrives. I’ve waited 10–15 minutes and tried again, but I still get the same error and still no SMS. I’ve double-checked that: My trusted phone number is correct in my Apple ID settings. My carrier isn’t blocking or rate-limiting SMS messages. I can log in successfully via other Apple services (e.g. iCloud.com) and receive codes there without issue. Steps to reproduce: Go to developer.apple.com and click “Sign In.” Enter Apple ID and password. Submit credentials → immediately see “too many verification codes sent.” No SMS arrives. Retrying doesn’t help. Expected behavior: Apple sends a new 6-digit 2FA SMS to my trusted number. After entering it, I can complete the login flow. Actual behavior: I receive the “too many verification codes sent” message instantly. I never get the SMS code, even after waiting or retrying. Has anyone else experienced this on the standard Developer portal? Is there a way to clear the “too many verification codes sent” flag or otherwise force delivery of the 2FA SMS? Any advice would be greatly appreciated! Thank you!

I am the sole administrator of a paid company Apple Developer account, and as of today I’m completely locked out everywhere: I cannot sign in to App Store Connect, developer.apple.com, or even account.apple.com. Every login attempt returns either “Please verify your account information and try again” or “This account is locked and can’t be used.” I have never changed my password, Two-Factor Authentication is enabled and delivering codes, there are no pending agreements or banking/tax forms, and I see no unrecognized devices in my account. I’ve tried multiple networks, browsers, and devices, and I’ve already contacted Apple Support—yet no explanation or resolution has been provided. This total lockout is preventing our app submissions from moving forward and putting our entire release schedule at risk. I need: A clear, specific reason why my corporate Developer account has been locked. Any immediate steps or known workarounds to restore full access. Advice from anyone who has faced the same unexplained lockout.

Hi, I'm unable to install provisioning profile on my iPad and I know the xcode component iOS/iPadOs version and iPadOS version should be same or below the latest compared to xcode components. Now the issue is xcode component version is iOS 18.4 (22E235) SDK + iOS 18.4 (22E238) Simulator (Installed) and iPadOS version is iOS 18.4.1(22E252) could this be cause of issue ? If yes then when will apple release components for 18.4.1? Because iOS 18.4.1 release at least 3-4 weeks before this post.