“missing package product”

Hello Apple Support Team, We are seeing a production crash on iOS 26 devices that appears to originate from Apple system frameworks rather than application code. 1. Crash Details OS Version: iOS 26.x App built with: Xcode 16 Devices: Multiple models (not device-specific) Exception Type: SIGSEGV SEGV_ACCERR Fault Address: 0x0000000000000100 Crashed Thread: 4 (network background queue) Crash trace summary: Last Exception : 0 libobjc.A.dylib _objc_release_x8 + 8 1 libboringssl.dylib _nw_protocol_boringssl_deallocate_options + 92 2 Network 0x000000019695207c 0x00000001968dc000 + 483452 3 libswiftCore.dylib __swift_release_dealloc + 56 4 libswiftCore.dylib bool swift::RefCounts >::doDecrementSlow<(swift::PerformDeinit)1>(swift::RefCountBitsT<(swift::RefCountInlinedness)1>, unsigned int) + 152 5 Network 0x0000000196951f6c 0x00000001968dc000 + 483180 6 Network 0x0000000196952000 0x00000001968dc000 + 483328 7 libswiftCore.dylib __swift_release_dealloc + 56 8 libswiftCore.dylib bool swift::RefC

Hello, I am planning to distribute my iOS app as an Unlisted App. I would like to confirm the following: If users access the standard App Store URL in the format below: https://apps.apple.com/app/idXXXXXXXXXX Will users be able to reach the Unlisted app’s App Store product page via this URL? Or is the specific Unlisted distribution link generated by App Store Connect required for access? My goal is to ensure that in-app update guidance directs users to the correct App Store page. Thank you for your support.

we have been offered a phone call by apple and we are going to do that but we need to be as ready as possible so here is the rejection we are getting We think we have addressed the issues but are unable to clear this message Notes from App Review 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. Next Steps Learn more about offering in-app purchases in App Store Connect Help. This is the original message Guideline 3.1.2 - Business - Payments - Subscriptions Issue Description The submission did not include all the required information for apps offering auto-renewable subscriptions. The following information needs to be included in the App Store metadata: A functional link to the Terms of Use (EULA). If you are using the standard Apple Terms of Use (EULA), include a link to the Terms of Use in the App

I have several macOS applications that use CloudKit. I need to test and finds out what happens when the user signs out of their iCloud account. That's because the application may lose data after signing out and then signing in again. Every time I do that, it'll take 15, 20 minutes... I don't time it, but it takes quite a gigantic time to sign out as the spinner keeps rolling. Why does it take so long to just sign out? This sign out effect is untestable because it takes a long time to sign out of an iCloud account and then make changes to the code and then test again. In case you need to know, my system version is Sequoia 15.7.

Hello everyone, I’m running into an issue where a partial sheet repeatedly presents and dismisses in a loop. Setup The main screen is presented using fullScreenCover From that screen, a button triggers a standard partial-height sheet The sheet is presented using .sheet(item:) Expected Behavior Tapping the button should present the sheet once and allow it to be dismissed normally. Actual Behavior After the sheet is triggered, it continuously presents and dismisses. What I’ve Verified The bound item is not being reassigned in either the parent or the presented view There is no .task, .onAppear, or .onChange that sets the item again The loop appears to happen without any explicit state updates Additional Context I encountered a very similar issue when iOS 26.0 was first released At that time, moving the .sheet modifier to a higher parent level resolved the issue The problem has now returned on iOS 26.4 beta I’m currently unable to reproduce this in a minimal sample project, which makes it unclear whether: this i

Hello, I’m currently experiencing a major issue while migrating my Apple Developer account from an Individual account to an Organization account. The migration process has been ongoing for more than 3 weeks, and during this transition: My app release is delayed. I am unable to submit updates. I also cannot use the old (individual) account normally because it appears to be locked in this transition state. This situation is critically affecting our product launch timeline. We already provided all requested documentation, including D-U-N-S verification and company details. However, the account status remains in transition, and no clear timeline has been provided. My main concerns: Is it normal for this migration to take more than 3 weeks? Is there any way to temporarily regain publishing capability while the migration is processed? Is there a specific escalation channel for cases where the transition blocks production releases? Case IDs: Case ID: 102820894024 Case ID: 2000010840072 We have an u

I realize there are already several posts here about the unusually long review times for app submissions. There are some replies from Apple stating that they are looking into it or that specific issues have been resolved, but the problem persists and no one seems to understand what is actually happening or what can be done to improve the situation. I have been experiencing the same issue over the past six weeks. My app (submission ID: 75aed892-ee07-49e1-b62b-fdd54f1b04f8) was rejected because the reviewer stated that it needed “citations, such as links to resources.” I therefore added citations with functional links to online resources directly on the page where the claims were made, yet my app was rejected again with exactly the same copy-and-paste feedback. I then asked for clarification, but my question has remained unanswered for a week. There seems to be a fundamental problem in the App Store review process. For me, it has become a cumbersome issue, as the unexpectedly long response times are causing me

My code that streams buffers into AVAudioPlayerNode is stuttering when the buffer is finished and before the next one is played. while engine.isRunning { let framesToCopy = min(buffer.frameLength - framePosition, Self.BufferSize) let srcRaw = UnsafeRawPointer(srcPtr) let playbackBuffer = AVAudioPCMBuffer(pcmFormat: buffer.format, frameCapacity: Self.BufferSize)! let playbackPtr = playbackBuffer.floatChannelData![0] let destRaw = UnsafeMutableRawPointer(mutating: playbackPtr) memcpy(destRaw, srcRaw, Int(framesToCopy) * MemoryLayout.stride) srcPtr = srcPtr.advanced(by: Int(framesToCopy)) playbackBuffer.frameLength = framesToCopy await player.scheduleBuffer(playbackBuffer, at: nil, options: [], completionCallbackType: .dataRendered) } I've tried to schedule multiple buffers at once using a combination of both the synchronous and async versions of scheduleBuffer because I thought the delay might be but it still stutters and the data copied into the playbackBuffer matches the source buffer. I've tried all combinat

After nearly ten years in Android development, I finally built a native iOS app, sharing the journey publicly while learning Swift and SwiftUI, using AI selectively, and finding the platform familiar yet different in tooling, concurrency, and culture. I reached production without initially buying a developer account and faced a stricter, iterative App Store review process than the Play Store, with several rejections that ultimately clarified Apple’s quality standards and expectations.