This is a M4 iMac 32GB 2TB where over the last few months memory use has been crazy. The worst offender is SimulatorTrampoline. I just opened a default iOS app and ran it in a simulator. So this is as simple as it gets: there's 1 SF Symbol and "Hello, world!" text. iStatMenus shows SimulatorTrampoline at 10.7GB, Safari 5.2GB, Xcode at 3.2GB, and swap at 548MB meanwhile ActivityMonitor shows the top memory use of Ildb-rpc-server at 2.30GB, Xcode at 523.4MB Swap is 548MB is the only number that matches and the fact that Memory used is ~26GB total. Is this amount of memory use normal? Is iStat menu reporting something different than Activity monitor. This computer used to never swap. Any suggestions?

We're having issues getting Sign in with Google to function on TestFlight (not experiencing these issues on iOS Browser) with user unable to be authorised and proceed to logged in screens of our app. Below are the three sign-in methods tested and the exact results for each. Button 1: Default Standard Google Sign-In button (Google JavaScript SDK) embedded in the frontend. Uses the normal OAuth browser redirect flow. Auth URL: https://accounts.google.com/o/oauth2/v2/auth?... Sometimes disallowed_useragent error. Other times a 400 invalid_request error. In most cases the callback is never triggered inside the wrapper. Appears that the wrapper does not retain cookies/session data from the external Google window. Button 2: Custom Custom button calling Google OAuth through our own redirect handler. Explicitly set a custom user-agent to bypass disallowed user agent logic. Later removed user-agent override entirely for testing. Added multiple ATS (App Transport Security) exceptions for Google domains. Added custom URL scheme to Info.plist for OAuth redirect. Changing the user-agent had no effect. ATS exceptions + scheme support verified and working. Redirect still fails to propagate tokens back to the WebView. In tests a few weeks ago we got to Google’s login page, but it never returned to the app with a valid code. Now we are consistently getting disallowed_useragent error. Button 3: Default Same as Button 1 however tested outside of Vue.js with just plain JavaScript. Added new Google domain exceptions and updated redirect URIs. Behaviour matches Button 1 Google account selection sometimes worked, however now consitently disallowed_useragent error Additional Technical Attempts User-Agent Modifications Set UA to standard desktop Chrome → no effect. Removed UA override → no effect. ATS / Domain / Scheme Configuration Added: accounts.google.com .googleusercontent.com *.googleapis.com

I am getting the following error: " Unable to process request - PLA Update available: You currently don't have access to this membership resource. To resolve this issue, agree to the latest Program License Agreement in your developer account." Seems to be straight forward enough but after agreeing to the updated PLA I still get the error..but weirdly only on one title and on one device. I can compile and run the app on my iPad, but it fails on the iPhone. Thoughts?

Hello, I am an Apple Developer and I have been unable to access my Apple ID for more than a week because of a verification code issue. Every time I try to sign in to my Apple ID or manage my banking information, I see this error message: “Too many verification codes have been sent. Enter the last verification code you received or try again later.” The problem is that I am not receiving any SMS verification codes at all, so I cannot enter any “last code”, and I cannot complete the sign-in process. I have already tried the following: Waited more than 24 hours without requesting new codes, several times. Tried signing in from different devices and networks. Confirmed that my phone number is active and can receive other SMS messages from different services. The issue persists and I am effectively locked out of my Apple ID. This is a critical problem for me because it directly affects my Apple Developer work: I cannot sign in to App Store Connect. I cannot add or edit my banking information. I cannot upload my app or submit it for review. I also do not have another phone number that I can add as a trusted phone number, so I cannot simply switch to a different number. I kindly ask for a concrete technical solution or manual intervention for my Apple ID, not just “wait 24 hours and try again”, because I have already done that multiple times and the error is still there. Could you please: check if there is a block or rate limit on verification codes for my account, and help reset it or provide another way to verify my identity and restore access to my Apple ID, or assist me with updating my trusted phone number after verifying my identity? This issue is blocking my ability to continue development and release of my app on the App Store, so I would really appreciate any escalation to the appropriate technical team. Thank you very much for your help. Best regards, Daniil

Hi everyone, I think this is a simple issue. I got the following error message" "PreviewDevice is ignored in a #Preview macro. Use the device picker at the bottom of the Canvas to change which device type is used for the preview. (from macro 'Preview')" after this line: ".previewDevice(PreviewDevice(rawValue: "iPhone 17 Pro"))" But in my Canvas I do not see the device picker. Thank you.

It has been two years since I wrote my a SwiftUI app, and I wanted to start again in Xcode 26. I can no longer see the attributes inspector when I select an element in the canvas. This was an Xcode feature that was very helpful as I am still a novice. Has this feature been deprecated in Xcode 26? And if not, please help explain how I can find and use it.

This is using: **Unity 6000.2.7f - latest ARKit etc Xcode 26.1 ** This is going to iPad/iPhone/iOS and I have succesfully built to the iPad before, but updates to the software seem to have added these errors in. Basically all updated as much as possible. Originally I got 5 errors, but updates brought it down. On build I now get 3 undefined symbols: Undefined symbol: _swift_FORCE_LOAD$_swiftCompatibility51 Undefined symbol: _swift_FORCE_LOAD$_swiftCompatibility56 Undefined symbol: _swift_FORCE_LOAD$_swiftCompatibilityConcurrency This appears to be a bug, or issue, that is in some way known, but I'm not sure how best to get past it. ld: warning: search path '/var/run/com.apple.security.cryptexd/mnt/com.apple.MobileAsset.MetalToolchain-v17.1.324.0.kGuqPt/Metal.xctoolchain/usr/lib/swift/iphoneos' not found ld: warning: search path '/var/run/com.apple.security.cryptexd/mnt/com.apple.MobileAsset.MetalToolchain-v17.1.324.0.kGuqPt/Metal.xctoolchain/usr/lib/swift-5.0/iphoneos' not found ld: warning: Could not find or use auto-linked library 'swiftCompatibility51': library 'swiftCompatibility51' not found ld: warning: Could not find or use auto-linked library 'swiftCompatibility56': library 'swiftCompatibility56' not found ld: warning: Could not find or use auto-linked library 'swiftCompatibilityConcurrency': library 'swiftCompatibilityConcurrency' not found ld: warning: Could not find or use auto-linked library 'swiftCompatibilityPacks': library 'swiftCompatibilityPacks' not found ld: warning: Could not find or use auto-linked framework 'CoreAudioTypes': framework 'CoreAudioTypes' not found ld: warning: Could not find or use auto-linked framework 'UIUtilities': framework 'UIUtilities' not found ld: warning: Could not parse or use implicit file '/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk/System/Library/Frameworks/SwiftUICore.framework/SwiftUICore.tbd': cannot link directly with 'SwiftUICore' because product being built is not an allowed client of it Undefined symbols for architecture arm64: "_swift_FORCE_LOAD$_swiftCompatibility51", referenced from: _swift_FORCE_LOAD$swiftCompatibility51$_UnityARKit in libUnityARKit.a[49](RoomCaptureSessionWrapper. o) "_swift_FORCE_LOAD$_swiftCompatibility56", referenced from: _swift_FORCE_LOAD$swiftCompatibility56$_UnityARKit in libUnityARKit.a[49](RoomCaptureSessionWrapper. o) "_swift_FORCE_LOAD$_swiftCompatibilityConcurrency", referenced from: _swift_FORCE_LOAD$swiftCompatibilityConcurrency$_UnityARKit in libUnityARKit.a[49](RoomCaptureSessionWrapper. o) ld: symbol(s) not found for architecture arm64 clang++: error: linker command failed with exit code 1 (use -v to see invocation)

Hello, I am currently working on a project that requires the use of the NFCTagReaderSession API to perform read and write operations on NFC tags (ISO15693 and other standard NFC tag types). According to the Apple documentation, CoreNFC and NFCTagReaderSession are fully supported on iPhone devices. However, the behavior and availability on iPad devices are not clearly documented. I would like to request clarification on the following points: Is NFCTagReaderSession officially supported on iPad devices? We have verified that some iPad models equipped with NFC hardware still do not expose support for this API. Is there an up-to-date list of iPad models that support CoreNFC? The documentation currently mentions only “iPhone 7 or later,” with no reference to iPad models. Does Apple plan to enable NFCTagReaderSession on iPad in the future? This information is important for our product roadmap, as several of our deployments rely on tablets. Our goal is to determine whether NFC tag read/write operations are intended to be available exclusively on iPhone, or whether there are existing or upcoming iPad models that will support CoreNFC as well. Thank you in advance for your support and for any clarification you can provide. Kind regards,

Problem When we merge FeatureModuleA.framework into IntegrationContainer.framework instead of HostApp_Main.app, the magic method Bundle(for: FeatureAProvider.self) does not work and this will trigger crash. When FeatureModuleA is merged into HostApp, Bundle(for: FeatureAProvider.self) will return: HostApp_Main.App/Frameworks/DomainFeatureA.framework instead of HostApp_Main.App/, although the FeatureAProvider class is actually in the merged main app binary So we can use the returned FeatureModuleA bundle get the nested resource. If we merge the frameworks into our IntegrationContainer.framework, the result will be: for release: PrototypeApp.app for debug: PrototypeApp.app/Frameworks/IntegrationContainer.framework/ReexportedBinaries/DomainFeatureA.framework Apple has not considered the case that frameworks are merged into independent framework. And other methods like bundle(for: identifier) does not work for both destination cases: merge into main app or a container framework.

GCC's shared library constructor technique has ceased working with the tool chain provided with XCode 16.4 and XCode 26. This is the GCC attribute: __attribute__((constructor)) Example use: void aConstructor(void) __attribute__((constructor)); void aConstructor(void) { printf("Called aConstructor\n"); } In our case aConstructor() was not called.

Hi everyone, I am trying to generate an .ipa file for my .NET MAUI (net9.0-ios) application, but every attempt fails with the same codesigning error. I have tried multiple approaches, including building from Windows paired to macOS, and directly building through the macOS terminal, but nothing is working. Below are the exact steps I followed: Steps I Performed Generated the Apple Development certificate using Keychain Access on macOS. Added that certificate into my developer account and created the corresponding provisioning profile. Created an App ID, attached the App ID to the provisioning profile, and downloaded it. Added the provisioning profile into Xcode. Verified that the certificate is correctly visible in Keychain Access (private key available). Attempted to build/publish the MAUI app to generate the .ipa file. Issue Whenever I run the publish command or build via Windows/macOS, codesigning fails with the following error: /usr/bin/codesign exited with code 1: Frameworks/libSkiaSharp.framework: replacing existing signature Warning: unable to build chain to self-signed root for signer "Apple Development: Created via API (8388XAA3RT)" Frameworks/libSkiaSharp.framework: errSecInternalComponent Failed to codesign 'PCS_EmpApp.app/Frameworks/libSkiaSharp.framework': Warning: unable to build chain to self-signed root for signer "Apple Development: Created via API (8388XAA3RT)" PCS_EmpApp.app: errSecInternalComponent Build eventually fails with: Build failed with 4 error(s) and 509 warning(s) Environment .NET: 9.0 MAUI: latest tools Xcode: 26.0.1 macOS: 26.0.1 Building for ios-arm64 (device) What I suspect It looks like the signer certificate might not be trusted, or the certificate chain cannot connect to an Apple root CA. But the certificate was created using the Developer website and appears valid. Need Help With Why is codesign unable to build the certificate chain? Do I need a different type of certificate? (App Store / Distribution vs Development?) Is there any special configuration required for MAUI apps using native frameworks like libSkiaSharp.framework? How can I successfully generate the .ipa file? Any guidance will be greatly appreciated. Thank you!

I want to create a dynamic library for my iOS project, which would be loaded at runtime. In Xcode, there are templates available for creating a static/dynamic lib for MacOS. But under the iOS tab, there is only a "static library" template. So, I used the "static library" template and in its build settings I changed the Mach-O type to "dynamic library". Now after building it, I use the file command on the generated file and it tells me it is a dynamic lib. But the generated file still has .a extension, which is usually for static libs. I'm aware we can tell Xcode in build settings to change the .a extension to something else, say .dylib but this seems like a hacky way to create a dynamic library. What is the correct way? I am aware that standalone dylibs are not supported on iOS, and we need to wrap them in a framework. For my use case, the framework will literally be a wrapper, it won't have any source files of its own. It should only contain the dynamic lib generated from some independent codebase. I am not sure how to place the dylib in the framework.

Hi, I have an iOS project with the following app targets: main iOS application a notification service extension 5 static libs containing some swift files with public methods 1 dynamic framework with above static libs as dependencies. The framework only contains 2 files - a default .h file and 1 .exp file. This exports file contains mangled-names of all the public methods that are exposed by the 5 static libs present as framework's dependencies. I obtained these symbols using the nm command for each static lib. The main iOS app target has 2 dependencies - the framework and the notification extension. The notification extension only depends on the framework. This setup works perfectly fine. I wanted to understand: If using the exports file is the only way to make this setup work? If not, what else can I do? What way does Apple recommend? According to my requirements, I only need at-most 2-3 functions to be exposed by the framework - thus using a exports file just for that seems to bug me. Thank you.

【溦N51888M】腾龙公司直属会员怎么开户【罔纸 211239.com 】输入官惘到浏览器打开联系24小时在线业务人员办理上下，打开公司官网. 二、点击主页右上角注册按钮. 三、填写账号信息. 四、输入手机号，验证码，密码. 五、勾选用户协议，完成注册协议，完成注册. 注意：若出现账号已存在」提示，需重新设置唯一账号名称

Once in a while I get from Xcode a reminder to test Coding Intelligence. I am today not interested in Coding Intelligence and it's unlikely that I will be in the future. Therefore, I would like to get rid of these for me useless reminders to activate Coding Intelligence. I have not found anywhere anything for doing so. Or do I get rid of the reminders when activating it and deactivating it immediately again (if this is possible)?

Using Xcode 26.1.1 on macOS 26.1 Tahoe, I noticed the ability to add a new value seems hidden or disabled. I'm unable to scrolling horizontally to view the rest of the values in each row and notice an overlap between the target properties and document types section.

I’m on the Apple Developer application on the Mac Mini, and I’m getting the option “Continue your enrollment.” When I click it, I’m shown a “Subscription Fee” button. After clicking that, I receive this message: “An Apple Developer Program membership subscription is already associated with your iTunes & App Store account.” The only option I have is to click OK, and when I do that, it takes me back to the same Subscription screen. The enrollment is not getting completed, and I’m stuck in a loop. Could you please help me with this?

The Test target not build for not such file or directory: 'CoreGraphics'. Not sure why I get this error, but I configured the target without forgetting the variables BUNDLE_LOADER with $(BUILT_PRODUCTS_DIR)/MyExistingApp.app/MyExistingApp value and TEST_HOST with $(BUNDLE_LOADER) value. App target (not the test target), the Symbols Hidden by Default build setting its equal to NO, unlike the Test target that is set to YES. Any variable more for this? I'm not sure if I should take anything into account when using Xcode 26.1.1 and Swift Testing framework.

Hi everyone, after enabling CloudKit in my project, my app started showing conflicts between MusicKit and CloudKit entitlements — and now Xcode is failing to generate the provisioning profile entirely. Current issue (Signing / Provisioning Profile Failure) Xcode shows this error: “Provisioning profile ‘iOS Team Provisioning Profile: team8.groovefy.dev’ doesn’t include the entitlements: com.apple.developer.media-library, com.apple.developer.music-user-token, com.apple.developer.musickit, com.apple.developer.playable-content, com.apple.security.exception.mach-lookup.global-name” Automatic signing fails, and Xcode cannot create or update the provisioning profile. This started right after CloudKit was enabled in the project. Context Before enabling CloudKit, MusicKit worked normally, including Apple Music authentication and playlist creation. After activating CloudKit capabilities: MusicKit stopped generating the Apple Music user token Playlist creation broke Now the provisioning profile cannot be rebuilt because the required MusicKit-related entitlements are no longer included Even after removing CloudKit entirely, the issue persists — as if the App ID or entitlements on the server side became inconsistent or corrupted. I already tried: Recreating App Identifier Recreating provisioning profiles Resetting capabilities Cleaning and reinitializing the Xcode project settings But Xcode still refuses to generate a valid provisioning profile that includes the MusicKit entitlements. Summary Enabling CloudKit caused MusicKit entitlements to collide, and now the provisioning profile no longer includes the required MusicKit entitlements — preventing the app from signing, running, or creating playlists. If anyone has faced this type of entitlements/provisioning corruption or knows how to reset the App ID entitlements on Apple’s side, any help would be greatly appreciated.

How can I allow the popup I am encountering while I run my UI tests with video recording in the Github actions. Since these tests are running on VMs, it's not possible to manually click Allow. Also the remote robot cannot interact with OS-level dialogs.