Search results for

xcode github

94,047 results found

Post

Replies

Boosts

Views

Activity

Xcode can't view code generated by Swift Package Plugins
When using a Swift Build Plugin, the generated code definitions are available through autocomplete, but it is currently not possible to view them directly in Xcode using Option+click. An example of such a plugin is swift-openapi-generator. According to information from Meet Swift Package plugins from WWDC22 the generated code is stored with other build artifacts. It would be immensely helpful if there was support for viewing these intermediate files in read-only mode using Option+click. Currently, I have to resort to opening these files through Finder, or opening the project in VS Code where viewing the generated files using Cmd+click works without a problem. Am I missing something? If not, it seems like a big oversight that this is not supported to the same extent in Apple's own tools.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
1
0
57
4w
Xcode Cloud Build timeouted by cloning our Bitbucket-Server Repository
We want to replace our CI/CD pipelines in Azure DevOps with Xcode Cloud and are currently facing a critical hurdle. For some time now, we’ve observed that the PoC pipelines in Xcode Cloud are having major issues cloning our repositories stored on our Bitbucket Server. More and more pipeline runs are timing out because Xcode Cloud cannot receive the data. Today I spoke with our network team to check whether we might have an issue on our side affecting access to the repository, but we couldn’t find any problems. Cloning the repository to an external machine only takes 30 seconds, so the host’s bandwidth doesn’t seem to be the problem. However, our network specialists did discover one message: Significance: Request abnormal event: high total time Connection abnormal event: client has a slow receive rate If this is the bottleneck in the system, we may ultimately have to stay with Azure DevOps and Fastlane in order to continue providing our product teams with reliable builds. I look forw
Topic: Developer Tools & Services SubTopic: Xcode Cloud Tags:
3
0
91
4w
[Xcode 26 beta 4] Cannot receive device token from APNS using iOS 26 simulator
Since upgrading to Xcode 26 beta 4 and using the iOS 26 simulator for testing our app, we've stopped being able to receive device tokens for the simulator from the development APNS environment. The APNS environment is able to return meta device information (e.g. model, type, manufacturer) but there are no device tokens present. When running the same app using the iOS 18.5 simulator, we are able to register the device with the same APNS environment and receive a valid device token.
Topic: App & System Services SubTopic: Notifications Tags:
14
0
2.4k
4w
Reply to SwiftUI Slider onEditingChanged is unreliable on iOS 26
Hi everyone, I wanted to share an additional finding that might help narrow down the issue. In my case, the unexpected behavior of onEditingChanged appears only when the Slider uses the step parameter. Here is a minimal reproducible example: @State private var speed = 50.0 @State private var isEditing = false { didSet { print(isEditing:(isEditing)) } } var body: some View { VStack { Slider( value: $speed, in: 0...100, step: 10, onEditingChanged: { editing in isEditing = editing } ) Text((speed)) .foregroundColor(isEditing ? .red : .blue) } } ✔️ Without the step parameter (works as expected): Start dragging: isEditing: true End dragging: isEditing: false ❌ With the step parameter: Start dragging: (no logs at all) End dragging: isEditing:false isEditing:true So the final editing state becomes true again when the drag gesture ends — matching what others here have observed. Additional details: Issue reproduces on iOS 26.1 Worked correctly on iOS 26.0.1 Tested with Xcode Version 26.1.1 (17B100) It seems t
Topic: UI Frameworks SubTopic: SwiftUI Tags:
4w
PaperKit: Adding Images is not functional
When utilizing Paperkit in its simplest form, PaperMarkupViewController does not show the option to add images. Furthermore, trying to add images directly to the PaperMarkup's insertNewImage() function does not display anything. It seems like image functionality is entirely broken on Xcode 26. This can be seen through the following example done by a fellow member here on the forums: https://gist.github.com/clarkezone/68eb3ee13b5607782ceb2e20cece4ab3
Topic: UI Frameworks SubTopic: SwiftUI Tags:
3
0
175
4w
Significant Disparity in Event Frequency Between CLCircularRegion (Legacy) and CLMonitor (iOS 17+) Geofencing APIs
1. The Inquiry Hello, I have been implementing a background geofencing feature and, during testing, I found a significant numerical difference in event callback frequency between the older CLCircularRegion API and the newer CLMonitor API (CLMonitor.CircularGeographicCondition), introduced in iOS 17. My testing was strictly conducted using the Always Allow location permission (requestAlwaysAuthorization()). I used both APIs in parallel under identical geofencing conditions and within the same implementation environment. Since a clear difference persists in the data, I suspect this may stem from structural differences in the internal mechanisms of the two APIs rather than an implementation error on my part. 2. Environment and Implementation Details (Proof of Integrity) I have ensured that my implementation adheres to Apple's guidelines and uses modern Swift concurrency features. A. Development Environment and Permissions iOS Version: iOS 18.x and later Xcode Version: Version 17A400 (Version 26.0.1) Loc
Topic: App & System Services SubTopic: Maps & Location Tags:
3
0
232
4w
Weird crash: missing symbol Swift.AsyncIteratorProtocol.next()
I got several reports about our TestFlight app crashing unconditionally on 2 devices (iOS 18.1 and iOS 18.3.1) on app start with the following reason: Termination Reason: DYLD 4 Symbol missing Symbol not found: _$sScIsE4next7ElementQzSgyYa7FailureQzYKF (terminated at launch; ignore backtrace) The symbol in question demangles to (extension in Swift):Swift.AsyncIteratorProtocol.next() async throws(A.Failure) -> A.Element? Our deploy target is iOS 18.0, this symbol was introduced in Swift 6.0, we're using latest Xcode 16 now - everything should be working, but for some reason aren't. Since this symbol is quite rarely used directly, I was able to pinpoint the exact place in code related to it. Few days ago I added the following code to our app library (details omitted): public struct AsyncRecoveringStream: AsyncSequence { ... public struct AsyncIterator: AsyncIteratorProtocol { ... public mutating func next(isolation actor: isolated (any Actor)? = #isolation) async throws(Failure) -> Element? { ...
Topic: App & System Services SubTopic: Core OS Tags:
3
0
220
4w
Reply to Bonjour for discovering a specific device's ip
Hi there, I struggle to get the mDNS name using _services._dns-sd._udp on iOS 26.1. I tried two methods: NetServiceBrowser always gives me [NSNetServicesErrorCode: -72008 (missingRequiredConfigurationError), NSNetServicesErrorDomain: 10] DNSServiceBrowser fails with NoAuth I also tried NWBrowser, but learned that it does not work with _services._dns-sd._udp. My Info.plist: NSBonjourServices _services._dns-sd._udp NSLocalNetworkUsageDescription mDNS_Browser needs to have network access to search for Multicast services I tested it with a physical device, none of the above methods work. The strange thing is that NSBonjourServices works in the simulator the first time I use it but then fails, DNSServiceBrowser does not work. But with macOS 17 DNSServiceBrowser works but NSBonjourServices does not. This is so random, I am out of ideas. Here is an example project that can be used to test both methods: GitHub @DTS Engineer :)
Topic: App & System Services SubTopic: Networking Tags:
4w
Static library produced by Xcode 26 causes link error on Xcode 16
When a static library is built with Xcode 26 (with deployment target set to iOS 13) and then linked into an app project compiled with Xcode 16, the build process fails with the following linker error: Undefined symbols for architecture arm64: _swift_coroFrameAlloc This occurs even though both the static library and the app project have their deployment targets set to iOS 13.0. The static library works on Xcode 26, but fails to link on Xcode 16. This issue shows up with certain Swift syntax. For example, in my case, using a property getter and setter caused the compiler to emit a reference to _swift_coroFrameAlloc, which in turn triggered the issue. This issue prevents us from distributing pre-built static libraries compiled with Xcode 26 to teammates who are still using Xcode 16. I’ve filed feedback for this issue (FB21130604). Is there any way to work around it? For example, by adding specific Build Settings or something similar? A demo project is availab
Topic: Developer Tools & Services SubTopic: General Tags:
2
0
262
4w