Search results for

“xcode github”

95,388 results found

Post

Replies

Boosts

Views

Activity

Section(isExpanded:) in sidebar List, inconsistent row animation on collapse/expand
When using Section(_:isExpanded:) inside a List with .listStyle(.sidebar) in a NavigationSplitView, some rows don't animate with the others during collapse and expand. Specific rows (often in the middle of the section) snap in/out instantly while the rest animate smoothly. I've reproduced this with both static views and ForEach. Minimal reproduction: struct SidebarView: View { @State private var sectionExpanded = true @State private var selection: Int? var body: some View { NavigationSplitView { List(selection: $selection) { Section(Section, isExpanded: $sectionExpanded) { ForEach(1...3, id: .self) { index in NavigationLink(value: index) { Label(Item (index), systemImage: (index).circle) } } } } .listStyle(.sidebar) .navigationTitle(Sidebar) } detail: { if let selection { Text(Selected item (selection)) } else { Text(Select an item) } } } } Environment: macOS 26.3, Xcode 26.3, SwiftUI Steps to reproduce: Run the above code in a macOS app Click the section disclosure chevron to collapse Observe that s
0
0
19
3h
Urgent: Bundle ID Case-Sensitivity Mismatch for Approved Family Controls Entitlement
Hello, I have a critical issue regarding the Family Controls (Distribution) entitlement. My app FocusPact was approved for the entitlement, but there is a technical mismatch in the Bundle IDs that prevents distribution via TestFlight. [Current Situation] Parent App ID: com.hayashikento.FocusPact (Approved / Capitalized) Approved Extension ID: com.hayashikento.focuspact.ShieldConfigurationExtension (Approved / Lowercase) [The Issue] Due to the case-sensitivity difference (FocusPact vs focuspact), Xcode throws a Bundle identifier prefix mismatch error. Since the parent app identifier is already established as capitalized, I cannot change it to lowercase without breaking the existing configuration. [Request] I have submitted a new entitlement request with the corrected capitalized Bundle ID: Corrected Extension ID: com.hayashikento.FocusPact.ShieldConfigurationExtension Could a DTS engineer please help me synchronize the approved status to this capitalized ID? This is purely a technical correction of an
0
0
44
9h
Urgent: Bundle ID Case-Sensitivity Mismatch for Approved Family Controls Entitlement
Hello, I have a critical issue regarding the Family Controls (Distribution) entitlement. My app FocusPact was approved for the entitlement, but there is a technical mismatch in the Bundle IDs that prevents distribution via TestFlight. [Current Situation] Parent App ID: com.hayashikento.FocusPact (Approved / Capitalized) Approved Extension ID: com.hayashikento.focuspact.ShieldConfigurationExtension (Approved / Lowercase) [The Issue] Due to the case-sensitivity difference (FocusPact vs focuspact), Xcode throws a Bundle identifier prefix mismatch error. Since the parent app identifier is already established as capitalized, I cannot change it to lowercase without breaking the existing configuration. [Request] I have submitted a new entitlement request with the corrected capitalized Bundle ID: Corrected Extension ID: com.hayashikento.FocusPact.ShieldConfigurationExtension Could a DTS engineer please help me synchronize the approved status to this capitalized ID? This is purely a technical correction of an
0
0
29
10h
Reply to Family Controls Entitlement NOT applied to App Extensions (and Support Form is broken)
[Reply to DTS Engineer] Thank you for looking into this. I have identified the root cause of the issue: it is a Bundle ID case-sensitivity mismatch. My parent app was approved as com.hayashikento.FocusPact (Capitalized), but I accidentally requested the Configuration Extension with a lowercase ID (com.hayashikento.focuspact...). This causes a Prefix Mismatch error in Xcode, preventing me from archiving the app. To fix this, I have just submitted a new entitlement request with the corrected capitalized ID: com.hayashikento.FocusPact.ShieldConfigurationExtension Since the core functionality was already approved under the lowercase ID, could you please expedite the approval for this capitalized version? This technical correction is the only thing blocking my TestFlight distribution. Thank you for your support!
10h
Face ID (LAContext) authenticate() causes SIGABRT crash immediately on iOS (Flutter local_auth)
I am developing a Flutter iOS application and encountering a crash when using biometric authentication (Face ID) via the local_auth plugin. ■ Environment Flutter: 3.x local_auth: 2.2.0 (also tested with 2.1.6) iOS: real device (Face ID is working normally for device unlock) Firebase Authentication (email/password) Xcode build ■ Issue When calling biometric authentication, the app crashes immediately. Code: final didAuthenticate = await auth.authenticate( localizedReason: 'Authenticate to login', options: const AuthenticationOptions( biometricOnly: false, useErrorDialogs: false, ), ); ■ Error Thread 1: signal SIGABRT Crash occurs in libsystem_kernel.dylib (__pthread_kill) Happens immediately when authenticate() is called No exception is caught in Dart (native crash) ■ Verified NSFaceIDUsageDescription is correctly included in Info.plist Confirmed it exists in the built Runner.app Info.plist localizedReason is non-empty and in English Flutter clean / pod install executed App reinstall
0
0
68
19h
Xcode 26.3 Simulator renders SwiftUI app only inside a rounded rectangle instead of full screen
Hi everyone, I’m seeing a strange rendering issue in Xcode 26.3 that seems to affect only the iOS Simulator. Environment: Xcode 26.3 SwiftUI app Reproduces in Simulator only Reproduces across multiple simulator device models My code is just a minimal example Expected behavior: The view should fill the entire screen. Actual behavior: The app content is rendered only inside a centered rounded rectangle/card-like area, with black space around it, as if the app canvas is being clipped incorrectly. Minimal reproduction: import SwiftUI @main struct LayoutShowcaseApp: App { var body: some Scene { WindowGroup { Color.green.ignoresSafeArea() } } } I also tried wrapping it in a ZStack and using: .frame(maxWidth: .infinity, maxHeight: .infinity) .background(...) .ignoresSafeArea() but the result is the same. What I already tried: Clean Build Folder Switching simulator device models Resetting simulator content/settings Rebuilding from a fresh minimal SwiftUI project Since this happens with such a minima
Topic: UI Frameworks SubTopic: SwiftUI
0
0
153
20h
Attached macro loses generated source file
I’m seeing what looks like a compiler / macro-expansion / build-pipeline issue. Environment: Xcode 26.4 RC (17E192, latest); I believe it is also reproducible on earlier versions. github source code I reduced this to a very small macOS/iOS app plus a local macro package. The app logic is trivial, but app exits immediately on launch with code 138 Important observations: If I inline everything into a single file, the problem disappears. I also see an error like this during investigation: The file path does not exist on the file system: /var/folders/.../swift-generated-sources/@__swiftmacro_18MacroFeedbackRepro20MountActivationState17PreservedRawValuefMm_.swift That makes me suspect this is not an application logic issue, but something in macro expansion / generated source handling / compiler pipeline.
0
0
191
1d
iOS 26: Toolbar button background flashes black during NavigationStack transitions (dark mode)
I’m seeing a visual glitch with toolbar buttons when building with Xcode 26 for iOS 26. During transitions (both pushing in a NavigationStack and presenting a .sheet with its own NavigationStack), the toolbar button briefly flashes the wrong background colour (black in dark mode, white in light mode) before animating to the correct Liquid Glass appearance. This happens even in a minimal example and only seems to affect system toolbar buttons. A custom view with .glassEffect() doesn’t have the issue. I’ve tried: .tint(...), UINavigationBarAppearance/UIToolbarAppearance, and setting backgrounds on hosting/nav/window but none of those made any difference. Here’s a minimal reproducible example: import SwiftUI struct ContentView: View { @State private var showingSheet = false var body: some View { NavigationStack { List { NavigationLink(Push (same stack — morphs)) { DetailView() } Button(Sheet (separate stack — flashes)) { showingSheet = true } } .navigationTitle(Root) .scrollContentBackground(.hidden) .b
0
0
190
1d
Xcode 26.4 rc
Since 26.4 beta 3 I've been having errors after a few hours of using Claude Agent. I get an error stating that I am not authed. If I go into Xcode settings, it still shows I am signed into Claude Agent. I have click sign out and then go through the whole auth process again to start using the agent again. This is on two separate computers. Is there anything I can do to stop this behaviour and stay logged in for longer? It worked fine in 26.3.
1
0
135
1d
Xcode 26.4: Regressions in Intelligence features
Just installed the new Xcode 26.4 RC build (17E192) after happily using 26.3 for a few months. I'm noticing some immediate regressions in the Intelligence features: Frequent losing of OAuth token (Claude Agent). This had previously been fixed and now is back. Agent Thinking is constrained to thought bubble windows, which are (a) too small to read, (b) not scrollable when thinking goes beyond a few paragraphs. Yes they are tappable when thinking is finished, but this doesn't help. Due to (2), in deep thinking, it's impossible to follow progress beyond the visible window, so impossible to know if the agent is going off the rails. I'm noticing just more general slowness to complete tasks. Not just complete them -- it seems like it takes longer to START tasks, which is really weird. It sits there thinking for longer. Same project, same model as before. Every time you tap New Chat it presents both Claude and Codex choices, even if you're only signed into one. This turned a simple single tap into now a req
2
0
129
1d
Reply to Apple watch Xcode pairing & connection issues
After 7 hours, successfully managed to get my first deployment on the watch. Definitely not something you expect from apple, in fact I cussed them out the whole way through. But here's what I did Mostly followed entouss's guide and most advice is reiterated from him + some of my experiences Before you do anything, make sure Apple Watch is fully charged (this WILL take a long time) It has a passcode You might get the bright idea to remove the passcode and put it on charger to prevent lock. Keep it on. Pre-pair Make sure you're on a 2.4 ghz network (mobile hotspot or create guest network on router) Connect all devices to that network Shutdown all devices and start them up 1 by 1 to start from a clean slate Get it to show up in Xcode devices If your apple watch is already in the xcode device list, DO NOT unpair it as it may not show back up again without large hassle WATCH for trust this device messages on your apple watch. If you accedentally press no, or press the crown while the dialog is on
1d
Reply to PencilKit PKCanvasView flicker
Thank you for the sample project and the video — both were very helpful. We were able to reproduce the flickering on iPad with Apple Pencil using your sample project. We tested several potential app-level workarounds (deferring contentInset updates, guarding against layout recalculation during active drawing, consolidating CATransaction blocks) but none of them resolved the issue. Based on our investigation, the flicker appears to be occurring within PKCanvasView's internal tile rendering when drawing at non-1x zoom scales, rather than being caused by anything in your app code. Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. I'll check the status next time I do a sweep of forums posts where I've suggested bug reports and post any information about changes I am able to share to
1d
FIFinderSync Extension fails to load on FIFinderSync Extension fails to load on macOS 26.3.1 (a) (25D771280a)
(! status in pluginkit, FinderSyncExtensionHost process missing) macOS Version: 26.3.1 Beta (25D771280a) Xcode Version: 16.3 (17C529) Steps to reproduce: Create a Finder Sync Extension project Build and install to /Applications Enable in System Settings → Extensions → Finder Extensions Extension shows ! in pluginkit output FinderSyncExtensionHost process never starts Context menu never appears in Finder Expected: Extension loads and context menu appears Actual: Extension marked with ! in pluginkit, no process launched pluginkit output: ! com.github.astronautJack.EasyNewFile.EasyNewFileExtension(1.0)
0
0
12
2d
Section(isExpanded:) in sidebar List, inconsistent row animation on collapse/expand
When using Section(_:isExpanded:) inside a List with .listStyle(.sidebar) in a NavigationSplitView, some rows don't animate with the others during collapse and expand. Specific rows (often in the middle of the section) snap in/out instantly while the rest animate smoothly. I've reproduced this with both static views and ForEach. Minimal reproduction: struct SidebarView: View { @State private var sectionExpanded = true @State private var selection: Int? var body: some View { NavigationSplitView { List(selection: $selection) { Section(Section, isExpanded: $sectionExpanded) { ForEach(1...3, id: .self) { index in NavigationLink(value: index) { Label(Item (index), systemImage: (index).circle) } } } } .listStyle(.sidebar) .navigationTitle(Sidebar) } detail: { if let selection { Text(Selected item (selection)) } else { Text(Select an item) } } } } Environment: macOS 26.3, Xcode 26.3, SwiftUI Steps to reproduce: Run the above code in a macOS app Click the section disclosure chevron to collapse Observe that s
Replies
0
Boosts
0
Views
19
Activity
3h
Urgent: Bundle ID Case-Sensitivity Mismatch for Approved Family Controls Entitlement
Hello, I have a critical issue regarding the Family Controls (Distribution) entitlement. My app FocusPact was approved for the entitlement, but there is a technical mismatch in the Bundle IDs that prevents distribution via TestFlight. [Current Situation] Parent App ID: com.hayashikento.FocusPact (Approved / Capitalized) Approved Extension ID: com.hayashikento.focuspact.ShieldConfigurationExtension (Approved / Lowercase) [The Issue] Due to the case-sensitivity difference (FocusPact vs focuspact), Xcode throws a Bundle identifier prefix mismatch error. Since the parent app identifier is already established as capitalized, I cannot change it to lowercase without breaking the existing configuration. [Request] I have submitted a new entitlement request with the corrected capitalized Bundle ID: Corrected Extension ID: com.hayashikento.FocusPact.ShieldConfigurationExtension Could a DTS engineer please help me synchronize the approved status to this capitalized ID? This is purely a technical correction of an
Replies
0
Boosts
0
Views
44
Activity
9h
Urgent: Bundle ID Case-Sensitivity Mismatch for Approved Family Controls Entitlement
Hello, I have a critical issue regarding the Family Controls (Distribution) entitlement. My app FocusPact was approved for the entitlement, but there is a technical mismatch in the Bundle IDs that prevents distribution via TestFlight. [Current Situation] Parent App ID: com.hayashikento.FocusPact (Approved / Capitalized) Approved Extension ID: com.hayashikento.focuspact.ShieldConfigurationExtension (Approved / Lowercase) [The Issue] Due to the case-sensitivity difference (FocusPact vs focuspact), Xcode throws a Bundle identifier prefix mismatch error. Since the parent app identifier is already established as capitalized, I cannot change it to lowercase without breaking the existing configuration. [Request] I have submitted a new entitlement request with the corrected capitalized Bundle ID: Corrected Extension ID: com.hayashikento.FocusPact.ShieldConfigurationExtension Could a DTS engineer please help me synchronize the approved status to this capitalized ID? This is purely a technical correction of an
Replies
0
Boosts
0
Views
29
Activity
10h
Reply to Family Controls Entitlement NOT applied to App Extensions (and Support Form is broken)
[Reply to DTS Engineer] Thank you for looking into this. I have identified the root cause of the issue: it is a Bundle ID case-sensitivity mismatch. My parent app was approved as com.hayashikento.FocusPact (Capitalized), but I accidentally requested the Configuration Extension with a lowercase ID (com.hayashikento.focuspact...). This causes a Prefix Mismatch error in Xcode, preventing me from archiving the app. To fix this, I have just submitted a new entitlement request with the corrected capitalized ID: com.hayashikento.FocusPact.ShieldConfigurationExtension Since the core functionality was already approved under the lowercase ID, could you please expedite the approval for this capitalized version? This technical correction is the only thing blocking my TestFlight distribution. Thank you for your support!
Replies
Boosts
Views
Activity
10h
Face ID (LAContext) authenticate() causes SIGABRT crash immediately on iOS (Flutter local_auth)
I am developing a Flutter iOS application and encountering a crash when using biometric authentication (Face ID) via the local_auth plugin. ■ Environment Flutter: 3.x local_auth: 2.2.0 (also tested with 2.1.6) iOS: real device (Face ID is working normally for device unlock) Firebase Authentication (email/password) Xcode build ■ Issue When calling biometric authentication, the app crashes immediately. Code: final didAuthenticate = await auth.authenticate( localizedReason: 'Authenticate to login', options: const AuthenticationOptions( biometricOnly: false, useErrorDialogs: false, ), ); ■ Error Thread 1: signal SIGABRT Crash occurs in libsystem_kernel.dylib (__pthread_kill) Happens immediately when authenticate() is called No exception is caught in Dart (native crash) ■ Verified NSFaceIDUsageDescription is correctly included in Info.plist Confirmed it exists in the built Runner.app Info.plist localizedReason is non-empty and in English Flutter clean / pod install executed App reinstall
Replies
0
Boosts
0
Views
68
Activity
19h
Xcode 26.3 Simulator renders SwiftUI app only inside a rounded rectangle instead of full screen
Hi everyone, I’m seeing a strange rendering issue in Xcode 26.3 that seems to affect only the iOS Simulator. Environment: Xcode 26.3 SwiftUI app Reproduces in Simulator only Reproduces across multiple simulator device models My code is just a minimal example Expected behavior: The view should fill the entire screen. Actual behavior: The app content is rendered only inside a centered rounded rectangle/card-like area, with black space around it, as if the app canvas is being clipped incorrectly. Minimal reproduction: import SwiftUI @main struct LayoutShowcaseApp: App { var body: some Scene { WindowGroup { Color.green.ignoresSafeArea() } } } I also tried wrapping it in a ZStack and using: .frame(maxWidth: .infinity, maxHeight: .infinity) .background(...) .ignoresSafeArea() but the result is the same. What I already tried: Clean Build Folder Switching simulator device models Resetting simulator content/settings Rebuilding from a fresh minimal SwiftUI project Since this happens with such a minima
Topic: UI Frameworks SubTopic: SwiftUI
Replies
0
Boosts
0
Views
153
Activity
20h
Attached macro loses generated source file
I’m seeing what looks like a compiler / macro-expansion / build-pipeline issue. Environment: Xcode 26.4 RC (17E192, latest); I believe it is also reproducible on earlier versions. github source code I reduced this to a very small macOS/iOS app plus a local macro package. The app logic is trivial, but app exits immediately on launch with code 138 Important observations: If I inline everything into a single file, the problem disappears. I also see an error like this during investigation: The file path does not exist on the file system: /var/folders/.../swift-generated-sources/@__swiftmacro_18MacroFeedbackRepro20MountActivationState17PreservedRawValuefMm_.swift That makes me suspect this is not an application logic issue, but something in macro expansion / generated source handling / compiler pipeline.
Replies
0
Boosts
0
Views
191
Activity
1d
iOS 26: Toolbar button background flashes black during NavigationStack transitions (dark mode)
I’m seeing a visual glitch with toolbar buttons when building with Xcode 26 for iOS 26. During transitions (both pushing in a NavigationStack and presenting a .sheet with its own NavigationStack), the toolbar button briefly flashes the wrong background colour (black in dark mode, white in light mode) before animating to the correct Liquid Glass appearance. This happens even in a minimal example and only seems to affect system toolbar buttons. A custom view with .glassEffect() doesn’t have the issue. I’ve tried: .tint(...), UINavigationBarAppearance/UIToolbarAppearance, and setting backgrounds on hosting/nav/window but none of those made any difference. Here’s a minimal reproducible example: import SwiftUI struct ContentView: View { @State private var showingSheet = false var body: some View { NavigationStack { List { NavigationLink(Push (same stack — morphs)) { DetailView() } Button(Sheet (separate stack — flashes)) { showingSheet = true } } .navigationTitle(Root) .scrollContentBackground(.hidden) .b
Replies
0
Boosts
0
Views
190
Activity
1d
Xcode 26.4 rc
Since 26.4 beta 3 I've been having errors after a few hours of using Claude Agent. I get an error stating that I am not authed. If I go into Xcode settings, it still shows I am signed into Claude Agent. I have click sign out and then go through the whole auth process again to start using the agent again. This is on two separate computers. Is there anything I can do to stop this behaviour and stay logged in for longer? It worked fine in 26.3.
Replies
1
Boosts
0
Views
135
Activity
1d
Xcode 26.4: Regressions in Intelligence features
Just installed the new Xcode 26.4 RC build (17E192) after happily using 26.3 for a few months. I'm noticing some immediate regressions in the Intelligence features: Frequent losing of OAuth token (Claude Agent). This had previously been fixed and now is back. Agent Thinking is constrained to thought bubble windows, which are (a) too small to read, (b) not scrollable when thinking goes beyond a few paragraphs. Yes they are tappable when thinking is finished, but this doesn't help. Due to (2), in deep thinking, it's impossible to follow progress beyond the visible window, so impossible to know if the agent is going off the rails. I'm noticing just more general slowness to complete tasks. Not just complete them -- it seems like it takes longer to START tasks, which is really weird. It sits there thinking for longer. Same project, same model as before. Every time you tap New Chat it presents both Claude and Codex choices, even if you're only signed into one. This turned a simple single tap into now a req
Replies
2
Boosts
0
Views
129
Activity
1d
Reply to Xcode 26 close the project when closing all tabs using cmd + w
Enhancements to Xcode's functionality should be filed through Feedback Assistant so the appropriate teams can consider the request. It would be helpful to detail why you'd like Xcode to behave as you describe and how that would help your development workflows when you file that.
Replies
Boosts
Views
Activity
1d
Reply to Apple watch Xcode pairing & connection issues
After 7 hours, successfully managed to get my first deployment on the watch. Definitely not something you expect from apple, in fact I cussed them out the whole way through. But here's what I did Mostly followed entouss's guide and most advice is reiterated from him + some of my experiences Before you do anything, make sure Apple Watch is fully charged (this WILL take a long time) It has a passcode You might get the bright idea to remove the passcode and put it on charger to prevent lock. Keep it on. Pre-pair Make sure you're on a 2.4 ghz network (mobile hotspot or create guest network on router) Connect all devices to that network Shutdown all devices and start them up 1 by 1 to start from a clean slate Get it to show up in Xcode devices If your apple watch is already in the xcode device list, DO NOT unpair it as it may not show back up again without large hassle WATCH for trust this device messages on your apple watch. If you accedentally press no, or press the crown while the dialog is on
Replies
Boosts
Views
Activity
1d
Reply to PencilKit PKCanvasView flicker
Thank you for the sample project and the video — both were very helpful. We were able to reproduce the flickering on iPad with Apple Pencil using your sample project. We tested several potential app-level workarounds (deferring contentInset updates, guarding against layout recalculation during active drawing, consolidating CATransaction blocks) but none of them resolved the issue. Based on our investigation, the flicker appears to be occurring within PKCanvasView's internal tile rendering when drawing at non-1x zoom scales, rather than being caused by anything in your app code. Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. I'll check the status next time I do a sweep of forums posts where I've suggested bug reports and post any information about changes I am able to share to
Replies
Boosts
Views
Activity
1d
Reply to sandbox purchase completes but app review gets stuck
There are a lot of topics about 'RevenueCat.' I would take a look at all of them if I were you. Actually, I think, I have read a quite similar topic probably a week ago. I do everything with Xcode. So I cannot offer a clue of any kind. I don't even know why people use RevenueCat. I only know the name. I would also find out if RevenueCat has support forums.
Replies
Boosts
Views
Activity
2d
FIFinderSync Extension fails to load on FIFinderSync Extension fails to load on macOS 26.3.1 (a) (25D771280a)
(! status in pluginkit, FinderSyncExtensionHost process missing) macOS Version: 26.3.1 Beta (25D771280a) Xcode Version: 16.3 (17C529) Steps to reproduce: Create a Finder Sync Extension project Build and install to /Applications Enable in System Settings → Extensions → Finder Extensions Extension shows ! in pluginkit output FinderSyncExtensionHost process never starts Context menu never appears in Finder Expected: Extension loads and context menu appears Actual: Extension marked with ! in pluginkit, no process launched pluginkit output: ! com.github.astronautJack.EasyNewFile.EasyNewFileExtension(1.0)
Replies
0
Boosts
0
Views
12
Activity
2d