Search results for

xcode github

92,023 results found

Post

Replies

Boosts

Views

Activity

Redefinition of module 'AppleTextureEncoder'
I have been working on a project before this year's new OSX and Xcode update and I was able to build the project with little trouble. But since updating to any of the beta software, including the latest version of Tahoe 26.0 and Xcode26-beta4 I have not been able to build this same project. I have tried reseting package cache and updating to the latest package versions. As well I have deleted the derived data and cleaning the build folder. The following error output is one of 55 errors I am getting. It seems like the modules for the XRSimulator are redefinitions from those for MacOSX. I don't know how to limit or redirect the definition of the modules to just those for the XRSimulator (this is a VisionOS project). I also tried all of this on different betas of Xcode with all the same result. This bug is causing a problem with the 16.4 version of Xcode as well. I would really really appreciate anybody's help on this. in file included from /Applications/Xcode.app/Contents/Developer/Pl
2
0
107
3w
Reply to Redefinition of module 'AppleTextureEncoder'
I tried a few different things on top of what I mentioned before. I went through the build settings and removed any reference to macosx or macos26 but that didn't really do much. I also tried the classic boot down and back up but that also has not worked. As a last ditch effort I also deleted the macosx sdk via terminal but I now end up with a different failure stating that this is a necessary dependency for Xcode. Im at my wits end sadly. I would appreciate a much more stable platform to build AR apps but this is pretty ridiculous.
3w
ViewModel Scene's not rendering properly
Hi All, I'm new to IOS development/Xcode and would appreciate any/all advice/guidance on this unexplainable issue. Please excuse my potential usage of wrong terms. I have a project that was handed to me in a near completed state and there is a UI bug in the program that I am trying to fix. It is opening multiple instances of a View Controller Scene in the wrong dimensions, causing instanced layers that act independently of each other rather than a simple page re-routing like regular front end development. Upon investigating the codebase I have noticed the following potential source: The storyboard was originally modeled after an IPhone 16 Pro Max, however the main device we will be creating the app for is an iPad 11 mini. Upon changing the simulated device, the view models for most of my XXXViewControllerScenes are not rendering the correct size. Here are some examples: Image1 ) When selecting the RootNavController (scene 1) > all storyboard scenes render the correct size (at least thats what it v
1
0
102
3w
Reply to Xcode 26 beta 3: StoreKit Testing broken
I just got this when running from Xcode 16.3, real device iOS 18.6.1 [9c592259_SK1] Could not parse product: missingValue(for: [StoreKit.ProductResponse.Key.price], expected: StoreKit.BackingValue) [9c592259_SK1] Could not parse product: missingValue(for: [StoreKit.ProductResponse.Key.price], expected: StoreKit.BackingValue) [9c592259_SK1] Could not parse product: missingValue(for: [StoreKit.ProductResponse.Key.price], expected: StoreKit.BackingValue) [9c592259_SK1] Could not parse product: missingValue(for: [StoreKit.ProductResponse.Key.price], expected: StoreKit.BackingValue) [9c592259_SK1] Could not parse product: missingValue(for: [StoreKit.ProductResponse.Key.price], expected: StoreKit.BackingValue) [9c592259_SK1] Could not parse product: missingValue(for: [StoreKit.ProductResponse.Key.price], expected: StoreKit.BackingValue) [9c592259_SK1] Could not parse product: missingValue(for: [StoreKit.ProductResponse.Key.price], expected: StoreKit.BackingValue) [9c592259_SK1] Could not parse product: mis
Topic: App & System Services SubTopic: StoreKit Tags:
3w
Xcode 26 beta 3: StoreKit Testing broken
It seems that beta 3 broke StoreKit Testing when running against an iOS 26 simulator device. Specifically, when validating product IDs, the debug console displays messages like the following: [492a4cfa_SK1] Could not parse product: missingValue(for: [StoreKit.ProductResponse.Key.price], expected: StoreKit.BackingValue) [492a4cfa_SK1] Could not parse product: missingValue(for: [StoreKit.ProductResponse.Key.price], expected: StoreKit.BackingValue) [492a4cfa_SK1] Could not parse product: missingValue(for: [StoreKit.ProductResponse.Key.price], expected: StoreKit.BackingValue) [492a4cfa_SK1] Could not parse product: missingValue(for: [StoreKit.ProductResponse.Key.price], expected: StoreKit.BackingValue) [492a4cfa_SK1] Could not parse product: missingValue(for: [StoreKit.ProductResponse.Key.price], expected: StoreKit.BackingValue) [492a4cfa_SK1] Could not parse product: missingValue(for: [StoreKit.ProductResponse.Key.price], expected: StoreKit.BackingValue) [492a4cfa_SK1] Could not parse product: missingValue(for:
4
0
229
3w
Overriding global new and delete is not working.
We developing Native App with C++17 for iOS. We override global new and delete operators. This App deallocate all allocated memories correctly by Run on Xcode (Command + R), but exception occurs launch from xcrun or App icon on iPhone. I debugged the exception. Overriding new operation was called correctly, but overriding delete operation was not called. The default delete was called. I'm not sure why is that. STEPS TO REPRODUCE Build xcode project. Run xcrun devicectl device install app --device Run xcrun devicectl device process launch --console --device PLATFORM AND VERSION iOS Development environment: Xcode 16.4, macOS macOS Sequoia 15.5 Run-time configuration: iOS 18.5 main.cpp I attached is sample code to reproduce this problem. main.cpp
4
0
607
3w
Reply to macOS 26 Tahoe Screen Saver issues
Yep. Sadly, that’s expected )-: There are actually a bunch of bugs mentioned in this thread, so let me summarise: FB19580645 — This is the scroll view nib issue. Looking at the underlying bug (r. 157494480) it’s hard to tell when the fix for this will land [1]. Given that, I recommend that you continue to test with macOS and Xcode betas as we seed them. FB6363533, FB19235887 — These are both requests for a new screen saver API based on appex technology. I think it’s safe to say that that won’t happen in macOS 26 |-: FB19201567, FB19204084, FB19206021 — These are all functionality issues with the existing screen saver API. I don’t have any news to share here. Certainly, I don’t expect to see improvements in 26.0b7. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] It’s always hard with nib bugs because part of the code lives in the OS and part of the code lives in Xcode.
Topic: App & System Services SubTopic: General Tags:
3w
Unable to use Bluetooth in watchOS companion app if iOS uses AccessorySetupKit
FB18383742 Setup 🛠️ Xcode 16.4 (16F6) 📱 iPhone 13 mini (iOS 18.0.1) ⌚️ Apple Watch Series 10 (watchOS 11.3.1) Observations As AccessorySetupKit does not request Core Bluetooth permissions, when a watchOS companion app is installed after having installed the iOS app, the toggle in the watch settings for Privacy & Security > Bluetooth is turned off and disabled After removing the iPhone associated with the Apple Watch, Bluetooth works as expected in the watchOS app Upon reinstalling the iOS app, there's a toggle for Bluetooth in the iOS ASK app's settings and the ASK picker cannot be presented 🤨 From ASK Documentation: AccessorySetupKit is available for iOS and iPadOS. The accessory’s Bluetooth permission doesn’t sync to a companion watchOS app. But this doesn't address not being able to use Core Bluetooth in a watch companion app at all 🥲 Reproducing the bug Install the iOS + watchOS apps Launch iOS app, tap start scan, observe devices can be discovered (project is set up to find heart rate
2
0
339
3w
Xcode 26 Beta 3 Crash on iOS 18 Simulators - NSInvalidUnarchiveOperationException (ToolbarVisualProvider8RootView missing)
Hi, I’m seeing a crash when running my app on iOS 18 simulators or devices using Xcode 26 beta 3. My app’s minimum deployment target is iOS 17, and the crash does not happen when running from Xcode 16.4. The crash occurs specifically at this line: return UIStoryboard(name: storyboard.rawValue, bundle: nil) .instantiateViewController(withIdentifier: view.rawValue) Crash Details: ** Terminating app due to uncaught exception 'NSInvalidUnarchiveOperationException', reason: 'Could not instantiate class named _TtGC5UIKit17UICoreHostingViewVCS_21ToolbarVisualProvider8RootView_ because no class named _TtGC5UIKit17UICoreHostingViewVCS_21ToolbarVisualProvider8RootView_ was found; the class needs to be defined in source code or linked in from a library (ensure the class is part of the correct target)' *** First throw call stack: (0x191c3321c 0x18f0cdabc 0x191c91ea0 0x19d740774 0x19d740a18 0x19d740cac 0x194626680 0x194dbc784 0x19d740890 0x19d740cac 0x1949aadd8 0x19d740890 0x19d740a18 0x19d740cac 0x19480
Topic: UI Frameworks SubTopic: UIKit Tags:
9
0
443
3w