xcode github

I have Mac mini intel, and updated top Sequia 15.7.2 and updated Xcode to 26 and now it crashes on launch. I uninstalled and reinstalled and still crashes. I uninstalled and installed Xcode 16.4 and that crashes on launch also. I've looked all over for help but cannot find anything. Can anyone please help me with this?

Hi, I am trying to update my apps and i couldn't do it, can anyone please help? this is what happened to me. Once my membership renewed, i couldn't compile my apps due to signing error. here is the error message: Xcode archive done. 31.7s Failed to build iOS app Error (Xcode): Communication with Apple failed: Your team has no devices from which to generate a provisioning profile. Connect a device to use or manually add device IDs in Certificates, Identifiers & Profiles. https://developer.apple.com/account/ /Users/tony/vn246/ios/Runner.xcodeproj when I go to the portal developer.apple.com/account to create the Provisioning Profile manually then it said there is no device, and when i go into the Devices section then the machine uuid is added and it's there and registered, i had always been compiling with it before the old membership was expired. I tried to remove those and re-added and the error still persisted. P.S.: I renewed all my certificates (removed old and recreated new) thank you

运营了一年多app，更新了很多版本，这一版更换了下ui的预览图，然后更新的时候一直正在等待审核，等了很多天没有结果，给苹果发了邮件询问，然后被标记封号下架了？请问这个是怎么回事，就是常规更新为什么不审核，然后又下架了？申诉了越没有任何回复邮件，这妥妥的霸王条款， appid：6670458903 串聊 请求苹果公司能开发者给恢复正常更新，谢谢 Pending Termination Notice Upon further review of the activity associated with your Apple Developer Program membership, it's been determined that your membership, or a membership associated with your account, has been used for dishonest or fraudulent activity, in violation of the Apple Developer Program License Agreement. Given the severity of the identified issues, your account has been flagged for removal. Because your account has been flagged for removal, any earnings payments are paused and app transfers are disabled. Creating new accounts after receiving this message may result in the termination of the new or associated accounts. Evidence of Dishonest or Fraudulent Activity App submissions from your account have repeatedly violated the App Review Guidelines in an attempt to evade the review process. After multiple resubmissions, the

I had, a long time ago (over 10 years) developed an application that is connected to my UPS (for solar panels). Until yet it worked very well, and I didnot have to compute more than making updates of XCode. That was all. But yet I have swiched to the latest value of switch, and it continue to compile, but it does'not work. I am asking to yo in order keeping my app working as previously. As it does not work, which library is replacing Cloudkit.framework ? and which library is replacing InsPersistantContainer.framework ? Have a good day Guy Desbief

We first discovered this issue in our own product, but we were able to reproduce it even when using Apple’s official demo: https://developer.apple.com/documentation/alarmkit/scheduling-an-alarm-with-alarmkit Reproduction Steps: Set an alarm on iOS 26.1 using AlarmKit. Upgrade the device to iOS 26.2 beta 3 or later. The alarm will no longer ring. Based on our testing, versions prior to 26.2 beta 2 do not exhibit this issue, so it appears that something introduced in beta 3 has caused the regression. The results are as follows: iOS 26.1 → iOS 26.2 beta 2 or earlier: Alarms ring normally iOS 26.1 / iOS 26.2 beta 2 → iOS 26.2 beta 3 / iOS 26.2 RC: Alarms fail to ring iOS 26.2 beta 3 → iOS 26.2 RC: Alarms ring normally This issue is critical. Users currently on iOS 26.1 may experience alarms failing to ring after updating their system, which can cause real-life disruptions (e.g., being late for work). We strongly recommend addressing this as soon as possible. Xcode Version: Version 26.1.1 (17B100) Feedbac

Stale TBD Files Cause Runtime Crash When Framework Changes from Dynamic to Static Summary When using EAGER_LINKING=YES, Xcode generates TBD files for dynamic frameworks. When a framework changes from dynamic to static, Xcode doesn't remove the stale TBD, causing dyld: Library not loaded crash at runtime. Environment Xcode 16.4 (16F6), macOS Darwin 24.6.0, iOS Simulator 18.5 Steps to Reproduce Project Structure: MainApp (EAGER_LINKING=YES) ProjectA/SharedLib (dynamic, mh_dylib) ProjectB/SharedLib (static, staticlib) Steps: Build with ProjectA (dynamic framework) → TBD created in EagerLinkingTBDs Switch workspace to ProjectB (static framework) without cleaning DerivedData Build again → BUILD SUCCEEDED Run app → CRASH: dyld: Library not loaded Root Cause Xcode adds -F EagerLinkingTBDs before -F Build/Products: -F/.../EagerLinkingTBDs/Debug-iphonesimulator ← checked FIRST -F/.../Build/Products/Debug-iphonesimulator ← checked SECOND The linker finds the stale TBD first and treat

Hello! I’m building my Swift Student Challenge project in Swift Playgrounds, and I’ve run into an issue with app orientation. Since this is a game, the layout and interactions only work correctly in landscape, but Playgrounds doesn’t offer the usual orientation settings you’d configure in Xcode. Is there a recommended way to force a landscape-only experience in Swift Playgrounds using SwiftUI? Any workarounds or guidance would be greatly appreciated! Thank you!

Hi everyone, I’m unable to enable Xcode Cloud for any app on my account. At the final step of the Xcode workflow setup (“Confirm App on App Store Connect”), pressing Complete always returns: “ could not be added to Xcode Cloud. Authentication credentials are invalid.” This affects both existing apps and completely new test apps with fresh bundle IDs. What I’ve verified • I am Account Holder and Admin. • All agreements are accepted. • App creation, bundle ID registration, and certificate management work normally. • I’ve removed/re-added my Apple ID in Xcode and cleared all Xcode-* tokens from Keychain. • Test apps in clean Git repos reproduce the same error. Support I have already opened Case ID 102769512657 with Apple Developer Support, but I’m posting here in case others have seen this issue or know of additional steps to confirm the provisioning state.

I have attached 2 images of our Mac Apps user interface. The app is built for macOS 15.6 or newer. On macOS 15 and earlier everything looks fine. But the same App running on macOS 26 the controls disappear. We were able to temporarily resolve the problem by adding UIDesignRequiresCompatibility to the info.plist. This type of nonsense happens all over the app without the compatibility switch. Shouldn't all these legacy controls be backward compatible on Glass? This part of the app where the controls are disappearing is built in Swift (not swift ui) and uses standard programatic layout and visual constraints. On macOS 26, there are no Xcode warnings or layout errors on the console relative to the layout so we are confused as to how we would resolve this without the use of UIDesignRequiresCompatibility. Is this some kind of bug in NSControl glass compatibility? We are not likely to move the entire app into SwiftUI anytime soon. How would we resolve this?