Post

Replies

Boosts

Views

Activity

Reply to Xcode seems not compatible with the ssh key RSA-SHA2 while trying to git clone from Azure
I'm also running into this issue. Xcode is just ignoring the .ssh/config file where the correct key exchange algorithms to use are listed. Unbelievable that this issue is still not fixed :(. For SPM integration I can only recommend configure to use the user configured git for this, which does respect .ssh/config. You can do this by executing this in a terminal: defaults write com.apple.dt.Xcode IDEPackageSupportUseBuiltinSCM YES I haven't found an equivalent preference to tell Xcode to use user configured git client for everything. For when Apple engineers would be reading this, details can be found https://devblogs.microsoft.com/devops/ssh-rsa-deprecation/
Apr ’25
Reply to Xcode/iOS Simulator running with x86_64 instead of arm64 architecture
Most likely a related issue, we've been trying to get 'Any iOS Simulator Device' destinations to only build for arm64. We want to do this because the libraries we develop and use in iOS apps rely on AVX instructions on x86_64 platforms. Building such libraries on Mac devices is getting increasingly complicated, as you can't buy Intel based Mac's anywhere, which you need to run x86_64 MacOS binaries that utilize AVX instructions. Rosetta doesn't solve anything in our case due to these AVX instructions that it can't translate to arm64. I've created a support ticket for this: FB16398099
Jan ’25
Reply to Swift Cpp/c++ interop: swift functions with c++ enums arguments not available in c++
Using swift enums in C++ isn't an issue, and it indeed does that weird'ish naming for the cases. What bothers me is that the Swift functions that I define that take a C++ enum or enum class just don't get interop at all. If the function is a global function, I get the // Unavailable in C++: Swift global function 'swiftFunctionWithCppEnum(_:)'. comment in the generate header. What's worse is that if the function is member for a Swift class, it just gets ommitted entirely without any indication that it is not compatible. It just doesn't show up at all in the generate Swift header. Upon further reading the C++ interop documentation I came across this: If I understand it correctly, this indicates that it actually should work? But it clearly doesn't.
Topic: Programming Languages SubTopic: Swift Tags:
Mar ’24
Reply to SFSpeechRecognizer.isAvailable returns wrong values
Further experimentation yields the following findings. When the iOS device is set to English (US), both SFSpeechRecognizer.isAvailable and .supportsOnDeviceRecognition return true. If we then set the SFSpeechAudioBufferRecognitionRequest’s requiresOnDeviceRecognition to true, we observe the stated issue where speechrecognition tasks fail with “Siri and Dictation are disabled” errors, while according to the SFSpeechRecognizer, it should work.
Topic: App & System Services SubTopic: Core OS Tags:
Oct ’23
Reply to Touch layout not matching UI layout on iPhone after waking device when .sheet is open
@Apple Any feedback on this? Can we expect a fix on this or do I need to implement a workaround for this in our upcoming release? Btw, this is my current workaround. You can add this to any View you show within the sheet, popover, etc... and when it gets dismissed, it will 'reset' the layout. public func body(content: Content) -> some View { content .onDisappear { let scene = UIApplication.shared.connectedScenes.first as? UIWindowScene if let viewFrame = scene?.windows.first?.rootViewController?.view.frame { scene?.windows.first?.rootViewController?.view.frame = .zero scene?.windows.first?.rootViewController?.view.frame = viewFrame } } } } public extension View { func syncLayoutOnDissappear() -> some View { modifier(SyncLayoutOnDissappear()) } }
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Feb ’23
Reply to Xcode seems not compatible with the ssh key RSA-SHA2 while trying to git clone from Azure
I'm also running into this issue. Xcode is just ignoring the .ssh/config file where the correct key exchange algorithms to use are listed. Unbelievable that this issue is still not fixed :(. For SPM integration I can only recommend configure to use the user configured git for this, which does respect .ssh/config. You can do this by executing this in a terminal: defaults write com.apple.dt.Xcode IDEPackageSupportUseBuiltinSCM YES I haven't found an equivalent preference to tell Xcode to use user configured git client for everything. For when Apple engineers would be reading this, details can be found https://devblogs.microsoft.com/devops/ssh-rsa-deprecation/
Replies
Boosts
Views
Activity
Apr ’25
Reply to Xcode/iOS Simulator running with x86_64 instead of arm64 architecture
Most likely a related issue, we've been trying to get 'Any iOS Simulator Device' destinations to only build for arm64. We want to do this because the libraries we develop and use in iOS apps rely on AVX instructions on x86_64 platforms. Building such libraries on Mac devices is getting increasingly complicated, as you can't buy Intel based Mac's anywhere, which you need to run x86_64 MacOS binaries that utilize AVX instructions. Rosetta doesn't solve anything in our case due to these AVX instructions that it can't translate to arm64. I've created a support ticket for this: FB16398099
Replies
Boosts
Views
Activity
Jan ’25
Reply to Swift Cpp/c++ interop: swift functions with c++ enums arguments not available in c++
Using swift enums in C++ isn't an issue, and it indeed does that weird'ish naming for the cases. What bothers me is that the Swift functions that I define that take a C++ enum or enum class just don't get interop at all. If the function is a global function, I get the // Unavailable in C++: Swift global function 'swiftFunctionWithCppEnum(_:)'. comment in the generate header. What's worse is that if the function is member for a Swift class, it just gets ommitted entirely without any indication that it is not compatible. It just doesn't show up at all in the generate Swift header. Upon further reading the C++ interop documentation I came across this: If I understand it correctly, this indicates that it actually should work? But it clearly doesn't.
Topic: Programming Languages SubTopic: Swift Tags:
Replies
Boosts
Views
Activity
Mar ’24
Reply to BAURLDownload failed on inaccurate fileSize when non-essential
Upon further experimentation I've discovered that you must set fileSize to 0 to make the BAURLDownload function as expected. Setting it to -1, or slightly different filesize will yield a download failure. So setting both fileSize to 0 and essential to false is required to download assets that you don't have a proper filesize for.
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Nov ’23
Reply to SFSpeechRecognizer.isAvailable returns wrong values
Further experimentation yields the following findings. When the iOS device is set to English (US), both SFSpeechRecognizer.isAvailable and .supportsOnDeviceRecognition return true. If we then set the SFSpeechAudioBufferRecognitionRequest’s requiresOnDeviceRecognition to true, we observe the stated issue where speechrecognition tasks fail with “Siri and Dictation are disabled” errors, while according to the SFSpeechRecognizer, it should work.
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Oct ’23
Reply to Touch layout not matching UI layout on iPhone after waking device when .sheet is open
I found this in iOS 17's Beta release notes: Fixed: Gestures could be misaligned if an app was backgrounded while a sheet was presented. (99202394). Hopefully this is referring to this particular issue.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Jun ’23
Reply to Xcode 15 linking error
Having the same problem.
Replies
Boosts
Views
Activity
Jun ’23
Reply to Iphone 13 and 14 have unusably inaccurate depth data. iPhone 12 and iPad Pro is fine
Apple responded to my reported Issue in the Feedback Assistant with: 'Investigation complete - Works as currently designed.' with no further explanation given. Highly disappointed about this. I'm just hoping they won't do the same thing in future iPad Pro iterations and it gets fixed in iPhone 15.
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
May ’23
Reply to Blurry Depth Data on iPhone 13
Not entirely sure we are seeing the same problem, but the depth data from iPhone 13 and newer is highly inaccurate as well. I've create a post about it too: https://developer.apple.com/forums/thread/728992
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Apr ’23
Reply to Touch layout not matching UI layout on iPhone after waking device when .sheet is open
This is still broken on iOS 16.4 and XCode 14.3
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Apr ’23
Reply to Touch layout not matching UI layout on iPhone after waking device when .sheet is open
@Apple Any feedback on this? Can we expect a fix on this or do I need to implement a workaround for this in our upcoming release? Btw, this is my current workaround. You can add this to any View you show within the sheet, popover, etc... and when it gets dismissed, it will 'reset' the layout. public func body(content: Content) -> some View { content .onDisappear { let scene = UIApplication.shared.connectedScenes.first as? UIWindowScene if let viewFrame = scene?.windows.first?.rootViewController?.view.frame { scene?.windows.first?.rootViewController?.view.frame = .zero scene?.windows.first?.rootViewController?.view.frame = viewFrame } } } } public extension View { func syncLayoutOnDissappear() -> some View { modifier(SyncLayoutOnDissappear()) } }
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Feb ’23
Reply to Touch layout not matching UI layout on iPhone after waking device when .sheet is open
Ok, made a copy-paste error. first line is missing: public struct SyncLayoutOnDissappear: ViewModifier {
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Feb ’23
Reply to Touch layout not matching UI layout on iPhone after waking device when .sheet is open
I already created a issue in the feedback assistent at the same time as posting this on the dev forums -> FB11983439
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Feb ’23
Reply to SwiftUI Previews in Xcode 14 failed to run with SettingsError: noExecutablePath(IDESwiftPackageStaticLibraryProductBuildable)
Yup, for me the problem still persist as well in 14.1 beta 3. HumanReadableSwiftError SettingsError: noExecutablePath(<IDESwiftPackageStaticLibraryProductBuildable:ObjectIdentifier(0x0000600014106940):'AppCenterAnalytics'>) Updated FB11515571 with new error report.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Sep ’22
Reply to SwiftUI Previews in Xcode 14 failed to run with SettingsError: noExecutablePath(IDESwiftPackageStaticLibraryProductBuildable)
Not sure @Dasoga mistyped, but I can confirm that the issue is NOT fixed entirely in 14.1 beta 1. Reported new issue: FB11515571
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Sep ’22