This wasn't happening until I updated Xcode to 16.2 (I'm using Sequoia 15.2). When I run any Mac app, I get these errors: Can't find or decode reasons Failed to get or decode unavailable reasons Can't find or decode disabled use cases I even got these errors running "Hello, world" which tells me that either I need to reinstall or there is a bug. Thanks for any help, -Ashley

In Xcode 16.2, I am trying to add a folder by reference but I can't find the good old option 'reference files in place' in the pull down menu (only the options 'Copy files to destination' and 'Move files to destination' are present. Is it expected? Thanks

I recently got some plugins from Universal Audio, and have licensed them properly through both UA and iLok manager. Whenever I try to load up the plugins (specifically from UA) in GarageBand, it first says that "NSCreateObjectFileImageFromMemory-p47UEwps” because the developper can not be verified. After clicking either 'show in finder' or 'okay', it opens the plugin in a form without its GUI and showing that it is not licensed (even though it is). It also displays error code 100001. I have tried only some basic stuff to troubleshoot like restarting the DAW/my computer and reinstalling/relicensing the softwares. I don't know if the macOS version has anything to do with it but for some reason I just can't get it to work.

Unable to distribute the App via Intune, When tried to install the App on Intune enrolled device. Gets error: Unable to install “App Name”. This app cannot be installed because its integrity could not be verified. Verified Bundle ID is getting updated and Sign-in shows successful. Mac OS Build - 13.7.2 (22H313) XCode Version: 15.1 (15C65) Provisioning Profile renewed this week Distribution Certificate Valid till 2027

This is using Xcode 16.2 (16C5032a), MacOS 15.2, on MacbookPro 16 M1 Pro. I have two repositories, one for an application and another one for a framework. The repository framework is integrated into the application one as git submodule. I was going to push the submodule to Github using Xcode git integration. It detects some conflicts and ask to pull. I pull. A window appears with some conflicting files (5 or 6). Review them. While reviewing something in Xcode crashed, but as Xcode was still up and running, ignored the crash. Decided to cancel the conflicts window and inspect my local files. Pull again but this time I decided to pull both repos. Review the conflicting changes and decided to cancel again to continue by hand in a terminal. Then, I notice that the project for the submodule is in red and that the "Changes" tab shows a bunch of files with and admiration mark. I go to the submodule folder in Finder and... everything inside the submodule folder was gone, disappeared, lost... everything, even the ".git" folder (only remained a binary folder for a component I use for the framework but is empty). I decided to run a recovery tool. It finds nothing to recover inside that folder, nothing. A lot of files even from years ago but nothing inside that folder? how is that possible? I filled a Feedback assistant issue: FB16307182 Could it be possible that Xcode "moved" everything to another place (I'm desperate so I'm starting to think in absurd explanations) Thanks

A new app I submitted to review was rejected due to a crash. I cannot reproduce the crash, even running it on exact the same device model used by App Review. So I need to symbolicate the ips crash log they provided me. Using MacSymbolicate and the archive located using Xcode Organizer I was able to partially symbolicate the crash log. To fully symbolicate the crash log, however, according to MacSymbolicate, I would need two more symbol files, which can't be located, because they relate to system frameworks (SwiftData and _SwiftData_SwiftUI). I have tried to follow the instructions provided on https://developer.apple.com/documentation/xcode/adding-identifiable-symbol-names-to-a-crash-report but I had no success. It seems to me that the instructions contained there for symbolicating using Xcode do not apply for crash logs downloaded from appstoreconnect after an App Review rejection. Also, the instructions seem to be out of date, e.g. "To symbolicate in Xcode, click the Device Logs button in the Devices and Simulators window.": This button was replaced by "Open Recent Logs", which opens what seems to be a different window (according to some online research). Is it possible to fully symbolicate such an ips file downloaded from App Review team? If so, how can this be achieved? Thanks This is how the partially symbolicated crash log looks like: Hardware Model: iPad13,16 ... AppStoreTools: 16C5031b Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd [1] ... OS Version: iPhone OS 18.2.1 (22C161) Release Type: User Report Version: 104 Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes: 0x0000000000000001, 0x000000018c100e2c Termination Reason: SIGNAL 5 Trace/BPT trap: 5 Terminating Process: exc handler [6226] Triggered by Thread: 0 Thread 0 name: Dispatch queue: com.apple.main-thread Thread 0 Crashed: 0 libswiftCore.dylib 0x18c100e2c _assertionFailure(_:_:file:line:flags:) + 264 1 SwiftData 0x24fa6f3b4 0x24fa4a000 + 152500 ... 14 SwiftData 0x24fa89700 0x24fa4a000 + 259840 15 _SwiftData_SwiftUI 0x250cd34e4 0x250cce000 + 21732 16 _SwiftData_SwiftUI 0x250cd1364 0x250cce000 + 13156 17 XXX 0x10451f7ac closure #1 in closure #2 in closure #1 in PaymentsMonthView.body.getter (in XXX) (PaymentsMonthView.swift:119) + 1324972 18 XXX 0x10451ea14 closure #1 in PaymentsMonthView.body.getter (in XXX) (PaymentsMonthView.swift:99) + 1321492 19 SwiftUICore 0x24fd5d304 specialized ViewBodyAccessor.updateBody(of:changed:) + 1240 20 SwiftUICore 0x24fd5cd4c closure #1 in DynamicBody.updateValue() + 600 21 SwiftUICore 0x24fd5c008 DynamicBody.updateValue() + 928 ... ... Thread 0 crashed with ARM Thread State (64-bit): x0: 0x000000011128b208 x1: 0x0000000200000003 x2: 0x0000000000000001 x3: 0x00000001130be744 x4: 0xfffffffffe1cd413 x5: 0x0000000000000013 x6: 0x0000000000000020 x7: 0x00000000000007fc x8: 0xfffffffe00000000 x9: 0x0000000200000003 x10: 0x0000000000000003 x11: 0x0000000000000000 x12: 0x00180080004019e0 x13: 0x00100000004017fc x14: 0x00000001046d23e0 x15: 0x00000000000001e0 x16: 0x952d0001130bde00 x17: 0x00000000020007fc x18: 0x0000000000000000 x19: 0x000000024fb661e0 x20: 0x000000011128b200 x21: 0x0000000000000000 x22: 0x000000000000000b x23: 0x000000000000001d x24: 0x0000000000000040 x25: 0x000000024fb64790 x26: 0xf000000000000977 x27: 0x0000000000000000 x28: 0x000000024fb64750 fp: 0x000000016ba188f0 lr: 0x000000018c100e2c sp: 0x000000016ba18820 pc: 0x000000018c100e2c cpsr: 0x60001000 far: 0x0000000000000000 esr: 0xf2000001 (Breakpoint) brk 1 Binary Images: 0x1043dc000 - 0x104633fff Locador arm64 <78fc8961d731321ba0c8f9bb051109c5> /private/var/containers/Bundle/Application/FE1C10C5-49C1-4022-860A-6C3515E2F8BB/Locador.app/Locador 0x1047fc000 - 0x104807fff libobjc-trampolines.dylib arm64e <be05652226b13a508ad193ac99fcdc9c> /private/preboot/Cryptexes/OS/usr/lib/libobjc-trampolines.dylib 0x18c0c9000 - 0x18c66afff libswiftCore.dylib arm64e <e9b1dc6b7fef3bbbb083f4e8faaa53df> /usr/lib/swift/libswiftCore.dylib 0x24fa4a000 - 0x24fb88ff7 SwiftData arm64e <90275b26954b349996ff44ada39f0358> /System/Library/Frameworks/SwiftData.framework/SwiftData 0x250cce000 - 0x250cebff8 _SwiftData_SwiftUI arm64e <d250fe30854c3f1c85fc8a89dec5d484> /System/Library/Frameworks/_SwiftData_SwiftUI.framework/_SwiftData_SwiftUI 0x24fcf8000 - 0x2508d4fff SwiftUICore arm64e <647b91f1620d3741bd708f9f26b5674b> /System/Library/Frameworks/SwiftUICore.framework/SwiftUICore 0x1ba831000 - 0x1ba874fff AttributeGraph arm64e <5eeff865ac123665a9dba9d612eb0e9f> /System/Library/PrivateFrameworks/AttributeGraph.framework/AttributeGraph 0x19220e000 - 0x1934d0fff SwiftUI arm64e <0b283f5831ae385f9c8ff128fd0e30b8> /System/Library/Frameworks/SwiftUI.framework/SwiftUI 0x1902f8000 - 0x19220dfff UIKitCore arm64e <f80c6ee450ca346f90ebbb3da9817503> /System/Library/PrivateFrameworks/UIKitCore.framework/UIKitCore 0x18dadc000 - 0x18e01ffff CoreFoundation arm64e <6a60be13e6573beca9acba239ae29862> /System/Library/Frameworks/CoreFoundation.framework/CoreFoundation 0x1dacec000 - 0x1dacf4fff GraphicsServices arm64e <f4e7a885f4913721862dc57403f4d821> /System/Library/PrivateFrameworks/GraphicsServices.framework/GraphicsServices 0x1b3d31000 - 0x1b3db413f dyld arm64e <4eb7459fe23738ce82403f3e2e1ce5ab> /usr/lib/dyld 0x0 - 0xffffffffffffffff ??? unknown-arch <00000000000000000000000000000000> ??? 0x1df105000 - 0x1df13efe3 libsystem_kernel.dylib arm64e <e3965df1a3a3374a94eaf86739c5cc8e> /usr/lib/system/libsystem_kernel.dylib 0x18c6e1000 - 0x18d411fff Foundation arm64e <7274dde368d634a08e677726e1265e80> /System/Library/Frameworks/Foundation.framework/Foundation 0x2185fc000 - 0x218608ff3 libsystem_pthread.dylib arm64e <b2fe0dfa67de3d7282676c42073e0e8d> /usr/lib/system/libsystem_pthread.dylib 0x1958ce000 - 0x19594dffb libsystem_c.dylib arm64e <8d425c7257c93e54a1e1e243cbdfc446> /usr/lib/system/libsystem_c.dylib EOF

The BUNDLE_DISPLAY_NAME of my app changes (between Testing, Staging, Production) so that it's obvious to testers etc. which varian they are using. The name contains unicode space to ensure the OS doesn't apply kerning to the spacing within the app name. If this is put directly into the info.plist then on the iPhone desktop it's displayed as desired i.e. if the info.plist contains My Application Name Then on the iPhone desktop it displays as: My Application Name However if the name is defined in an .xcconfig file as BUNDLE_DISPLAY_NAME = Xfinity Call Guard And the info.plist contains $(BUNDLE_DISPLAY_NAME) Then the name is displayed on the iPhone desktop as My Application N.... Is there a way to specify the name with the unicode characters within an .xcconfig and get that to appear as spaces on the desktop?

Hello, I am working on updating my system for Xcode but it has hanged here from last 4 hours I checked my internet. Thanks Zippy Games

Due to legal issues, our build machine is not connected to the Internet. We built the app through the "xcodebuild" command, and we have all the supplies for the build without internet connection. Certificate for valid deployment on keychain (including private key) Provisioning Profiles Disable the ability to automatically sign on to build settings. After updating to xcode16.0, I found that the build doesn't work at all. When I checked the release notes(xcod16.0), I saw that the provisioning profile needs to be newly issued and then built. When I issued and built a new provisioning profile, the app build was successful, but we found that it took more than twice the build time. When I look at the build log, it is exposed, and it is estimated that there is a long wait. The stage where this log comes out GatherProvisioningInputs The moment you start exporting after the archive has been completed 1.GatherProvisioningInputs 13-Jan-2025 12:31:13 2025-01-13 12:31:13.072 xcodebuild[36909:161529200] DVTDeveloperAccountManager: Failed to load credentials for CC992AE6-495A-419C-B6B8-65D10F340DAE: Error Domain=DVTDeveloperAccountCredentialsError Code=0 "Invalid credentials in keychain for CC992AE6-495A-419C-B6B8-65D10F340DAE, missing Xcode-Username" UserInfo={NSLocalizedDescription=Invalid credentials in keychain for CC992AE6-495A-419C-B6B8-65D10F340DAE, missing Xcode-Username} 13-Jan-2025 12:31:13 2025-01-13 12:31:13.078 xcodebuild[36909:161529200] DVTDeveloperAccountManager: Failed to load credentials for D604A570-36EF-438B-BDEE-7D097892F46F: Error Domain=DVTDeveloperAccountCredentialsError Code=0 "Invalid credentials in keychain for D604A570-36EF-438B-BDEE-7D097892F46F, missing Xcode-Username" UserInfo={NSLocalizedDescription=Invalid credentials in keychain for D604A570-36EF-438B-BDEE-7D097892F46F, missing Xcode-Username} 13-Jan-2025 12:31:13 2025-01-13 12:31:13.085 xcodebuild[36909:161529200] DVTDeveloperAccountManager: Failed to load credentials for mymailadress: Error Domain=DVTDeveloperAccountCredentialsError Code=0 "Invalid credentials in keychain for mymailadress, missing Xcode-Token" UserInfo={NSLocalizedDescription=Invalid credentials in keychain for mymailadress, missing Xcode-Token} The moment you start exporting after the archive has been completed 13-Jan-2025 12:39:59 ** ARCHIVE SUCCEEDED ** 13-Jan-2025 12:39:59 13-Jan-2025 12:40:01 2025-01-13 12:40:01.028 xcodebuild[44083:161711515] [MT] IDEDistribution: -[IDEDistributionLogging _createLoggingBundleAtPath:]: Created bundle at path "/var/folders/zv/mn5wc_kx19n19vntm4mwqv800000gn/T/NewLotteCard Release_2025-01-13_12-40-01.025.xcdistributionlogs". 13-Jan-2025 12:40:02 2025-01-13 12:40:02.016 xcodebuild[44083:161711515] [MT] IDEDistribution: Command line name "app-store" is deprecated. Use "app-store-connect" instead. 13-Jan-2025 12:40:03 2025-01-13 12:40:03.287 xcodebuild[44083:161713365]  DVTDeveloperAccountManager: Failed to load credentials for CC992AE6-495A-419C-B6B8-65D10F340DAE: Error Domain=DVTDeveloperAccountCredentialsError Code=0 "Invalid credentials in keychain for CC992AE6-495A-419C-B6B8-65D10F340DAE, missing Xcode-Username" UserInfo={NSLocalizedDescription=Invalid credentials in keychain for CC992AE6-495A-419C-B6B8-65D10F340DAE, missing Xcode-Username} 13-Jan-2025 12:40:03 2025-01-13 12:40:03.291 xcodebuild[44083:161713365]  DVTDeveloperAccountManager: Failed to load credentials for D604A570-36EF-438B-BDEE-7D097892F46F: Error Domain=DVTDeveloperAccountCredentialsError Code=0 "Invalid credentials in keychain for D604A570-36EF-438B-BDEE-7D097892F46F, missing Xcode-Username" UserInfo={NSLocalizedDescription=Invalid credentials in keychain for D604A570-36EF-438B-BDEE-7D097892F46F, missing Xcode-Username} 13-Jan-2025 12:40:03 2025-01-13 12:40:03.295 xcodebuild[44083:161713365]  DVTDeveloperAccountManager: Failed to load credentials for 7E18031A-9964-4A42-9F5C-6D36B08ACD40: Error Domain=DVTDeveloperAccountCredentialsError Code=0 "Invalid credentials in keychain for 7E18031A-9964-4A42-9F5C-6D36B08ACD40, missing Xcode-Username" UserInfo={NSLocalizedDescription=Invalid credentials in keychain for 7E18031A-9964-4A42-9F5C-6D36B08ACD40, missing Xcode-Username} 13-Jan-2025 12:40:03 2025-01-13 12:40:03.300 xcodebuild[44083:161713365]  DVTDeveloperAccountManager: Failed to load credentials for mymailadress: Error Domain=DVTDeveloperAccountCredentialsError Code=0 "Invalid credentials in keychain for mymailadress, missing Xcode-Token" UserInfo={NSLocalizedDescription=Invalid credentials in keychain for mymailadress, missing Xcode-Token} 13-Jan-2025 12:41:04 2025-01-13 12:41:04.323 xcodebuild[44083:161713365]  IDEDistribution: Failed to log in with account "(null)" while checking for an App Store Connect account (Error Domain=DVTServicesAccountBasedSessionErrorDomain Code=1 "Unable to log in with account ''." UserInfo={NSLocalizedFailureReason=Unable to log in with account ''., NSLocalizedRecoverySuggestion=An unexpected failure occurred while logging in (Underlying error code -1001)., DVTDeveloperAccountErrorAccount=<DVTAppleIDBasedDeveloperAccount: 0x6000037a8e80; username=''>, NSUnderlyingError=0x600003eb9920 {Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo={_kCFStreamErrorCodeKey=-2102, NSUnderlyingError=0x600003ebd290 {Error Domain=kCFErrorDomainCFNetwork Code=-1001 "(null)" UserInfo={_kCFStreamErrorCodeKey=-2102, _kCFStreamErrorDomainKey=4}}, _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask <23649340-3ED0-4D97-A0E7-3F46ED30721F>.<1>, _NSURLErrorRelatedURLSessionTaskErrorKey=( 13-Jan-2025 12:41:04 "LocalDataTask <23649340-3ED0-4D97-A0E7-3F46ED30721F>.<1>" 13-Jan-2025 12:41:04 ), NSLocalizedDescription=The request timed out., NSErrorFailingURLStringKey=https://developerservices2.apple.com/services/QH65B2/viewDeveloper.action?clientId=XABBG36SBA, NSErrorFailingURLKey=https://developerservices2.apple.com/services/QH65B2/viewDeveloper.action?clientId=XABBG36SBA, _kCFStreamErrorDomainKey=4}}}) 13-Jan-2025 12:42:05 2025-01-13 12:42:05.319 xcodebuild[44083:161713365]  IDEDistribution: Failed to log in with account "(null)" while checking for an App Store Connect account (Error Domain=DVTServicesAccountBasedSessionErrorDomain Code=1 "Unable to log in with account ''." UserInfo={NSLocalizedFailureReason=Unable to log in with account ''., NSLocalizedRecoverySuggestion=An unexpected failure occurred while logging in (Underlying error code -1001)., DVTDeveloperAccountErrorAccount= The xcode version cannot be updated due to obfuscation solution issues, I would like to ask if you have any ideas. thank you

I have an xCode project called Vision + CoreML I wanted add some charts into it so I started installing cocoapad for the first time I followed all the steps from installing the latest ruby version to running pod install The critical .xcworkspace had been never created no matter how many times pod install was run. It is nowhere to be found. Could anyone advise me on what went wrong here? Here are some files used to generate Podfile platform :ios, '15.0' target 'Vision + CoreML' do use_frameworks! # Comment the next line if you don't want to use dynamic frameworks pod 'Alamofire', '~> 5.6' # Pods for Vision + CoreML pod 'Charts' end and here is the command prompt output ls MacBook-Pro-3:NotAbgabe myusername$ ls App Main View Configuration Models Documentation Podfile Extensions README.md Image Predictor Vision+Core-ML.xcodeproj LICENSE I ran all the commands under the NotAbgabe folder. Not sure if xcworkspace is hidden somewhere between the files

Could not launch “App Name” Domain: IDELaunchErrorDomain Code: 20 Recovery Suggestion: LaunchServices has returned error -54. Please check the system logs for the underlying cause of the error. User Info: { DVTErrorCreationDateKey = "2024-12-27 12:16:34 +0000"; DVTRadarComponentKey = 113722; IDERunOperationFailingWorker = IDELaunchServicesLauncher; } The operation couldn’t be completed. (OSStatus error -54.) Domain: NSOSStatusErrorDomain Code: -54 User Info: { "_LSFunction" = "_LSOpenStuffCallLocal"; "_LSLine" = 4224; }

unable to add for review the items below are required to start the review process: new apps and app updates must be built with the latest public (gm) versions of xcode, and the ios, macos, watchos, and tvos sdks. apps built with

I must be missing something here. I want to put a landscape image in a geometry reader that contains a ZStack that contains an image and an overlay centred on top of the Image. I would like the ZStack and GeoReader's sizes to be the size of Image. (ie I want geometry.size to be the size of the image, which can be used to control the offset of the overlay's position.) Unfortunately the ZStack also includes the space above the image (ie the top safeArea) and the GeometryReader also includes all the space below the Image. (so geometry.size.height is greater than the height of Image) I've gone down rabbit holes of adding other items above/below, but I don't seem to be able to prevent the GeometryReader from being vertically greedy. eg the Text(" ") above the ZStack in the VStack solves the ZStack claiming the top safe area. But adding Text(" ") below the ZStack does not prevent the GeometryReader from claiming more vertical space below the image. Any/all guidance greatly appreciated. struct ContentView: View { var body: some View { VStack { // Text(" ") GeometryReader { geometry in ZStack { Image( uiImage: .init(imageLiteralResourceName: "LandscapeSample") ) .resizable() .aspectRatio(contentMode: .fit) Text("Hello, world!") .background(.white) } .background(.red) } .background(.blue) // Text(" ") } } }

I have an iOS application view that contains an AVCaptureSession, AVCaptureVideoPreviewLayer (created with the AVCaptureSession), and a UIImageView (in the backend the app takes the output of the AVCaptureSession, runs it through a Semantic Segmentation model, and displays the output in the UIImageView). When I pause the app and run the “Debug View Hierarchy”, it shows the UIImageView, the relevant buttons and labels. However, it does not seem to show AVCaptureVideoPreviewLayer that I have set up in my application. Is there some special set up that needs to be done to be able to view Camera Related features? The following is part of the view code, a component that is used to render the AVCaptureVideoPreviewLayer (not sure if this is enough, please let me know if its not): class CameraViewController: UIViewController { var session: AVCaptureSession? var frameRect: CGRect = CGRect() var rootLayer: CALayer! = nil private var previewLayer: AVCaptureVideoPreviewLayer! = nil init(session: AVCaptureSession) { self.session = session super.init(nibName: nil, bundle: nil) } required init?(coder: NSCoder) { super.init(coder: coder) } override func viewDidLoad() { super.viewDidLoad() setUp(session: session!) } private func setUp(session: AVCaptureSession) { previewLayer = AVCaptureVideoPreviewLayer(session: session) previewLayer.videoGravity = AVLayerVideoGravity.resizeAspectFill previewLayer.frame = self.frameRect DispatchQueue.main.async { [weak self] in self!.view.layer.addSublayer(self!.previewLayer) //self!.view.layer.addSublayer(self!.detectionLayer) } } } struct HostedCameraViewController: UIViewControllerRepresentable{ var session: AVCaptureSession! var frameRect: CGRect func makeUIViewController(context: Context) -> CameraViewController { let viewController = CameraViewController(session: session) viewController.frameRect = frameRect return viewController } func updateUIViewController(_ uiView: CameraViewController, context: Context) { } }

Dear Sirs, I'm searching for the most straightforward way to identify the root of a "Publishing changes from within view updates is not allowed, this will cause undefined behavior." warning. It is a complex SwiftUI project and I think there should be a better way than just try and error with disabling/removing and enabling/adding different screen elements to check if the warning still is shown. I tried to set a symbolic breakpoint for "os_log" in my XCode project and indeed this is triggered right before the warning appears but the callstack doesn't give me a direct hint to the part of my code which causes this warning. What would be the most direct way and is there something like an exception handler in such cases? Thanks and best regards, Johannes

I'm using SwiftData with an @Model and am also using an @ModelActor. I've fixed all concurrency issues and have migrated to Swift 6. I am getting a console error that I do not understand how to clear. I get this error in Swift 6 and Swift 5. I do not experience any issue with the app. It seems to be working well. But I want to try to get all issues taken care of. I am using the latest Xcode beta. error: the replacement path doesn't exist: "/var/folders/1q/6jw9d6mn0gx1znh1n19z2v9r0000gp/T/swift-generated-sources/@_swiftmacro_17MyAppName14MyModelC4type18_PersistedPr> opertyfMa.swift"

I am editing my iOS project in Xcode 16 and want to use the "Swift Compiler - Upcoming Features" section of the build settings to selectively enable the new Swift 6 language features. I have read the instructions for doing this and have dowloaded an Apple sample project and can see that section under the project and target-level Build Settings in the sample project However, when I open my Xcode project in XCode 16 that section does not appear. Is there any way for me to influence how Xcode 16 displays the build settings? In fact, no "Swift Compiler" sections appear at all under my project Build Settings (All | Combined). There is a "User-Defined" section that has the Swift Version, Compilation Mode and Optimization level. The project itself is several years old and was on a very old project version. I have upgraded my project document format to "Xcode 16" but it made no difference. I have compared my project and the sample project in a text editor and both seem to have similar structure. I tried removing unused and outdated settings from my project but that also had no effect. Is there an alternative to deleting my project file and adding the source files to it? I have a large project with multiple targets so that would be something I'd rather not do.

I can sucessfully send pushes to an app (which has been installed/run via Xcode) when the pushes are going through the Apple sandbox server. However I want to test the server is configured correctly to send them through the Apple production server. In the Xcode scheme I tried to change the build configuration to release (and ticked debug executable off) ,however the pushes still only work when sent through the sandbox. Is there a way of installing/running the app using Xcode such that its compatible with the push production environment? Does the APS Environment entitlement come into play here? this only ever says development. (The app is on behalf of a 3rd party company, they've added me to their apple developer account but with limited powers, I can't upload to Testflight nor make an ad-hoc release with with to test with)

I'm attempting make to make a distribution build of an app. In the Xcode target the supported destinations has only iPhone and build active architectures only is set to NO. I created an archive, then selected Distribute App/ Debugging, but then got this error: Provisioning profile "iOS Team Provisioning Profile: com.abc.def" doesn't include the currently selected device "DT-iPad-XXXX" (identifier YYYY-YYYYYY). I've no idea what this device is, it's nothing to do with me, somebody must have added it to the provisioning profile. But that should be beside the point shouldn't it? Because this device has never ever been connected to my Mac/Xcode and so can't be "the currently selected device". So I tried again. I changed build active architectures to YES and connected an iPhone to the Mac/Xcode and created an archive again. But it was the exact same error. What's going on, why is Xcode saying this iPad is the currently selected device when attempting to make a distribution?

Hi all, I got the email saying my certificate(s) will be expiring in 30 days. I can view my certificates (distribution, distribution managed, and 2x developments) on my account page. The distribution expires in 30 days (4/20/2023) The distribution managed expires in 6 months Development #1 (under my name) expires in 30 days (4/20/2023) Development #2 (also under my name) expires in 2 months (5/26/2023) However, I don't see any way to renew them. I have read other posts that talk about 'edit' or 'generate' buttons, but I don't see that and I presume those posts are just out of date. When I look in my xcode project, I see that I am using 'automatically manage singing'. Xcode also shows that a provisioning profile is expiring in 2 months. I presume that is something different? It has the same expiration date as my development #2 certificate (5/26/2023). It's also unclear what is going to happen when these certificates expire. I read that devices running builds with the expired distribution cert will stop working. Is that just for internal builds downloaded from something like Test Flight? Will live builds, downloaded by actual players from the AppStore, stop working if I don't push a release with a new cert in the next month? I am the one that set this all up and 'maintains' it, but I don't engage with it often enough to remember the bits and bobs. My apologies for all the newbie questions. Thank you for your assistance