Search results for

xcode github

93,996 results found

Post

Replies

Boosts

Views

Activity

Reply to How to properly use PermissionKit to ask permission
the communication permission work for me with xcode and ios 26.2 public release it needs sync contacts and enable communication limit on the child device. Thanks. I also got mine working. Not sure if it was the upgrade to 26.2 actual release from 26.2 RC or changing the Communications limits. I still don't know how to fake my location to texas to test significant app update Two thoughts: Use a VPN GPX file in your project (for testing) - https://techcommunity.microsoft.com/discussions/windows10space/can-i-spoof-gps-location-on-iphone--no-jailbreak-needed/4427403/replies/4427409
2d
Facing 2 issues: Issue uploading for external testers, and issue in downloading the app for internal testers. Although the app work perfeclty when i build it directly locally to my phone.
Although the application functions correctly when deployed locally to a physical iPhone using Flutter (direct debug/development build via Xcode), we are encountering the following issues only within App Store Connect / TestFlight: 1- Internal Testing Issue: After completing all required steps in App Store Connect and adding internal testers, testers are unable to install the app. TestFlight displays the error: “Could not install app. The requested app is not available or doesn’t exist.” 2- External Testing Issue: When attempting to add a processed build to an External Testing group (Public Link), App Store Connect returns the following message: “There was an error processing your request. Please try again later.” The build has successfully uploaded and processed, and is marked as Ready to Submit in TestFlight. These issues do not occur during direct device deployment and appear to be isolated to TestFlight / App Store Connect. We would appreciate guidance on how to solve this issue which is preventin
1
0
58
2d
Reply to Xcode Cloud fail in task Export archive
I'm seeing a similar issue with just Xcode cloud builds. Feedback here: FB21343022 For us, changing Xcode version on Xcode cloud doesn't resolve. To repeat details from the feedback for those at home: We see the following error on repeated Xcode cloud builds when trying to archive for “iOS App Store”. Export archive for development distribution Command exited with non-zero exit-code: 70 The “Archive Build” step is failing with what looks like some internal error. Xcode Version: 26.1.1 (17B100) macOS Version : macOS Tahoe 26.1 (25B78) Attached are the logs, within the relevant part I see this repeated (truncated here for reference and brevity) 2025-12-14T23:42:24.246116551Z error: exportArchive There is a problem with the request entity 2025-12-14T23:42:24.246119266Z 2025-12-14T23:42:24.246121303Z error: exportArchive No signing certificate iOS Development found 2025-12-14T23:42:24.246124727Z 2025-12-14T23:42:24.246126906Z error: exportArchive There is a problem wit
2d
Reply to Xcode Cloud fails while exporting archive
Seeing this as well. I don't see those exact errors in the log. In our case it repeatedly mentions: 2025-12-14T23:42:24.246116551Z error: exportArchive There is a problem with the request entity 2025-12-14T23:42:24.246119266Z 2025-12-14T23:42:24.246121303Z error: exportArchive No signing certificate iOS Development found 2025-12-14T23:42:24.246124727Z 2025-12-14T23:42:24.246126906Z error: exportArchive There is a problem with the request entity 2025-12-14T23:42:24.246129486Z 2025-12-14T23:42:24.246131437Z error: exportArchive No signing certificate iOS Development found Which is odd as we use cloud managed signing. I do see a Development certificate created by Xcode cloud. The app id that references is setup for iOS. I don't see an Xcode cloud generated Provisioning profile in the development portal, but I can't recall if they show up there. FB21343022
2d
Xcode Cloud fails while exporting archive
Hi, Since Xcode 26.2 beta 1, till now (I thought RC or actual release will solve this issue) I have problems exporting archive to appstore via Xcode Cloud (locally everything works and using Xcode 26.2 I was able to submit app to AppStore). Build is archived successfully but during export I get an error Exporting for App Store Distribution failed. Please download the logs artifact for more information. In xcodebuild-export-archive.log I see multiple attempts & errors like this 2025-12-13T08:29:34.040644840Z 2025-12-13 00:29:33.900 xcodebuild[10889:58988] DVTServices: Sending request 9A4173F4-CD87-4A76-95FC-501B4D11EF22 to for session DVTFoundation.DVTServicesSessionProxy. 2025-12-13T08:29:34.040647258Z Method: POST 2025-12-13T08:29:34.040648780Z 2025-12-13T08:29:34.040650230Z Headers: 2025-12-13T08:29:34.040651730Z { 2025-12-13T08:29:34.040653539Z Accept = application/vnd.api+json; 2025-12-13T08:29:34.040655403Z Accept-Encoding = gzip, deflate; 2025-12-13T08:29:34.040673847Z Co
1
0
182
2d
Xcode Simulator causes Mac audio crackling and distortion
[Submitted as FB20950954] Xcode Simulator causes crackling and distortion in audio playback across all apps (Apple Podcasts, Music, third-party). REPRO STEPS Open any audio app and start playback Note the audio quality Launch Xcode Simulator After a few seconds, note audio quality again Quit Xcode Simulator Audio returns to normal CURRENT Audio has crackling and distortion while Simulator is running. EXPECTED Clean audio playback regardless of whether Simulator is running. SYSTEM INFO macOS 26.1 (25B78) Xcode 26.1 (17B55) Simulator 26.0 (1058)
2
0
138
3d
Reply to DeclaredAgeRange framework new cases and properties cause runtime crash with missing symbol
@DTS Engineer Tested with Xcode 26.2 downloaded from the App Store, against iPhone 17 Pro running 26.1 (23B85) Xcode Version 26.2 (17C52) So this property wasn't tested. I haven't touched PermissionKit yet so I wasn't actively testing this, however my wrapper library code still fails for this property too and causes a runtime crash due to symbol not found. AgeRangeService.ParentalControls.significantAppChangeApprovalRequired 55C0A89C-7970-4C69-B5D3-1E6873C6EF2B-diagnostic.json Here is some offending code, assumes iOS 26 minimum target: extension ParentalControls { public init(activeParentalControls: AgeRangeService.ParentalControls) { var value: Int = 0 if activeParentalControls.contains(.communicationLimits) { value |= ParentalControls.communicationLimits.rawValue } if activeParentalControls.contains(.significantAppChangeApprovalRequired) { value |= ParentalControls.significantAppChangeApprovalRequired.rawValue } self.rawValue = value } }
3d
DeclaredAgeRange framework new cases and properties cause runtime crash with missing symbol
I'm making a wrapper library to abstract away some of the 'missing platform support' of DeclaredAgeRange until hopefully it expands to additional platforms. When I'm trying to fully enumerate all of the cases of AgeRangeDeclaration, which they all state available starting 26.0 (mysteriously added in Xcode 26.2 beta), the app crashes due to a missing symbol at launch time. This happens both for Xcode 26.1, 26.2 beta 2, and matching Xcode Cloud builds. So I've isolated it beyond doesn't work on my machine. I just made a handful of crashes and attached a sysdiagnose to a fresh feedback. FB21121092 - DeclaredAgeRange: Eligibility property and new declaration cases unavailable on iOS 26.1 device contradicting documentation - causes runtime symbol not found crash If anyone is curious what these crashes look like I've attached the DiagnosticPayload.jsonRepresentation() generated from one of my favorite frameworks, MetricKit. Very clearly articulated in the diagnostic metadata you can see t
4
0
664
3d
Reply to SDK for Swift Student Challenge 2026 submissions
👋Hi @DTS Engineer I remember that the form submitted last year needed to be filled in with Xcode or Playground test, and it seems that it was also mentioned: • If you use Xcode, the judges may use Simulator to run. • If you use Playground, it's a real machine. But my work this time will encounter two limitations: It will use the framework/API only available in iOS 26 (so if it is a Playground environment, it may not run) It will also use some content that must be real to run (such as ARKit), which means that Xcode Simulator is not good. So I would like to ask: Does this year's review allow you to compile and connect the iPad to the real machine? Or did I misremember last year's regulations? If the judge's environment is fixed (for example, only Playground or only Simulator), how should I adjust the submission method or implement the scheme? Looking forward to your reply, thank you. ~ Jiaxu Li
3d
Importing files to Files.app in iOS 26 Simulator
In previous versions of the simulator, it was possible to import files into the Files app by dragging them from the Finder into the Simulator. It appears that in the iOS 26 Simulator, this opens the file in Safari. I've only tried it with .json files so far. The documentation at https://developer.apple.com/documentation/xcode/sharing-data-with-simulator says that the original behaviour should happen: To add files to Simulator, select one or more files in Finder on your Mac, then click the Share button. Select Simulator from the share destination list. Choose the simulated device from the drop-down list. Simulator opens the Files app, and lets you select where to save the files. I'd love to learn if this is intentional behaviour, and if so, what workarounds there might be. I use this pattern quite a lot, as I have a HealthKit app, and I've built a system that allows me to export workouts as JSON files from a real device, that I can then import into a simulator for testing. Edit: I found a workaround.
7
0
330
3d
Tapping on ShareLink crashes the app
Overview Tapping on ShareLink crashes the app when ShareLink is added in the toolbar with the placement of secondaryAction Feedback FB21337385 Note: Apple engineers please priorities this is a blocker and affects production apps and prevents us from going live. Environment Xcode: 26.2 (17C52) iOS: 26.2 iPadOS: 26.2 Reproduce Able to reproduce 100% both on Simulator and Device Isolation of the crash The crash happens only when the ShareLink is used with the placement .secondaryAction The crash doesn't 'happen when the ShareLink is used with the placement .primaryAction Code import SwiftUI struct ContentView: View { var body: some View { NavigationStack { Text(Hello, world!) .toolbar { ToolbarItem(placement: .primaryAction) { Button(Dummy) { print(dummy) } } // Tapping on share button will cause it to crash // Crash only happens when the ShareLink is used with placement .secondaryAction // It doesn't crash when placement is primaryAction ToolbarItem(placement: .secondaryAction) { ShareLink(item: Some s
1
0
85
3d