Overview

Post

Replies

Boosts

Views

Activity

Notarizations stuck in progress over 24 hours
I made a small 20MB .pkg installer for some Logic Pro Drum Machine Designer patches so the user doesn't have to manually place the files by hand. Tried to notarize 3 times, all attempts have been stuck "in progress" since yesterday and can't seem to get any log files that might explain where things are getting stuck. Are the duplicate submissions causing this and if so is there a way to de-duplicate? My first time doing this so when notarization was hanging on the first attempt I thought I had done something incorrectly. Not sure how to troubleshoot this and would appreciate any guidance.
0
0
9
32m
iOS 26.5 breaks AppIntents with AppEnums defined in Swift Package
For some reason since iOS 26.5, a ControlWidgetButton or a Button in a widget configured with an AppIntent conforming to OpenIntent fails to receive its AppEnum parameter correctly if the intent and enum are defined inside a shared Swift Package. Tapping the control widget button opens the main application, but it doesn't pass the AppEnum parameter value in, leaving the app on its default screen instead of navigating to the intended view. This was working perfectly in iOS 26.4, where the app would launch and receive the correct enum case from the intent. No code, configuration, or scheme changes were made between the two runs, only the simulator/OS version differs. Has anyone else run into what seems to be a regression on iOS 26.5? I filed feedback with a sample project: FB22848510
0
0
7
34m
AssistiveTouch eye tracker HID over USB-C/iAP2 accepted by iPadOS, but gaze point mapping is wrong
I’m implementing an Apple AssistiveTouch eye tracker accessory for iPad over USB-C using iAP2 plus native HID Gaze Point reports. Current state: iAP2 authentication succeeds identification succeeds StartNativeHID is received AssistiveTouchInformation(IsEnabled=true) is received iPadOS enumerates the HID interface and consumes the interrupt IN reports The remaining issue is that the gaze-point behavior is not interpreted as direct screen coordinates. Repeated fixed gaze inputs produce deterministic but incorrect cursor motion, often appearing like orbiting or projection around a locus rather than stable placement. I have tested: the 119-byte Apple example HID descriptor from the Accessory Interface Specification two report-1 layouts: timestamp + x + y status + timestamp + x + y normalized and physical coordinate scaling verified on the wire that the intended report bytes are sent and consumed iPad console logs show internal model point (HID r) values and multiple derived Pointer positions for a single commanded point, which suggests the device is accepted but the gaze report semantics are still not what iPadOS expects. Questions: Is the example Gaze Point HID descriptor in the Apple Accessory Interface Specification sufficient as-is for iPadOS? What exact payload layout is expected for the Gaze Point report? Is a per-sample status byte required in the gaze input report? Are additional HID feature/input reports required for correct interpretation? I can provide: the exact HID descriptor bytes sample report payloads USB analyzer traces iPad console excerpts showing the resulting model-point and pointer projections
0
0
23
1h
Custom Keyboard help
import UIKit class KeyboardViewController: UIInputViewController { // MARK: - Properties private var keyboardView: KeyboardView! private var heightConstraint: NSLayoutConstraint! private var hasInitialLayout = false // 存储系统键盘高度和动画参数 private var systemKeyboardHeight: CGFloat = 300 private var keyboardAnimationDuration: Double = 0.25 private var keyboardAnimationCurve: UIView.AnimationOptions = .curveEaseInOut // MARK: - Lifecycle override func viewDidLoad() { super.viewDidLoad() setupKeyboard() } override func viewWillAppear(_ animated: Bool) { super.viewWillAppear(animated) // 在视图显示前更新键盘高度,避免闪动 if !hasInitialLayout { hasInitialLayout = true } } override func viewDidAppear(_ animated: Bool) { super.viewDidAppear(animated) } // MARK: - Setup private func setupKeyboard() { // 创建键盘视图 keyboardView = KeyboardView() keyboardView.translatesAutoresizingMaskIntoConstraints = false view.addSubview(keyboardView) // 设置约束 - 确保键盘贴紧屏幕底部 NSLayoutConstraint.activate([ keyboardView.leftAnchor.constraint(equalTo: view.leftAnchor), keyboardView.rightAnchor.constraint(equalTo: view.rightAnchor), keyboardView.bottomAnchor.constraint(equalTo: view.bottomAnchor) ]) // 设置初始高度约束(使用系统键盘高度或默认值) let initialHeight = systemKeyboardHeight heightConstraint = keyboardView.heightAnchor.constraint(equalToConstant: initialHeight) heightConstraint.isActive = true } // MARK: - Layout Events override func viewDidLayoutSubviews() { super.viewDidLayoutSubviews() } override func viewSafeAreaInsetsDidChange() { super.viewSafeAreaInsetsDidChange() } // MARK: - 键盘高度请求 // 这个方法可以确保键盘扩展报告正确的高度给系统 override func updateViewConstraints() { super.updateViewConstraints() // 确保我们的高度约束是最新的 if heightConstraint == nil { let height = systemKeyboardHeight > 0 ? systemKeyboardHeight : 216 heightConstraint = NSLayoutConstraint( item: self.view!, attribute: .height, relatedBy: .equal, toItem: nil, attribute: .notAnAttribute, multiplier: 0.0, constant: height ) heightConstraint.priority = UILayoutPriority(999) view.addConstraint(heightConstraint) } else { let height = systemKeyboardHeight > 0 ? systemKeyboardHeight : 216 heightConstraint.constant = height } } } // MARK: - Keyboard View Implementation class KeyboardView: UIView { private var keysContainer: UIStackView! override init(frame: CGRect) { super.init(frame: frame) setupView() } required init?(coder: NSCoder) { super.init(coder: coder) setupView() } private func setupView() { backgroundColor = UIColor(red: 0.82, green: 0.84, blue: 0.86, alpha: 1.0) // 创建按键容器 keysContainer = UIStackView() keysContainer.axis = .vertical keysContainer.distribution = .fillEqually keysContainer.spacing = 8 keysContainer.translatesAutoresizingMaskIntoConstraints = false addSubview(keysContainer) // 添加约束 - 确保内容在安全区域内 NSLayoutConstraint.activate([ keysContainer.topAnchor.constraint(equalTo: safeAreaLayoutGuide.topAnchor, constant: 8), keysContainer.leftAnchor.constraint(equalTo: safeAreaLayoutGuide.leftAnchor, constant: 8), keysContainer.rightAnchor.constraint(equalTo: safeAreaLayoutGuide.rightAnchor, constant: -8), keysContainer.bottomAnchor.constraint(equalTo: safeAreaLayoutGuide.bottomAnchor, constant: -8) ]) // 添加键盘行 } }
Topic: UI Frameworks SubTopic: UIKit Tags:
5
0
221
1h
TestFlight not working for internal testing – affects all apps
Hi, I am an iOS developer and I am facing a critical issue with TestFlight that is affecting ALL of my applications, not just one. Issue: TestFlight is not working during internal testing for any of my apps I am unable to install or test any build through TestFlight The problem is consistently reproducible Example App Details: App Name: PDF Editor & PDF Compressor Version: 1.2 (Build 1) Build Status: Ready to Submit Testing Group: Internal (1 Tester) Invite Status: Accepted I already submitted a support case (Case ID: 102895219145) on May 20, 2026 but have not received any response yet. Has anyone else faced this issue? Any help would be greatly appreciated. Thank you.
0
0
19
1h
App live and searchable in App Store, but not selectable in Apple Ads
Hello, my app is live on the App Store and can be found in App Store search. However, when I try to create an Apple Ads campaign, the app does not appear as a selectable app/promotion option. App name: Zenbara Apple ID: 6760915770 App Store URL: https://apps.apple.com/de/app/zenbara/id6760915770 Country/region: Germany The app is available in Germany and searchable in the App Store, but it is not available in Apple Ads campaign creation. According to Apple Ads Help, a new app can take up to 24 hours to appear during campaign creation. This period has already passed. Any of you has an idea why the app is missing from the Apple Ads eligibility index or campaign creation index? Thank you.
0
0
29
2h
switching membership issue
Hello, I'm trying to switch my membership from individual to organization and filled out the form. After submitting the form, the page says We’ll review your request and get back to you within one (1) business day. but the issue is they haven't responded in a month. this happened twice so far and i contacted Apple support and they haven't answered yet as well. Today, i re-submitted the form again and it still says the same thing. I don't know what to do. I want to publish an application and the process has stopped because of this. Can someone help me please? Thanks in advance.
0
0
28
2h
Can't download files from file provider's folder if they are read-only
I face this issue only on macOS 26 and only on the Intel architecture. I'm unable to download files from a file provider's folder when I make them read-only. STEPS TO REPRODUCE Download the sample from https://developer.apple.com/documentation/fileprovider/synchronizing-files-using-file-provider-extensions?language=objc Follow the steps on the page to configure the project. Build the project. Run it. Add a domain. Open the domain's folder in the Finder. Move a file to the domain's folder. Right-click on the file in the domain's folder and select "Remove Download". Close the Finder's window with the domain's folder and kill all the "Provider" processes to get rid of running instances of the extension. Change Item's capabilities in Item.swift to make the items read-only: var result: NSFileProviderItemCapabilities = [ .allowsContentEnumerating, .allowsReading ] Rebuild the project and run it. Open the domain's folder and try to drag and drop the file from the extension's folder to, let's say, the Desktop folder. EXPECTED RESULT The file is copied ACTUAL RESULT A dialog pops up with text "The file “filename” cannot be downloaded. Do you want to skip it?" Stop/Skip
4
0
264
3h
Orphaned 9GB Simulator Runtime in /System/Library/AssetsV2 - Cannot Delete (SIP protected)
I have an orphaned asset folder taking up 9.13GB located at: /System/Library/AssetsV2/com_apple_MobileAsset_iOSSimulatorRuntime/c0d3fd05106683ba0b3680d4d1afec65f098d700.asset It contains SimulatorRuntimeAsset version 18.5 (Build 22F77). Active Version: My current Xcode setup is using version 26.2 (Build 23C54). I checked the plist files in the directory and found what seems to be the cause of the issue: The "Never Collected" Flag: The Info.plist inside the orphaned asset folder explicitly sets the garbage collection behavior to "NeverCollected": <key>__AssetDefaultGarbageCollectionBehavior</key> <string>NeverCollected</string> The Catalog Mismatch: The master catalog file (com_apple_MobileAsset_iOSSimulatorRuntime.xml) in the parent directory only lists the new version (26.2). Because the old version (18.5) is missing from this XML, Xcode and mobileassetd seem to have lost track of it entirely. What I Have Tried (All Failed) Xcode Components: The version 18.5 does not appear in Settings -> Components, so I cannot delete it via the GUI. Simctl: xcrun simctl list runtimes does not list this version. Running xcrun simctl runtime delete 22F77 fails with: "No runtime disk images or bundles found matching '22F77'." Manual Deletion: sudo rm -rf [path] fails with "Operation not permitted", presumably because /System/Library/AssetsV2 is SIP-protected. Third-party Tools: Apps like DevCleaner do not detect this runtime (likely because they only scan ~/Library or /Library, not /System/Library). Has anyone found a way to force the system (perhaps via mobileassetd or a specific xcrun flag) to re-evaluate this folder and respect a deletion request? I am trying to avoid booting into Recovery Mode just to delete a cache file. Any insights on how AssetsV2 handles these "orphaned" files would be appreciated.
19
7
2.0k
3h
UITextField and UITextView abnormally popped up the network permission application interface
in iOS26.4, after installing the app for the first time, opening the app and clicking on the UITextField input box will trigger the system to pop up the network permission application interface. This issue did not exist before iOS 26.3, only in iOS 26.4. This is a fatal bug where the network permission request box should not pop up when the developer has not called the network related API.
5
0
593
14h
Xcode 26.5 downloads darwin-arm64 Claude Agent binary on Intel Macs, causing exec failure misreported as code-signing error (workaround verified)
Xcode 26.5 downloads darwin-arm64 Claude Agent binary on Intel Macs, causing exec failure misreported as code-signing error (workaround verified) On Intel Macs, Xcode 26.5 (build 17F42) downloads the darwin-arm64 build of the Claude Agent rather than the darwin-x64 build that the vendor publishes at the same version. The arm64 binary fails to exec on Intel with NSPOSIXErrorDomain Code=86 ("Bad CPU type in executable") and Xcode's Intelligence subsystem then surfaces this in the UI as a code-signing / sandboxing failure. Replacing the downloaded binary with the parallel darwin-x64 build, and updating the agent's Info.plist checksum and URL to match, results in a fully functional Claude Agent in Xcode 26.5 on the same Intel Mac. This was verified end to end on the affected hardware. The agent downloader in Xcode should select the URL matching the host CPU architecture (e.g. by inspecting the result of uname -m or the equivalent in Foundation). This appears to be an isolated fix to whichever component constructs the agent's download URL in Xcode's Intelligence subsystem. Secondary suggestion: the user-facing error message "the code signing identity for the agent did not match expectations, or the agent violated sandboxing rules" should be revised when the underlying cause is an exec failure (EBADARCH or otherwise). The current wording is misleading and has produced considerable misdirected investigation in the developer community. USER-SIDE WORKAROUND (VERIFIED) The following restores Claude Agent functionality on this Intel Mac running Xcode 26.5. It may need re-applying after Xcode updates the agent, since the buggy download logic will run again. Quit Xcode. Download the parallel darwin-x64 binary from the vendor's release bucket (the same URL as in the Info.plist, with "darwin-arm64" replaced by "darwin-x64"). Make the destination writable, copy in the new binary, restore read-only mode. Recompute SHA-512 and update Info.plist's checksum and url fields with plutil. Relaunch Xcode. Workaround for Intel Mac users (verified) This restores a working Claude Agent in Xcode 26.5 on Intel until Xcode'sdownloader is fixed. Quit Xcode fully first. 1. Quit Xcode osascript -e 'tell application "Xcode" to quit' sleep 3 2. Download the correct-arch binary directly from Anthropic's release bucket curl -fL -o /tmp/claude-x64\ttps://storage.googleapis.com/claude-code-dist-86c565f3-f756-42ad-8dfa-d59b1c096819/claude-code-releases/2.1.118/darwin-x64/claude chmod +x /tmp/claude-x64 3. Verify it's the right arch and properly signed file /tmp/claude-x64 # → Mach-O 64-bit executable x86_64 codesign --verify --verbose /tmp/claude-x64 4. Replace the arm64 binary Xcode downloaded (destination is read-only by default) AGENT_DIR=~/Library/Developer/Xcode/CodingAssistant/Agents/XcodeVersions/17F42/claude chmod u+w "$AGENT_DIR/claude" cp -p /tmp/claude-x64 "$AGENT_DIR/claude" chmod a-w "$AGENT_DIR/claude" 5. Update Info.plist so its checksum and URL match the swapped binary NEW_CHECKSUM=$(shasum -a 512 "$AGENT_DIR/claude" | awk '{print $1}') plutil -replace checksum -string "$NEW_CHECKSUM" "$AGENT_DIR/Info.plist" plutil -replace url -string "https://storage.googleapis.com/claude-code-dist-86c565f3-f756-42ad-8dfa-d59b1c096819/claude-code-releases/2.1.118/darwin-x64/claude" "$AGENT_DIR/Info.plist" 6. Relaunch Xcode; the Claude Agent now works on Intel. Caveats Adjust 17F42 and 2.1.118 to whatever your Xcode build and agent version actually are. Check with ls ~/Library/Developer/Xcode/CodingAssistant/Agents/XcodeVersions/ and the version key in the Info.plist. The workaround may not survive an Xcode update. If Xcode refreshes the agent (new Claude Code version, new Xcode point release), the buggy download logic will run again and overwrite the x86_64 binary. The same procedure restores working state. Worth saving the commands above as a small shell script so you don't have to re-derive them next time. ENVIRONMENT Hardware: MacBook Pro 2019, Intel Core i9 (x86_64) macOS: 26.5 Xcode: 26.5 (build 17F42) Agent: Claude Code 2.1.118 Account: Claude Pro (claude.ai OAuth) I have tried unsuccessfully to request via 'Apple Feedback Assistant' that the above problem be looked into. This was their response: "Thank you for your feedback, it is noted. Engineering has determined that there are currently no plans to address this issue. This feature relies on the dedicated Neural Engine found on Macs with Apple silicon (M1 or newer) to provide the necessary performance and capabilities. As a result, systems that do not include this hardware are not supported for this specific workflow. You can close this feedback by selecting "Close Feedback" via the Actions button found above. This Feedback will no longer be monitored, and incoming messages will not be reviewed. " Clearly no one from the senior engineering team has looked at this or given it any consideration and they are not interested in making a trivial fix within Xcode so that it selects the correct Claude binary for download. It is frustrating that Apple's response cites the requirement for a 'neural engine found in M-series Macs' , when this is very clear to any developer that Claude does not make use of this feature and it self-evidently works on x86 hardware without it . If anyone has any ideas how to get a response from a helpful senior Xcode developer, I would be most interested. I can understand Apple are reluctant to put any effort into old hardware, however they still provide an up to date Xcode for the x86 platform and I don't think it is asking too much to fix a simple bug which would make life easier.
1
0
106
14h
SwiftData 100% crash when fetching history with codable (test included!)
SwiftData crashes 100% when fetching history of a model that contains an optional codable property that's updated: SwiftData/Schema.swift:389: Fatal error: Failed to materialize a keypath for someCodableID.someID from CrashModel. It is possible that this path traverses a type that does not work with append(), please file a bug report with a test. Would really appreciate some help or even a workaround. Code: import Foundation import SwiftData import Testing struct VaultsSwiftDataKnownIssuesTests { @Test func testCodableCrashInHistoryFetch() async throws { let container = try ModelContainer( for: CrashModel.self, configurations: .init( isStoredInMemoryOnly: true ) ) let context = ModelContext(container) try SimpleHistoryChecker.hasLocalHistoryChanges(context: context) // 1: insert a new value and save let model = CrashModel() model.someCodableID = SomeCodableID(someID: "testid1") context.insert(model) try context.save() // 2: check history it's fine. try SimpleHistoryChecker.hasLocalHistoryChanges(context: context) // 3: update the inserted value before then save model.someCodableID = SomeCodableID(someID: "testid2") try context.save() // The next check will always crash on fetchHistory with this error: /* SwiftData/Schema.swift:389: Fatal error: Failed to materialize a keypath for someCodableID.someID from CrashModel. It is possible that this path traverses a type that does not work with append(), please file a bug report with a test. */ try SimpleHistoryChecker.hasLocalHistoryChanges(context: context) } } @Model final class CrashModel { // optional codable crashes. var someCodableID: SomeCodableID? // these actually work: //var someCodableID: SomeCodableID //var someCodableID: [SomeCodableID] init() {} } public struct SomeCodableID: Codable { public let someID: String } final class SimpleHistoryChecker { static func hasLocalHistoryChanges(context: ModelContext) throws { let descriptor = HistoryDescriptor<DefaultHistoryTransaction>() let history = try context.fetchHistory(descriptor) guard let last = history.last else { return } print(last) } }
1
1
209
16h
App stuck in "Waiting for Review" for 4+ days — bug fix update
App name: Pandit AI Apple ID: 6752389345 Submitted: 19th May Current status: Waiting for Review (has not entered In Review) This is an update containing a bug fix for our live app. The build has been sitting in "Waiting for Review" for four days and has not yet been picked up by a reviewer. I've submitted expedited review requests, but the status hasn't changed. There are no messages in the Resolution Center and no communication from App Review. Is there a queue issue affecting this submission, or anything I can do to help it move forward? Any guidance would be appreciated. Thank you.
0
0
26
17h
StoreKit 2 Product.products always returns an empty list
All of a sudden both our development and production app stopped loading products for the subscription screens. Within our code I noticed that product.products is always returning 0 elements even after confirming product ids are correct and ensuring all agreements in App Store Connect are signed and active. What could be the issue?
Replies
0
Boosts
0
Views
2
Activity
13m
Notarizations stuck in progress over 24 hours
I made a small 20MB .pkg installer for some Logic Pro Drum Machine Designer patches so the user doesn't have to manually place the files by hand. Tried to notarize 3 times, all attempts have been stuck "in progress" since yesterday and can't seem to get any log files that might explain where things are getting stuck. Are the duplicate submissions causing this and if so is there a way to de-duplicate? My first time doing this so when notarization was hanging on the first attempt I thought I had done something incorrectly. Not sure how to troubleshoot this and would appreciate any guidance.
Replies
0
Boosts
0
Views
9
Activity
32m
iOS 26.5 breaks AppIntents with AppEnums defined in Swift Package
For some reason since iOS 26.5, a ControlWidgetButton or a Button in a widget configured with an AppIntent conforming to OpenIntent fails to receive its AppEnum parameter correctly if the intent and enum are defined inside a shared Swift Package. Tapping the control widget button opens the main application, but it doesn't pass the AppEnum parameter value in, leaving the app on its default screen instead of navigating to the intended view. This was working perfectly in iOS 26.4, where the app would launch and receive the correct enum case from the intent. No code, configuration, or scheme changes were made between the two runs, only the simulator/OS version differs. Has anyone else run into what seems to be a regression on iOS 26.5? I filed feedback with a sample project: FB22848510
Replies
0
Boosts
0
Views
7
Activity
34m
AssistiveTouch eye tracker HID over USB-C/iAP2 accepted by iPadOS, but gaze point mapping is wrong
I’m implementing an Apple AssistiveTouch eye tracker accessory for iPad over USB-C using iAP2 plus native HID Gaze Point reports. Current state: iAP2 authentication succeeds identification succeeds StartNativeHID is received AssistiveTouchInformation(IsEnabled=true) is received iPadOS enumerates the HID interface and consumes the interrupt IN reports The remaining issue is that the gaze-point behavior is not interpreted as direct screen coordinates. Repeated fixed gaze inputs produce deterministic but incorrect cursor motion, often appearing like orbiting or projection around a locus rather than stable placement. I have tested: the 119-byte Apple example HID descriptor from the Accessory Interface Specification two report-1 layouts: timestamp + x + y status + timestamp + x + y normalized and physical coordinate scaling verified on the wire that the intended report bytes are sent and consumed iPad console logs show internal model point (HID r) values and multiple derived Pointer positions for a single commanded point, which suggests the device is accepted but the gaze report semantics are still not what iPadOS expects. Questions: Is the example Gaze Point HID descriptor in the Apple Accessory Interface Specification sufficient as-is for iPadOS? What exact payload layout is expected for the Gaze Point report? Is a per-sample status byte required in the gaze input report? Are additional HID feature/input reports required for correct interpretation? I can provide: the exact HID descriptor bytes sample report payloads USB analyzer traces iPad console excerpts showing the resulting model-point and pointer projections
Replies
0
Boosts
0
Views
23
Activity
1h
SwiftUI MapKit
MapKit offers showsTraffic: Bool, which is great for displaying live traffic data on the map. However, MapPolyline sits above it, which makes it quite useless. Is this the expected behaviour?
Replies
7
Boosts
0
Views
449
Activity
1h
Custom Keyboard help
import UIKit class KeyboardViewController: UIInputViewController { // MARK: - Properties private var keyboardView: KeyboardView! private var heightConstraint: NSLayoutConstraint! private var hasInitialLayout = false // 存储系统键盘高度和动画参数 private var systemKeyboardHeight: CGFloat = 300 private var keyboardAnimationDuration: Double = 0.25 private var keyboardAnimationCurve: UIView.AnimationOptions = .curveEaseInOut // MARK: - Lifecycle override func viewDidLoad() { super.viewDidLoad() setupKeyboard() } override func viewWillAppear(_ animated: Bool) { super.viewWillAppear(animated) // 在视图显示前更新键盘高度,避免闪动 if !hasInitialLayout { hasInitialLayout = true } } override func viewDidAppear(_ animated: Bool) { super.viewDidAppear(animated) } // MARK: - Setup private func setupKeyboard() { // 创建键盘视图 keyboardView = KeyboardView() keyboardView.translatesAutoresizingMaskIntoConstraints = false view.addSubview(keyboardView) // 设置约束 - 确保键盘贴紧屏幕底部 NSLayoutConstraint.activate([ keyboardView.leftAnchor.constraint(equalTo: view.leftAnchor), keyboardView.rightAnchor.constraint(equalTo: view.rightAnchor), keyboardView.bottomAnchor.constraint(equalTo: view.bottomAnchor) ]) // 设置初始高度约束(使用系统键盘高度或默认值) let initialHeight = systemKeyboardHeight heightConstraint = keyboardView.heightAnchor.constraint(equalToConstant: initialHeight) heightConstraint.isActive = true } // MARK: - Layout Events override func viewDidLayoutSubviews() { super.viewDidLayoutSubviews() } override func viewSafeAreaInsetsDidChange() { super.viewSafeAreaInsetsDidChange() } // MARK: - 键盘高度请求 // 这个方法可以确保键盘扩展报告正确的高度给系统 override func updateViewConstraints() { super.updateViewConstraints() // 确保我们的高度约束是最新的 if heightConstraint == nil { let height = systemKeyboardHeight &gt; 0 ? systemKeyboardHeight : 216 heightConstraint = NSLayoutConstraint( item: self.view!, attribute: .height, relatedBy: .equal, toItem: nil, attribute: .notAnAttribute, multiplier: 0.0, constant: height ) heightConstraint.priority = UILayoutPriority(999) view.addConstraint(heightConstraint) } else { let height = systemKeyboardHeight &gt; 0 ? systemKeyboardHeight : 216 heightConstraint.constant = height } } } // MARK: - Keyboard View Implementation class KeyboardView: UIView { private var keysContainer: UIStackView! override init(frame: CGRect) { super.init(frame: frame) setupView() } required init?(coder: NSCoder) { super.init(coder: coder) setupView() } private func setupView() { backgroundColor = UIColor(red: 0.82, green: 0.84, blue: 0.86, alpha: 1.0) // 创建按键容器 keysContainer = UIStackView() keysContainer.axis = .vertical keysContainer.distribution = .fillEqually keysContainer.spacing = 8 keysContainer.translatesAutoresizingMaskIntoConstraints = false addSubview(keysContainer) // 添加约束 - 确保内容在安全区域内 NSLayoutConstraint.activate([ keysContainer.topAnchor.constraint(equalTo: safeAreaLayoutGuide.topAnchor, constant: 8), keysContainer.leftAnchor.constraint(equalTo: safeAreaLayoutGuide.leftAnchor, constant: 8), keysContainer.rightAnchor.constraint(equalTo: safeAreaLayoutGuide.rightAnchor, constant: -8), keysContainer.bottomAnchor.constraint(equalTo: safeAreaLayoutGuide.bottomAnchor, constant: -8) ]) // 添加键盘行 } }
Topic: UI Frameworks SubTopic: UIKit Tags:
Replies
5
Boosts
0
Views
221
Activity
1h
TestFlight not working for internal testing – affects all apps
Hi, I am an iOS developer and I am facing a critical issue with TestFlight that is affecting ALL of my applications, not just one. Issue: TestFlight is not working during internal testing for any of my apps I am unable to install or test any build through TestFlight The problem is consistently reproducible Example App Details: App Name: PDF Editor & PDF Compressor Version: 1.2 (Build 1) Build Status: Ready to Submit Testing Group: Internal (1 Tester) Invite Status: Accepted I already submitted a support case (Case ID: 102895219145) on May 20, 2026 but have not received any response yet. Has anyone else faced this issue? Any help would be greatly appreciated. Thank you.
Replies
0
Boosts
0
Views
19
Activity
1h
Stolen device
My iPhone got stolen and am trying to trace it location using find my apple but i couldn't get it. Any other options to trace it
Replies
0
Boosts
0
Views
24
Activity
2h
App live and searchable in App Store, but not selectable in Apple Ads
Hello, my app is live on the App Store and can be found in App Store search. However, when I try to create an Apple Ads campaign, the app does not appear as a selectable app/promotion option. App name: Zenbara Apple ID: 6760915770 App Store URL: https://apps.apple.com/de/app/zenbara/id6760915770 Country/region: Germany The app is available in Germany and searchable in the App Store, but it is not available in Apple Ads campaign creation. According to Apple Ads Help, a new app can take up to 24 hours to appear during campaign creation. This period has already passed. Any of you has an idea why the app is missing from the Apple Ads eligibility index or campaign creation index? Thank you.
Replies
0
Boosts
0
Views
29
Activity
2h
switching membership issue
Hello, I'm trying to switch my membership from individual to organization and filled out the form. After submitting the form, the page says We’ll review your request and get back to you within one (1) business day. but the issue is they haven't responded in a month. this happened twice so far and i contacted Apple support and they haven't answered yet as well. Today, i re-submitted the form again and it still says the same thing. I don't know what to do. I want to publish an application and the process has stopped because of this. Can someone help me please? Thanks in advance.
Replies
0
Boosts
0
Views
28
Activity
2h
anyone have this gltich where
anyone else have this gltich? my app seems to be in stuck state and has not been reviewed for a week now. help?
Replies
0
Boosts
0
Views
17
Activity
2h
Can't download files from file provider's folder if they are read-only
I face this issue only on macOS 26 and only on the Intel architecture. I'm unable to download files from a file provider's folder when I make them read-only. STEPS TO REPRODUCE Download the sample from https://developer.apple.com/documentation/fileprovider/synchronizing-files-using-file-provider-extensions?language=objc Follow the steps on the page to configure the project. Build the project. Run it. Add a domain. Open the domain's folder in the Finder. Move a file to the domain's folder. Right-click on the file in the domain's folder and select "Remove Download". Close the Finder's window with the domain's folder and kill all the "Provider" processes to get rid of running instances of the extension. Change Item's capabilities in Item.swift to make the items read-only: var result: NSFileProviderItemCapabilities = [ .allowsContentEnumerating, .allowsReading ] Rebuild the project and run it. Open the domain's folder and try to drag and drop the file from the extension's folder to, let's say, the Desktop folder. EXPECTED RESULT The file is copied ACTUAL RESULT A dialog pops up with text "The file “filename” cannot be downloaded. Do you want to skip it?" Stop/Skip
Replies
4
Boosts
0
Views
264
Activity
3h
Orphaned 9GB Simulator Runtime in /System/Library/AssetsV2 - Cannot Delete (SIP protected)
I have an orphaned asset folder taking up 9.13GB located at: /System/Library/AssetsV2/com_apple_MobileAsset_iOSSimulatorRuntime/c0d3fd05106683ba0b3680d4d1afec65f098d700.asset It contains SimulatorRuntimeAsset version 18.5 (Build 22F77). Active Version: My current Xcode setup is using version 26.2 (Build 23C54). I checked the plist files in the directory and found what seems to be the cause of the issue: The "Never Collected" Flag: The Info.plist inside the orphaned asset folder explicitly sets the garbage collection behavior to "NeverCollected": <key>__AssetDefaultGarbageCollectionBehavior</key> <string>NeverCollected</string> The Catalog Mismatch: The master catalog file (com_apple_MobileAsset_iOSSimulatorRuntime.xml) in the parent directory only lists the new version (26.2). Because the old version (18.5) is missing from this XML, Xcode and mobileassetd seem to have lost track of it entirely. What I Have Tried (All Failed) Xcode Components: The version 18.5 does not appear in Settings -> Components, so I cannot delete it via the GUI. Simctl: xcrun simctl list runtimes does not list this version. Running xcrun simctl runtime delete 22F77 fails with: "No runtime disk images or bundles found matching '22F77'." Manual Deletion: sudo rm -rf [path] fails with "Operation not permitted", presumably because /System/Library/AssetsV2 is SIP-protected. Third-party Tools: Apps like DevCleaner do not detect this runtime (likely because they only scan ~/Library or /Library, not /System/Library). Has anyone found a way to force the system (perhaps via mobileassetd or a specific xcrun flag) to re-evaluate this folder and respect a deletion request? I am trying to avoid booting into Recovery Mode just to delete a cache file. Any insights on how AssetsV2 handles these "orphaned" files would be appreciated.
Replies
19
Boosts
7
Views
2.0k
Activity
3h
VZVirtualMachineView window and system function keys
HI, I am trying to send system function keys like F10, F11 to VzVirtualMachineView window and it is not registering system assigned function keys. The function keys that are not assinged by mac are being send correctly. Is there a way i can send system assigned function keys to VZVirtualMachineView Window? Thanks and Regards
Replies
5
Boosts
0
Views
158
Activity
4h
Check appeal status & expected response time
Hi, I submitted an app review appeal on May 21. It has been over 60 hours now. I'm unsure if I viewed the submission success page. No confirmation email received, and no status update in App Store Connect. App Apple ID: 1308698895 Could you please confirm: 1.Whether my appeal has been successfully received 2.The estimated time to get a reply Thanks.
Replies
0
Boosts
0
Views
86
Activity
13h
UITextField and UITextView abnormally popped up the network permission application interface
in iOS26.4, after installing the app for the first time, opening the app and clicking on the UITextField input box will trigger the system to pop up the network permission application interface. This issue did not exist before iOS 26.3, only in iOS 26.4. This is a fatal bug where the network permission request box should not pop up when the developer has not called the network related API.
Replies
5
Boosts
0
Views
593
Activity
14h
Xcode 26.5 downloads darwin-arm64 Claude Agent binary on Intel Macs, causing exec failure misreported as code-signing error (workaround verified)
Xcode 26.5 downloads darwin-arm64 Claude Agent binary on Intel Macs, causing exec failure misreported as code-signing error (workaround verified) On Intel Macs, Xcode 26.5 (build 17F42) downloads the darwin-arm64 build of the Claude Agent rather than the darwin-x64 build that the vendor publishes at the same version. The arm64 binary fails to exec on Intel with NSPOSIXErrorDomain Code=86 ("Bad CPU type in executable") and Xcode's Intelligence subsystem then surfaces this in the UI as a code-signing / sandboxing failure. Replacing the downloaded binary with the parallel darwin-x64 build, and updating the agent's Info.plist checksum and URL to match, results in a fully functional Claude Agent in Xcode 26.5 on the same Intel Mac. This was verified end to end on the affected hardware. The agent downloader in Xcode should select the URL matching the host CPU architecture (e.g. by inspecting the result of uname -m or the equivalent in Foundation). This appears to be an isolated fix to whichever component constructs the agent's download URL in Xcode's Intelligence subsystem. Secondary suggestion: the user-facing error message "the code signing identity for the agent did not match expectations, or the agent violated sandboxing rules" should be revised when the underlying cause is an exec failure (EBADARCH or otherwise). The current wording is misleading and has produced considerable misdirected investigation in the developer community. USER-SIDE WORKAROUND (VERIFIED) The following restores Claude Agent functionality on this Intel Mac running Xcode 26.5. It may need re-applying after Xcode updates the agent, since the buggy download logic will run again. Quit Xcode. Download the parallel darwin-x64 binary from the vendor's release bucket (the same URL as in the Info.plist, with "darwin-arm64" replaced by "darwin-x64"). Make the destination writable, copy in the new binary, restore read-only mode. Recompute SHA-512 and update Info.plist's checksum and url fields with plutil. Relaunch Xcode. Workaround for Intel Mac users (verified) This restores a working Claude Agent in Xcode 26.5 on Intel until Xcode'sdownloader is fixed. Quit Xcode fully first. 1. Quit Xcode osascript -e 'tell application "Xcode" to quit' sleep 3 2. Download the correct-arch binary directly from Anthropic's release bucket curl -fL -o /tmp/claude-x64\ttps://storage.googleapis.com/claude-code-dist-86c565f3-f756-42ad-8dfa-d59b1c096819/claude-code-releases/2.1.118/darwin-x64/claude chmod +x /tmp/claude-x64 3. Verify it's the right arch and properly signed file /tmp/claude-x64 # → Mach-O 64-bit executable x86_64 codesign --verify --verbose /tmp/claude-x64 4. Replace the arm64 binary Xcode downloaded (destination is read-only by default) AGENT_DIR=~/Library/Developer/Xcode/CodingAssistant/Agents/XcodeVersions/17F42/claude chmod u+w "$AGENT_DIR/claude" cp -p /tmp/claude-x64 "$AGENT_DIR/claude" chmod a-w "$AGENT_DIR/claude" 5. Update Info.plist so its checksum and URL match the swapped binary NEW_CHECKSUM=$(shasum -a 512 "$AGENT_DIR/claude" | awk '{print $1}') plutil -replace checksum -string "$NEW_CHECKSUM" "$AGENT_DIR/Info.plist" plutil -replace url -string "https://storage.googleapis.com/claude-code-dist-86c565f3-f756-42ad-8dfa-d59b1c096819/claude-code-releases/2.1.118/darwin-x64/claude" "$AGENT_DIR/Info.plist" 6. Relaunch Xcode; the Claude Agent now works on Intel. Caveats Adjust 17F42 and 2.1.118 to whatever your Xcode build and agent version actually are. Check with ls ~/Library/Developer/Xcode/CodingAssistant/Agents/XcodeVersions/ and the version key in the Info.plist. The workaround may not survive an Xcode update. If Xcode refreshes the agent (new Claude Code version, new Xcode point release), the buggy download logic will run again and overwrite the x86_64 binary. The same procedure restores working state. Worth saving the commands above as a small shell script so you don't have to re-derive them next time. ENVIRONMENT Hardware: MacBook Pro 2019, Intel Core i9 (x86_64) macOS: 26.5 Xcode: 26.5 (build 17F42) Agent: Claude Code 2.1.118 Account: Claude Pro (claude.ai OAuth) I have tried unsuccessfully to request via 'Apple Feedback Assistant' that the above problem be looked into. This was their response: "Thank you for your feedback, it is noted. Engineering has determined that there are currently no plans to address this issue. This feature relies on the dedicated Neural Engine found on Macs with Apple silicon (M1 or newer) to provide the necessary performance and capabilities. As a result, systems that do not include this hardware are not supported for this specific workflow. You can close this feedback by selecting "Close Feedback" via the Actions button found above. This Feedback will no longer be monitored, and incoming messages will not be reviewed. " Clearly no one from the senior engineering team has looked at this or given it any consideration and they are not interested in making a trivial fix within Xcode so that it selects the correct Claude binary for download. It is frustrating that Apple's response cites the requirement for a 'neural engine found in M-series Macs' , when this is very clear to any developer that Claude does not make use of this feature and it self-evidently works on x86 hardware without it . If anyone has any ideas how to get a response from a helpful senior Xcode developer, I would be most interested. I can understand Apple are reluctant to put any effort into old hardware, however they still provide an up to date Xcode for the x86 platform and I don't think it is asking too much to fix a simple bug which would make life easier.
Replies
1
Boosts
0
Views
106
Activity
14h
Too long waiting for review
My app has been for review for 2 months now , and the support team is ignoring my emails any reason this is my app id 6757392645
Replies
0
Boosts
0
Views
86
Activity
15h
SwiftData 100% crash when fetching history with codable (test included!)
SwiftData crashes 100% when fetching history of a model that contains an optional codable property that's updated: SwiftData/Schema.swift:389: Fatal error: Failed to materialize a keypath for someCodableID.someID from CrashModel. It is possible that this path traverses a type that does not work with append(), please file a bug report with a test. Would really appreciate some help or even a workaround. Code: import Foundation import SwiftData import Testing struct VaultsSwiftDataKnownIssuesTests { @Test func testCodableCrashInHistoryFetch() async throws { let container = try ModelContainer( for: CrashModel.self, configurations: .init( isStoredInMemoryOnly: true ) ) let context = ModelContext(container) try SimpleHistoryChecker.hasLocalHistoryChanges(context: context) // 1: insert a new value and save let model = CrashModel() model.someCodableID = SomeCodableID(someID: "testid1") context.insert(model) try context.save() // 2: check history it's fine. try SimpleHistoryChecker.hasLocalHistoryChanges(context: context) // 3: update the inserted value before then save model.someCodableID = SomeCodableID(someID: "testid2") try context.save() // The next check will always crash on fetchHistory with this error: /* SwiftData/Schema.swift:389: Fatal error: Failed to materialize a keypath for someCodableID.someID from CrashModel. It is possible that this path traverses a type that does not work with append(), please file a bug report with a test. */ try SimpleHistoryChecker.hasLocalHistoryChanges(context: context) } } @Model final class CrashModel { // optional codable crashes. var someCodableID: SomeCodableID? // these actually work: //var someCodableID: SomeCodableID //var someCodableID: [SomeCodableID] init() {} } public struct SomeCodableID: Codable { public let someID: String } final class SimpleHistoryChecker { static func hasLocalHistoryChanges(context: ModelContext) throws { let descriptor = HistoryDescriptor<DefaultHistoryTransaction>() let history = try context.fetchHistory(descriptor) guard let last = history.last else { return } print(last) } }
Replies
1
Boosts
1
Views
209
Activity
16h
App stuck in "Waiting for Review" for 4+ days — bug fix update
App name: Pandit AI Apple ID: 6752389345 Submitted: 19th May Current status: Waiting for Review (has not entered In Review) This is an update containing a bug fix for our live app. The build has been sitting in "Waiting for Review" for four days and has not yet been picked up by a reviewer. I've submitted expedited review requests, but the status hasn't changed. There are no messages in the Resolution Center and no communication from App Review. Is there a queue issue affecting this submission, or anything I can do to help it move forward? Any guidance would be appreciated. Thank you.
Replies
0
Boosts
0
Views
26
Activity
17h