Search results for

xcode github

94,696 results found

Post

Replies

Boosts

Views

Activity

Reply to Errors with PerfPowerTelemetryClientRegistrationService and PPSClientDonation when running iOS application in Xcode
Thanks Quinn. This looks to possibly be an internal Apple bug with MKMapView. I can recreate the issue with the following code: import MapKit import SwiftUI struct MyMapkitView: UIViewRepresentable { typealias UIViewType = MKMapView func makeUIView(context: Context) -> MKMapView { return MKMapView() } func updateUIView(_ uiView: MKMapView, context: Context) {} } struct ContentView: View { var body: some View { VStack { MyMapkitView() } .padding() } } Which immediately gives the errors below that match what I'm seeing in my app. I wish I could ignore it, but it quite literally is happening 2-3 times a second so the log is completely buried with these messages. This only started happening when I upgraded Xcode to 26.
1w
Confirmation Items Regarding the Mandatory UIScene Lifecycle Support in iOS 27
After reviewing the following Apple Technote, I have confirmed the statement below: https://developer.apple.com/documentation/technotes/tn3187-migrating-to-the-uikit-scene-based-life-cycle In the next major release following iOS 26, UIScene lifecycle will be required when building with the latest SDK; otherwise, your app won’t launch. While supporting multiple scenes is encouraged, only adoption of scene life-cycle is required. Based on the above, I would appreciate it if you could confirm the following points: Is my understanding correct that the term “latest SDK” refers to Xcode 27? Is it correct that an app built with the latest SDK (Xcode 27, assuming the above understanding is correct) will not launch without adopting the UIScene lifecycle, with no exceptions? Is it correct that an app built with Xcode 26 without UIScene lifecycle support will still launch without issues on an iPhone updated to iOS 27?
Topic: UI Frameworks SubTopic: General Tags:
2
0
209
1w
Reply to Confirmation Items Regarding the Mandatory UIScene Lifecycle Support in iOS 27
Thank you for your reply. Assuming that the next major iOS release version is iOS 27, I understand that apps built with Xcode 27—which would be considered the “latest” at the time of release—will need to support the scene lifecycle. Conversely, I understand that if an app is built with Xcode 26, it is not yet necessary to support the scene lifecycle. Based on past years, it can be inferred that the deadline for supporting Xcode 27 will be around April 2027, so I am planning to complete the necessary changes by then.
Topic: UI Frameworks SubTopic: General Tags:
1w
Xcode crashing in live view
I'm new to Xcode. I just downloaded version 26.2 and I'm working on an iMac with macOS Sequoia 15.7.3. I'm created a playground with some very simple code and it crashes when I click live view. I tried looking all over online for a solution and nothing has worked. I tried uninstalling and reinstalling Xcode and still have the same problem. When running the code with the console open I do see the following error. objc[19786]: Class _TtC16AppIntentSchemas16AppIntentDomains is implemented in both /System/Library/PrivateFrameworks/AppIntentSchemas.framework/Versions/A/AppIntentSchemas (0x2840a4c28) and /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/AppIntentSchemas.framework/Versions/A/AppIntentSchemas (0x3276359e8). This may cause spurious casting failures and mysterious crashes. One of the duplicates must be removed or renamed. I went to the first folder mentioned in the error /System/Library/PrivateFrameworks/AppIntentSchemas.framework
2
0
65
1w
Reply to Xcode crashing in live view
Thanks for the post, looks like you are trying to reference a framework that isn’t there and should not be there. The issue is in your Xcode project, look at the reference of frameworks and remove the AppIntentSchemas.framework Can you post your answer about the UIKIT? This points to a conflict between a framework provided by the underlying macOS system and one provided by Xcode's toolchain. This is not a problem with your simple Playground code itself, but rather an environmental conflict, likely caused by having a beta or pre-release version of macOS or Xcode components installed that clash with your current setup. If you using Xcode create a new project and add your code. Albert Pascual
  Worldwide Developer Relations.
1w
In-App Provisioning
I'm implementing the in app provisioning in a financial project. I got my entitlement identifier, I'm also implementing the wallet extension but I have the problem with Xcode. Domain: IXUserPresentableErrorDomain Code: 1 ... NSExtensionPointIdentifier key in the NSExtension dictionary in its Info.plist that does not correspond to a known extension point. But I'm not sure what does this mean, I reviewed the info.plist form the project and the wallet extension
4
0
119
1w
Reply to In-App Provisioning
Thanks for that!! Very useful, I would review each string as the NSExtensionPrincipalClass does not look correct to me but is set by Xcode, but it's been a while since I create an extension, I should try today to create a new one to see how it works. I'll invite extension experts to look at your configuration. As Xcode sets your string must be correct, just make sure the method get called? $(PRODUCT_MODULE_NAME).handler.... https://developer.apple.com/documentation/BundleResources/Information-Property-List/NSExtension/NSExtensionPrincipalClass NSExtensionPointIdentifier com.apple.passkit.issuer-provisioning NSExtensionPrincipalClass $(PRODUCT_MODULE_NAME).IssuerExtensionHandler https://developer.apple.com/documentation/bundleresources/managing-your-app-s-information-property-list#Manually-supply-an-information-property-list-file https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/AppExtensionKeys.html So it I follow the documentation i
1w
Reply to iOS 26.2 Safari back button fails to re-open tab with same target
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 this thread. Bug Reporting: How and Why? has tips on creating your bug report.
Topic: Safari & Web SubTopic: General Tags:
1w
Simulator is not working.
Hi, I am a UI designer and a total newbie with coding, so I have been using AI in Xcode to do all my coding for my personal project. Everything was working fine until this morning, when I tried to run my app in the simulator (I didn't even change any code from the last time I ran the simulator) and now the simulator is crashing and freezing and I have been trying to fix it with the AI recommendations, but it seems way too complicated for me to handle even with AI's help. I feel like I need to talk to an expert and guide me out of this hole. Please help. Thank you!
3
0
344
1w
Share Issue
We are facing an issue where we share the Taqeem app (https://apps.apple.com/app/id6692622292) but sharing is not working properly. Few iPhone gives image, url however few share only image as shown in attached screenshot. Also with our devices (iPhone 16 Pro, iPhone 14 Pro - especially Pro series) if we share any ad from our app, it is sharing only image and text + url that we share also not get shared. We were using regular code as below. So we believe that Share using UIActivityViewController is having an issue. Images are available at below links. https://ibb.co/RkG70NqH https://ibb.co/dJKBR9jc Code I used is as below. func shareDetails(shareText : String, shareURLString : String) { if let shareURL : NSURL = NSURL(string: shareURLString) { // If you want to use an image let image : UIImage = UIImage(named: logo.png) let activityViewController : UIActivityViewController = UIActivityViewController(activityItems: [shareText, shareURL, image], applicationActivities: nil) // This lines is for
3
0
115
1w
Reply to XCode26.2 ld: Assertion failed: ((ct == Atom::ContentType::objcConst) || (ct == Atom::ContentType::objcData) || (ct == Atom::ContentType::constData) || (ct == Atom::ContentType::constText)), function ObjCClassReadOnlyDataRef, file Atom.cpp, line 329
Thanks for this very interesting post. I'm not an expert in this field and I invite experts to comment, in my modest opinion, It looks like there’s something unexpected with ObjC/Swift metadata. Can we ask them for a focused sample project that reproduces the issue, can you make a copy of the project that is causing the issue, and then remove everything that isn’t important to keep the meta data in the project that may be causing this? Maybe the linker error you're encountering in Xcode 26.2 after migrating from Xcode 16.2, along with the modifications you've made to the linker flags, points to a deeper issue with how object files are being processed, specifically related to Objective-C runtime data. Could that mean or indicates there is an incompatibility or corruption in Objective-C metadata? Any object files or libraries you're linking were compiled with an older compiler version? Any external libraries or frameworks, with the Xcode 26.2 compiler. If you're using CocoaPods or Car
1w
Reply to iOS Simulator fails to boot (18.6 / 26.1 / 26.2) – launchd_sim could not bind to session
Having the same issue, Macos Tahoe 26.2, i tried everything i found on net: deleting caches, all xcode files, reinstalling it, rebooting my computer, deleting all simalator devices, deleting IOS from Xcode => setting components, downloading it again. I tried installing older IOS, no help, when starting emulator i have this error: Unable to boot the Simulator And this error, when i'm trying to do this from terminal == Devices == -- iOS 26.2 -- iPhone 17 Pro (1FC8FFC9-A04D-434B-85F0-F5AE2DB4CDAC) (Shutdown) iPhone 17 Pro Max (71761C54-D406-496E-A552-CD72FACD10DA) (Shutdown) iPhone Air (64607ACA-F580-4A6A-A816-1AD1E8BEBC32) (Shutdown) iPhone 17 (7ECEC4C0-0DC9-4B5A-A9A0-05E4B1038C68) (Shutdown) iPhone 16e (A175B467-438D-41A7-B537-D7E23B4FFF21) (Shutdown) iPad Pro 13-inch (M5) (FA74F9C7-93C9-40D6-86F5-74E46FCCF7EC) (Shutdown) iPad Pro 11-inch (M5) (73A17C77-DBFA-4748-880D-15FBBE43E57E) (Shutdown) iPad mini (A17 Pro) (09BF89D2-640C-4083-937A-4859633BB69E) (Shutdown) iPad (A16) (5FF5869B-042F-48
1w
Reply to Linker nondeterminism (ld_new) involving branch islands
[quote='873554022, jamie_sq, /thread/805609?answerId=873554022#873554022, /profile/jamie_sq'] if any investigation has revealed whether there's anything that can be done to work around the problem [/quote] Nothing obvious popped out )-: I can say that we do fully understand the issue now and that makes the likelihood of a fix promising. However, I can’t offer a concrete timeline, other than to confirm that the fix didn’t catch the Xcode 26.2 bus. As always, I recommend that you re-test with future beta releases of Xcode as we seed them. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
1w
Linker nondeterminism (ld_new) involving branch islands
Hi, I'm investigating what looks like possibly nondeterministic behavior when linking large iOS app binaries. I do not have a concise reproduction of the issue yet, but am trying to hunt down possible leads. In particular, the problem appears to surface when invoking clang to link a binary and the resulting order of the 'branch island' instructions appears to be random each time the binary is linked (as shown by the link map output). I was wondering if anyone with insight into the linker's current implementation could shed light on whether that is expected, and if there is anything that can be done to prevent it. FWIW, it seems like it might be size-dependent as smaller app binaries don't appear to exhibit the same behavior. I'd be glad to share more specifics and hopefully a reproduction if I can ever find one eventually. Some environment info (Xcode 16.4 toolchain): clang -v: Apple clang version 17.0.0 (clang-1700.0.13.5) Target: arm64-apple-darwin24.6.0 Thread model: posix InstalledDir: /Applicati
4
0
525
1w