Search results for

build disappears

49,250 results found

Post

Replies

Boosts

Views

Activity

'tabViewBottomAccessory' leaves an empty accessory area when conditionally hidden
We use SwiftUI's .tabViewBottomAccessory in our iOS apps for displaying an Audio MiniPlayer View (like in the Apple Music App). TabView(selection: $viewModel.selectedTab) { // Tabs here } .tabViewBottomAccessory { if viewModel.showAudioMiniPlayer { MiniPlayerView() } } The Problem This code works perfectly on iOS 26.0. When viewModel.showAudioMiniPlayer is false, the accessory is completely hidden. However, on iOS 26.1 (23B5059e), when 'viewModel.showAudioMiniPlayer' becomes false, the MiniPlayerView disappears, but an empty container remains, leaving a blank space above the tab bar. Is this a known Bug in iOS 26.1 and are there any effective workarounds?
Topic: UI Frameworks SubTopic: SwiftUI
3
0
141
1w
Cluster not displaying in CarPlay POI template on iPhone 14 with iOS 26.0.1
I am experiencing an issue with the CarPlay POI template in my CarPlay application. On my iPhone 14 running iOS 26.0.1, the clustering of POIs on the CarPlay map is not displaying at all. However, this issue only affects this specific model and OS version. The same app works correctly on an iPhone 14 with iOS 18.5 and on an iPhone 16 Pro Max with iOS 26.0.1. There are no code changes between builds for each device.
Topic: UI Frameworks SubTopic: UIKit Tags:
1
0
58
1w
App Switcher briefly flashes or disappears on iPadOS 26.0.1
I’m experiencing a strange issue with the App Switcher on my iPad. When I swipe up from the bottom to open the App Switcher, the apps that should be running sometimes don’t appear — they briefly flash for a split second and then disappear. The App Switcher itself stays open, but it shows no app cards. Here are some details: Device: iPad Pro (11-inch, 2nd generation) iPadOS version: 26.0.1 Reproducibility: Happens intermittently Steps to reproduce: Open several apps. Swipe up from the bottom and pause to show the App Switcher. Sometimes, the app cards flash for a moment and then disappear, leaving the App Switcher empty. Expected behavior: The App Switcher should display all running apps consistently. Actual behavior: The App Switcher appears, but the app cards briefly flash and disappear, leaving a blank screen. I’ve seen a few similar reports on the Apple Support Community, but I’m not sure if this is a known issue in iPadOS 26.0.1. Has anyone else encountered this problem? Any con
0
0
23
1w
'tabViewBottomAccessory' leaves an empty container when conditionally hidden
We use SwiftUI's .tabViewBottomAccessory in our iOS apps for displaying an Audio MiniPlayer View (like in the Apple Music App). TabView(selection: $viewModel.selectedTab) { // Tabs here } .tabViewBottomAccessory { if viewModel.showAudioMiniPlayer { MiniPlayerView() } } The Problem This code works perfectly on iOS 26.0. When 'viewModel.showAudioMiniPlayer' is 'false', the accessory is completely hidden. However, on iOS 26.1 (23B5059e), when 'viewModel.showAudioMiniPlayer' is 'false', the MiniPlayerView disappears, but an empty container remains, leaving a blank space above the tab bar. Is this a known Bug in iOS 26.1 and are there any effective workarounds or should I just wait until Apple fixed it?
Topic: Design SubTopic: General
3
0
959
1w
Xcode Cloud issue (ibtoold crash?)
Hi, our builds with a Test action in Xcode Cloud are failing because of an internal Xcode Cloud crash. We see the red cloud with an X icon, that indicates that it's an Xcode Cloud issue, and the message says The Test - iOS action could not complete due to an error. The error may not occur on rebuild. but this has been happening for a while now, and for repeated builds. In the artifacts there is a crash log apparently related to the ibtoold process, has anybody had this issue before? Thanks
5
0
284
1w
Unable to enable Apple Pay for App Clip – “relationship 'undefined'” error when adding capability
Hey everyone, hoping someone here has run into this before. I have a fully functional App Clip (com.didyoucatchit.app.Clip) linked to my main app (com.didyoucatchit.app). The Clip builds and runs perfectly, but I’m seeing issues trying to enable Apple Pay for it. When I try to link my Merchant ID under the “On Demand Install Capable” capability in the Apple Developer portal, I get this error: A relationship in the provided entity is not allowed for this request. The relationship 'undefined' can not be included in a 'bundleIdCapabilities' request. Here’s what I have already configured and confirmed: App Clip capabilities in Xcode include: Apple Pay Payment Processing Associated Domains (appclips:app.didyoucatchit.com) Provisioning profile includes: Apple Pay Payment Processing Associated Domains In-App Purchase On-Demand Install Capable Entitlements file for the Clip: com.apple.developer.associated-domains appclips:app.didyoucatchit.com com.apple.developer.in-app-payments merchant.com.didyoucatchit
0
0
64
1w
Reply to Creating Swift Package with binaryTarget that has dependencies
Let's examine this log: objc[39953]: Class _TtC10KingfisherP33_6AA794C9C370CDB07604B4D8B99AEAA312BundleFinder is implemented in both /Users/Name/Library/Developer/Xcode/DerivedData/TestApp-capvhjiqxrdgdnbevpkajicnjpcs/Build/Products/Debug-iphonesimulator/WallpaperKit.framework/WallpaperKit (0x100e8bbf8) and /Users/Name/Library/Developer/CoreSimulator/Devices/E0AF13C2-874C-47B9-B864-72AF3E4D5D4B/data/Containers/Bundle/Application/AF32011A-92E7-4E26-9A97-9F0C25C07863/TestApp.app/TestApp.debug.dylib (0x101a543b0). This may cause spurious casting failures and mysterious crashes. One of the duplicates must be removed or renamed. You have mangled Swift class names there, and they exist in two places, so the system doesn't know which implementation to use. While the crux of your question is Why are these symbols still given an _implementationOnly import, there's something subtle here — this log is being generated by the Objective-C runtime, for a Swift class — notice the system logging this is named objc at
1w
Reply to Capturing NWConnection in Receive Closure – Risk of Strong Reference Cycle?
My understanding is that NWConnection holds a reference to the closure, and if I capture the NWConnection instance inside the closure, the closure will have a reference back to the connection, which, according to my understanding, creates a strong reference cycle. Is my understanding correct? Sort of. You're right that it would be holding a strong reference; however, the key word in the documentation for receive(minimumIncompleteLength..) and receiveMessage(completion:) is single: Schedules a single ... completion handler In both cases, what NWConnection is actually doing is: Retaining the block for later use. Calling the block when the data is received. Releasing the block after it's been called once. That leads to here: If so, how can we break the strong reference cycle — using a capture list, or is there any other way as well? Strictly speaking, I believe there's already a retain cycle here as I don't think NWConnection will destroy itself as long as there is a pending receive block. However, NWConnection
1w
Reply to Multipeer Connectivity connection is flaky on iOS 26
While updating our test devices to iOS 26, we noticed that the connection between devices is flaky. Often when connecting to a peer from a device running iOS 26, we can observe the invite coming through and when accepting said invite, both ends go to .connecting state and a while later go back to .notConnected within the peer(_ peerID: MCPeerID, didChange state: MCSessionState) function. This happens regularly, and retrying the invitation process several times usually resolves it. Have you filed a bug on this, and if so, what is the bug number? Does anyone have any information or guidance on how to resolve this issue? Well, unfortunately, my (and Quinn's) longstanding advice has been to move to a new API and stop using MultipeerConnectivity. Quinn actually has an extended forum post describing how to move to the Network framework. I'd also suggest taking a look at the Building a custom peer-to-peer protocol sample, which uses the Network framework to implement something very similar to what Multipeer
1w
Forwarded from App Review ticket 102715606681 – still unresolved.”
My message - URGENT - ESCALATE - App Store Connect UI Broken for 10+ Days I have already had to remove a subscription and do a new one as the option for a new in-app purchase was not appearing (I tired to explain that but no one is listening) I still cannot proceed with my app submission. New critical issues: My app version is frozen now. I have tried on a new browser, deleting caches but nothing is working. Every build is costing me money. I email and no response from Monday. Cannot change build from 11 to 12 in app version - no way of deleting last build - no red circle appears. In-App Purchases section is completely unresponsive - cannot attach subscription I have build 12 ready in TestFlight. I have subscription impulse404_premium_monthly_v2 ready to submit. But App Store Connect UI is broken and preventing me from attaching either. This is now costing me significant money in delays. Please escalate this immediately. MY RESPONSE FROM APPLE - Hello, Thank you for making
0
0
35
1w
Share Extension Lifetime and SwiftData
I have an app that uses a Share Extension that allows the user to share videos, from Files and Photos etc., the video URL and some related data is then persisted with SwiftData and synchronized with CloudKit. This code has worked consistently for a long time although recently, with iOS 26 and recent builds of iOS 18, I have observed that the video is either not saved to SwiftData (iOS 26.0), or available locally when the app is opened on the same device where the share occurred, but not synchronized to other devices (iOS 18.7 and iOS 26.1 beta). Assuming the video is opened locally after being shared into the app, it is typically synchronized with CloudKit to other devices although it's not as reliable as it should be. Is there a reliable approach in the Share Extension to ensure that the data is saved to the local SwiftData database and then synchronized with CloudKit. I suspect it could be that the lifetime of the Share Extension has become even more constrained in recent OS updates that the proces
1
0
51
1w
iOS 26 UITargetedPreview not responding to touches
We have a UICollectionView whose cells have custom context menu highlight previews. In the delegate method collectionView(_:contextMenuConfiguration:highlightPreviewForItemAt:), we build a UITargetedPreview whose custom view contains some action buttons. Up until iOS 18, our setup has been working perfectly. But since iOS 26, the custom view is not responding to touches. When the user taps one of its buttons, the context menu gets dismissed as if the touch was outside of the custom view. Is there any UICollectionView-related API change in version 26?
Topic: UI Frameworks SubTopic: UIKit Tags:
1
0
72
1w