I'm having trouble with this Info.plist for Firebase Frameworks/FirebaseFirestoreInternal.framework/Info.plist unable to install It looks like Firebase removed Info.plist files in 10.20.0. and its causing this error below. Most of the online support says to update Cocafile PODs to not embed however I can't find any solutions for Package Manager. StackOverflow: https://stackoverflow.com/questions/64977628/all-framework-error-when-launch-framework-info-plist-no-such-file-or-directory/64979956#64979956 https://stackoverflow.com/questions/77888962/issue-trying-to-run-app-on-ios-simulator-missing-a-plist-from-firebase Error: App installation failed: Unable to Install “Replayology” Please try again later. Failed to load Info.plist from bundle at path /Users/chronicler/Library/Developer/CoreSimulator/Devices/A087805B-77FD-446A-96C5-9DCE2F813D60/data/Library/Caches/com.apple.mobile.installd.staging/temp.YGB5zA/extracted/Replayology.app/Frameworks/FirebaseFirestoreInternal.framework; Extra info about "/Users/chronicler/Library/Developer/CoreSimulator/Devices/A087805B-77FD-446A-96C5-9DCE2F813D60/data/Library/Caches/com.apple.mobile.installd.staging/temp.YGB5zA/extracted/Replayology.app/Frameworks/FirebaseFirestoreInternal.framework/Info.plist": Couldn't stat /Users/chronicler/Library/Developer/CoreSimulator/Devices/A087805B-77FD-446A-96C5-9DCE2F813D60/data/Library/Caches/com.apple.mobile.installd.staging/temp.YGB5zA/extracted/Replayology.app/Frameworks/FirebaseFirestoreInternal.framework/Info.plist: No such file or directory Details App installation failed: Unable to Install “Replayology” Domain: IXUserPresentableErrorDomain Code: 1 Failure Reason: Please try again later. Recovery Suggestion: Failed to load Info.plist from bundle at path /Users/chronicler/Library/Developer/CoreSimulator/Devices/A087805B-77FD-446A-96C5-9DCE2F813D60/data/Library/Caches/com.apple.mobile.installd.staging/temp.YGB5zA/extracted/Replayology.app/Frameworks/FirebaseFirestoreInternal.framework; Extra info about "/Users/chronicler/Library/Developer/CoreSimulator/Devices/A087805B-77FD-446A-96C5-9DCE2F813D60/data/Library/Caches/com.apple.mobile.installd.staging/temp.YGB5zA/extracted/Replayology.app/Frameworks/FirebaseFirestoreInternal.framework/Info.plist": Couldn't stat /Users/chronicler/Library/Developer/CoreSimulator/Devices/A087805B-77FD-446A-96C5-9DCE2F813D60/data/Library/Caches/com.apple.mobile.installd.staging/temp.YGB5zA/extracted/Replayology.app/Frameworks/FirebaseFirestoreInternal.framework/Info.plist: No such file or directory User Info: { DVTErrorCreationDateKey = "2025-05-29 23:54:11 +0000"; IDERunOperationFailingWorker = IDELaunchiPhoneSimulatorLauncher; SimCallingSelector = "installApplication:withOptions:error:"; } Unable to Install “Replayology” Domain: IXUserPresentableErrorDomain Code: 1 Failure Reason: Please try again later. Recovery Suggestion: Failed to load Info.plist from bundle at path /Users/chronicler/Library/Developer/CoreSimulator/Devices/A087805B-77FD-446A-96C5-9DCE2F813D60/data/Library/Caches/com.apple.mobile.installd.staging/temp.YGB5zA/extracted/Replayology.app/Frameworks/FirebaseFirestoreInternal.framework; Extra info about "/Users/chronicler/Library/Developer/CoreSimulator/Devices/A087805B-77FD-446A-96C5-9DCE2F813D60/data/Library/Caches/com.apple.mobile.installd.staging/temp.YGB5zA/extracted/Replayology.app/Frameworks/FirebaseFirestoreInternal.framework/Info.plist": Couldn't stat /Users/chronicler/Library/Developer/CoreSimulator/Devices/A087805B-77FD-446A-96C5-9DCE2F813D60/data/Library/Caches/com.apple.mobile.installd.staging/temp.YGB5zA/extracted/Replayology.app/Frameworks/FirebaseFirestoreInternal.framework/Info.plist: No such file or directory Failed to load Info.plist from bundle at path /Users/chronicler/Library/Developer/CoreSimulator/Devices/A087805B-77FD-446A-96C5-9DCE2F813D60/data/Library/Caches/com.apple.mobile.installd.staging/temp.YGB5zA/extracted/Replayology.app/Frameworks/FirebaseFirestoreInternal.framework; Extra info about "/Users/chronicler/Library/Developer/CoreSimulator/Devices/A087805B-77FD-446A-96C5-9DCE2F813D60/data/Library/Caches/com.apple.mobile.installd.staging/temp.YGB5zA/extracted/Replayology.app/Frameworks/FirebaseFirestoreInternal.framework/Info.plist": Couldn't stat /Users/chronicler/Library/Developer/CoreSimulator/Devices/A087805B-77FD-446A-96C5-9DCE2F813D60/data/Library/Caches/com.apple.mobile.installd.staging/temp.YGB5zA/extracted/Replayology.app/Frameworks/FirebaseFirestoreInternal.framework/Info.plist: No such file or directory Domain: MIInstallerErrorDomain Code: 35 User Info: { FunctionName = "-[MIBundle _validateWithError:]"; LegacyErrorString = PackageInspectionFailed; SourceFileLine = 64; } System Information macOS Version 15.2 (Build 24C101) Xcode 16.3 (23785) (Build 16E140) Timestamp: 2025-05-29T18:54:11-05:00

Hi! I am getting this error since an xcode update when trying to build my project. Module 'audioplayers' not found (in target 'Runner' from project 'Runner'). Thank you in advance for any help!

Where are the local documentation files location on MacOS? None of the existing data on the internet is applicable anymore. Trying to bundle documentation for use in an LLM and the developer site is unusable for crawling. Thanks! *.docset

Just wondering if it is possible to configure a secondary macbook to act as a run destination in Xcode, similar to how you would configure an iPhone as a run destination. I have tried connecting my device via USB-C and I can see that my macbook detects the second macbook via USB but it does not show up when trying to add devices in Xcode. I suppose this flow might not be supported?

We using below command to run unit test and collect coverage: xcodebuild -workspace Demo.xcworkspace -scheme VideoTests -configuration Debug -derivedDataPath ../build/derivedData -destination 'platform=iOS Simulator,id=E6630007-570B-4DEB-A023-2BCE91116A8D' -resultBundlePath './fastlane/test_output/VideoTests.xcresult' -enableCodeCoverage YES -testPlan 'Video' test-without-building | tee '/Users/rcadmin/Library/Logs/scan/VideoTests.log' | xcbeautify -q --is-ci and using xcrun llvm-cov show command to generate coverage report: xcrun llvm-cov show /build/unit-test/coverage/libraries/merged/video.o -instr-profile=/app/ios/build/derivedData/Build//ProfileData/E6630007-570B-4DEB-A023-2BCE91116A8D/video.profdata -show-branches count -show-expansions -show-line-counts -use-color -format=html -output-dir coverage and the html report does not include branch coverage: how to generate the branch coverage?

An internal error occurs when executing the xcodebuild -list command targeting a Swift Package. This behavior is new in Xcode 16.3 and was not present in the previous version, Xcode 16.2. cd ~/Developer mkdir Playground cd Playground swift package init xcodebuild -list Command line invocation: /Applications/Xcode-16.3.0.app/Contents/Developer/usr/bin/xcodebuild -list Resolve Package Graph ** INTERNAL ERROR: Unable to load workspace '/Users/treastrain/Developer/Playground' ** Uncaught Exception: -[Swift.__SwiftDeferredNSArray intersectsSet:]: unrecognized selector sent to instance 0x600001aab5e0 Stack: 0 __exceptionPreprocess (in CoreFoundation) 1 objc_exception_throw (in libobjc.A.dylib) 2 -[NSObject(NSObject) __retain_OA] (in CoreFoundation) 3 ___forwarding___ (in CoreFoundation) 4 _CF_forwarding_prep_0 (in CoreFoundation) 5 -[DVTCoreDevice(DVTCoreDeviceIDE) deviceSupportsBuildable:buildParameters:error:] (in IDEFoundation) 6 -[DVTCoreDevice(DVTCoreDeviceIDE) supportedArchitecturesForBuildableContext:buildParameters:error:] (in IDEFoundation) 7 _IDERunDestinationsForBuildableUsingDeviceWithBuildParameters (in IDEFoundation) 8 -[IDERunDestinationManager runDestinationsForScheme:schemeCommands:executionEnvironment:eligibleOnly:genericOnly:architectureVisibility:] (in IDEFoundation) 9 IDESchemeDetermineAvailableRunDestinations (in IDEFoundation) 10 -[IDEScheme _actuallyInvalidateAvailableRunDestinations] (in IDEFoundation) 11 addSchemeAndMakeActiveIfNecessary #1 (result:error:) in IDESwiftPackage.generateScheme(with:buildable:additionalBuildables:unsetRunnable:makeActive:orderHint:) (in IDESwiftPackageCore) 12 IDESwiftPackage.generateScheme(with:buildable:additionalBuildables:unsetRunnable:makeActive:orderHint:) (in IDESwiftPackageCore) 13 IDESwiftPackage.generateSchemes(_:isRootPackage:) (in IDESwiftPackageCore) 14 IDESwiftPackage.update(from:graphHasErrors:delegate:) (in IDESwiftPackageCore) 15 specialized IDESPMWorkspaceDelegate.rootPackagesDidUpdate(packages:graphHasErrors:modelGraphSynchronizerToken:) (in IDESwiftPackageCore) 16 closure #1 in IDESPMWorkspaceDelegate.packageGraphDidFinishAction(_:duration:result:) (in IDESwiftPackageCore) 17 partial apply for closure #1 in IDESPMWorkspaceDelegate.disableWorkspaceContentSynchronization(during:) (in IDESwiftPackageCore) 18 <deduplicated_symbol> (in DVTFoundation) 19 <deduplicated_symbol> (in DVTFoundation) 20 thunk for @escaping @callee_guaranteed () -> () (in DVTFoundation) 21 __58-[DVTModelObjectGraph performBlockCoalescingModelChanges:]_block_invoke (in DVTFoundation) 22 -[DVTModelGraphTransactionScope performTransaction:] (in DVTFoundation) 23 -[DVTModelObjectGraph performBlockCoalescingModelChanges:] (in DVTFoundation) 24 DVTModelObjectGraph.performBlockCoalescingModelChanges<A>(_:) (in DVTFoundation) 25 IDESPMWorkspaceDelegate.disableWorkspaceContentSynchronization(during:) (in IDESwiftPackageCore) 26 IDESPMWorkspaceDelegate.packageGraphDidFinishAction(_:duration:result:) (in IDESwiftPackageCore) 27 <deduplicated_symbol> (in IDESwiftPackageCore) 28 SPMWorkspace.packageGraphActionFinished(_:) (in SwiftPM) 29 closure #2 in closure #3 in SPMWorkspace.processPackageGraphActionsInBackgroundIfNeeded(canProcessPackageGraphActions:) (in SwiftPM) 30 <deduplicated_symbol> (in SwiftPM) 31 <deduplicated_symbol> (in SwiftPM) 32 <deduplicated_symbol> (in SwiftPM) 33 completeTaskWithClosure(swift::AsyncContext*, swift::SwiftError*) (in libswift_Concurrency.dylib) zsh: abort xcodebuild -list Environments: % xcodebuild -version Xcode 16.3 Build version 16E140 % swift --version swift-driver version: 1.120.5 Apple Swift version 6.1 (swiftlang-6.1.0.110.21 clang-1700.0.13.3) Target: arm64-apple-macosx15.0

Xcode 16 insists on showing deprecations of this type: Some.xib SF Symbol 'doc.on.doc' is deprecated, use 'document.on.document' instead. The problem is that the XIBs in question are set with a Deployment Target of macOS 12, where "document.on.document" actually isn't available and produces a missing image. So the warnings are wrong, as they ignore the deployment target set on the XIB. I filed a bug against this long ago and it was ignored. Having given up... does anyone know how to disable this particular warning?

Hello, I recently enrolled in the Apple Developer Program and created an App ID with the bundle ID com.echo.eyes.voice. I am trying to enable Speech Recognition in the App ID capabilities list, but the option does not appear — even after waiting over a week since my membership was activated. I’ve already: Confirmed my Apple Developer account is active Checked the Identifiers section in the Developer portal Tried editing the App ID, but Speech Recognition is not listed Contacted both Developer Support and Developer Technical Support (Case #102594089120), but was told to post here for help My app uses Capacitor + the @capacitor-community/speech-recognition plugin. I need the com.apple.developer.speech-recognition entitlement to appear so I can use native voice input in iOS. I would really appreciate help from an Apple engineer or anyone who has faced this issue. Thank you, — Daniel Colyer

我们这边收到的一个通知，是设置的订阅明明是6块，苹果通知过来的是renewalPrice是6000，个别是6000，也有600的，如何设置renewalPrice这个字段是除1000还是除100换算

I am building an iOS app with the App ID: com.echo.eyes.app I have a paid Apple Developer membership and have followed all correct procedures, including: Adding com.apple.developer.speech-recognition manually to the App.entitlements file Setting Info.plist keys for microphone and speech permissions Assigning my Apple Developer Team to the project Setting App/App.entitlements under Code Signing Entitlements Despite all this, Xcode automatic signing fails, and I receive the error: vbnet Copy Edit Provisioning profile 'iOS Team Provisioning Profile: com.echo.eyes.app' doesn't include the com.apple.developer.speech-recognition entitlement. I am unable to add the entitlement via the Capabilities section, and no method I try will allow provisioning to succeed. Please update this App ID to include the required entitlement in the provisioning profile. This issue is preventing all voice recognition functionality. Thank you.

Hello. For the last few months I have been facing a situation for which I do not understand either the reason or the solution. Here is an example for the last few weeks: In App Store Connect it shows 214 crashes for the last week In Xcode it shows 56 crashes for the last 2 weeks without stack traces (NO_CRASH_STACK) In Firebase Crashlytics there is not a single crash. When I click "Show in Finder" it opens a folder with .xccrashpoint files. As far as I understood from the instructions on posting crash reports - this is not what is needed. Interesting point: it looks like the errors occur on iOS 15-16 devices. I have several questions: Why is the number of crashes in Xcode different from the number in App Store Connect? Where are the other crashes? How can I understand what the problem is if there are no stack traces in Xcode?

So Xcode has projects. And I breakup my code/libraries/targets into those. So why after 20 years of Xcode, can a workspace, that holds projects not display the same project opened in another workspace? The workspace redirects all output the project would normally generate in DerivedData to a completely different folder by default. What this means is I have to shut one workspace, and then open the other workspace with a different set of projects to see the ones that are shared. The workspace can't build because it can't open the project shared with another one that is open. VS sln files don't have this issue, so why do workspace files.

No, seriously, what's the excuse there? How many apps never got to iOS because of this? I already have a computer I'm happy with, buying a Mac just for code is too much. Yet I really wish I could develop for my iPad, because I love my iPad. So here I am, doing android dev for my phone, hopping someday, I can make iOS dev too.

Hello, I am currently developing a game streaming application using ReplayKit and Broadcast Upload Extension. I would like to ask for your assistance regarding capturing snapshots of a WKWebView in the upload extension without adding it to a visible view hierarchy. From my understanding, calling takeSnapshot(with:) on a WKWebView that is not added to the view hierarchy generally works for simple web pages. However, when it comes to more complex web content — such as animations or WebGL — the snapshot returns a blank or static image. I believe this is because rendering such content requires access to the GPU, which is not fully available when the web view is off-screen. That said, I’ve observed that certain apps are able to capture live animated web content inside their broadcast upload extensions, even when the main app is terminated. This suggests that the snapshot is not being generated by the main app or from a remote server — especially since the network activity confirms the content is served locally (via localhost or local IP). Given this, I believe there must be a way to achieve GPU-accelerated rendering for WKWebView directly within the upload extension context, without attaching it to the app's UI. I would greatly appreciate any guidance, APIs, or recommended techniques that could help me achieve this behavior correctly and within system limitations. Thank you in advance for your support. I look forward to your advice. Warm regards,

Hi everyone, I recently built an iOS application that fetches the healthkit data with the BGProcessingTask. It is working as expected in the debug with the physical device connected but its not working in Testflight. I printed out the logs but they don't show that the background process's running. Here is my code snippet. func registerBackgroundTask() { BGTaskScheduler.shared.register(forTaskWithIdentifier: taskIdentifier, using: nil) { task in LogManager.shared.addBackgroundProcessLog("registering the background task...") print("registering the background task...") self.handleBackgroundTask(task: task as! BGProcessingTask) } } func scheduleBackgroundHealthKitSync() { print("scheduling background task...") LogManager.shared.addBackgroundProcessLog("scheduling background task...") let request = BGProcessingTaskRequest(identifier: taskIdentifier) request.earliestBeginDate = Date(timeIntervalSinceNow: 60 * 1) request.requiresNetworkConnectivity = true request.requiresExternalPower = false do { try BGTaskScheduler.shared.submit(request) print("BGProcessingTask scheduled") LogManager.shared.addBackgroundProcessLog("BGProcessingTask scheduled") } catch { print("Failed to schedule task: \(error)") LogManager.shared.addBackgroundProcessLog("Failed to schedule task: \(error)", isError: true) print(LogManager.shared.backgroundProcessLogs) } } func handleBackgroundTask(task: BGProcessingTask) { LogManager.shared.addBackgroundProcessLog("handleBackgroundTask triggered") print("handleBackgroundTask triggered") let dispatchGroup = DispatchGroup() dispatchGroup.enter() // Reschedule the background sync for the next time scheduleBackgroundHealthKitSync() var taskCancelled = false // Handling expiration task.expirationHandler = { taskCancelled = true LogManager.shared.addBackgroundProcessLog("Background task expired", isError: true) print("Background task expired") dispatchGroup.leave() } let healthKitManager = HealthKitManager.shared // Start the background sync operation healthKitManager.fetchAndSendAllTypes() { success in if success { LogManager.shared.addBackgroundProcessLog("HealthKit sync completed successfully") print("HealthKit sync completed successfully") } else { LogManager.shared.addBackgroundProcessLog("HealthKit sync failed", isError: true) print("HealthKit sync failed") } dispatchGroup.leave() } // Notify when all tasks are completed dispatchGroup.notify(queue: .main) { // Check if the task was cancelled using your own flag or state if taskCancelled { task.setTaskCompleted(success: false) // Fail the task if it was cancelled } else { task.setTaskCompleted(success: true) // Complete successfully if not cancelled } LogManager.shared.addBackgroundProcessLog("Background task ended with status: \(taskCancelled == false)") print("Background task completed with success: \(taskCancelled == false)") // Logs success or failure } } Here are the logs from my device. scheduling background task... BGProcessingTask scheduled

This really shouldn't be this difficult. Here's the situation: We had a card linked to our Apple Developer account, which expired. It had already seen 2 successful membership purchases. We had auto-renewal turned on for the membership, which failed due to the expired card. I was unable to capture new payment details for about 2 days (battling with various Apple payment pages to get the new card added). But finally managed to do so. Now, there is no way to disable auto-renewal, and no way to trigger renewal. The membership is in expired status. We can't post updates, we can't take apps live. We have several clients eagerly awaiting publication of their apps. And Apple Support has been silent for over two weeks despite numerous requests. Anyone have any idea how to resolve this? I've tried almost every option described on every forum post.

Start from clean iOS 18.4 simulator. Application tried to request authorisation from user for microphone access. Clicking allow caused the application crashed. Used Swift 6. Report Identifier FB17686864.

Hello There! I will try to be very active! (I had nothing to type lol)

I am encountering an issue while running my CarPlay app in the simulator using CPListTemplate. On app launch, when I tap on the first item in the list and then tap on the second item, both items remain selected instead of only the latest tapped item. This behavior does not align with the expected single-item selection functionality. Has anyone else faced this issue? Is there a workaround or a known resolution for this behavior?