Search results for

build disappears

49,257 results found

Post

Replies

Boosts

Views

Activity

Subscription issue
My app / subscription gets rejected with the following: Guideline 2.1 - Performance - App Completeness We have returned your in-app purchase products to you as the required binary was not submitted. When you are ready to submit the binary, please resubmit the in-app purchase products with the binary. and Your first subscription must be submitted with a new app version. Create your subscription, then select it from the app’s In-App Purchases and Subscriptions section on the version page before submitting the version to App Review. Once your binary has been uploaded and your first subscription has been submitted for review, additional subscriptions can be submitted from the Subscriptions section. Learn More ...ive tried all kinds. I archive a new build, upload it, update the app information top show new build so it ties in...and still nothing works. it is incredible frustrating. Can anyone help please. Ive wasted days on this
2
0
151
1w
SwiftUI macOS Preview Crash When Using Custom Row Directly Inside List
I’ve hit a strange SwiftUI preview crash that happens on macOS previews when using a view inside a List’s ForEach, resulting in the error Fatal Error in TableViewListCore_Mac2.swift. Only crashes macOS preview - iPhone/iPad preview doesn't crash. Doesn't crash when actually running the app. Here’s a minimal reproducible example, causing the preview to crash. XCode: Version 26.0.1 (17A400) MacOS: 26.0.1 (25A362) import SwiftUI struct Item: Identifiable { let id = UUID() let name: String } struct ItemRow: View { let item: Item var body: some View { HStack { Button(action: {}) { Image(systemName: play) } Text(item.name) Spacer() ProgressView() } } } struct ContentView: View { @State private var items = [ Item(name: Item A), Item(name: Item B), ] var body: some View { List { ForEach(items) { item in ItemRow(item: item) } } } } #Preview(Content view) { ContentView() } #Preview(Item row) { ItemRow(item: Item(name: Item A)) } If I wrap the row in a container, like this: ForEach(items) { item in ZStack { ItemRow(item
1
0
63
1w
Reply to Xcode 26 RC unable to compile asset catalogs on CI
I'm running into the same issue (Xcode 26.0.1 on macOS 15.7.1). I've added a retry logic to my build script. It now just retries on error 65. Of course each failed attempt takes a minute or two. This is very frustrating. set +e while true; do xcrun xcodebuild archive (...) case $? in 0) break ;; 65) echo Received Status 65. Probably asset compiler bug. Trying again! ;; *) exit $? ;; esac done It usually works after 3-5 attempts. But that's ridiculous!
1w
App Store Connect UI Broken - Cannot Attach Build or Subscription for 10+ Days
I've been unable to submit my app for over 10 days due to App Store Connect UI issues. I've contacted Apple Support (Case #102715606681) but haven't received a response in 3 days. App Details: App: IMPULSE404 Bundle ID: com.sophie.impulse404 Apple ID: 6752914939 Version: 1.0 (Prepare for Submission) Build 12 uploaded successfully to TestFlight Issues: Cannot change build: Build 12 is available in TestFlight, but I cannot switch from build 11 to build 12 in my app version. The usual option/button to change builds is not appearing. In-App Purchases section unresponsive: When I click Select the in-app purchases or subscriptions... nothing happens. I cannot attach my subscription (impulse404_premium_monthly_v2) which is Ready to Submit. What I've Tried: Multiple browsers (Safari, Chrome) Cleared cache and cookies Logged out and back in Restarted computer Different devices Waited 3+ days Impact: This is blocking my entire app launch and costing me significant m
4
0
142
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
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
App Rejected Under Guideline 4.3(a) - “Spam” for Unofficial Telegram Client with Unique Features
Hi everyone, I’m currently working on a project based on the Telegram iOS open-source code. My goal is to build an unofficial Telegram client with Telegram’s permission (they have publicly allowed third-party clients under their open-source license). My app includes unique new features and UI improvements that are not present in the official Telegram app. Essentially, it’s Telegram plus additional features — built from the official source, but extended significantly. However, when I try to submit my app to the App Store, Apple rejects the build under Guideline 4.3(a) - Design - Spam with this message: “We still noticed your app shares a similar binary, metadata, and/or concept as apps submitted to the App Store by other developers, with only minor differences. Submitting similar or repackaged apps is a form of spam that creates clutter and makes it difficult for users to discover new apps.” I completely understand Apple’s intent to prevent low-effort clones or spam apps. However, in my case,
1
0
133
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
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
73
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