Search results for

xcode github

93,987 results found

Post

Replies

Boosts

Views

Activity

Apple CDN connection error after changing server ip version to v6
The universal links for my apps stopped working. The server where the AASA files where hosted worked on IPV4 exclusively, a few days ago i changed the configuration to IPV6 only. I´ve created new IPV6 entries, renewed all certifactes and deleted all IPV4 entries for the domains. All seemed fine, but at Saturday I realized that my universal links stopped working for new user. What i´ve done to find the issue: Example domain that was used for debugging: https://developffw.burns.fun I´ve verified the AASA file is hosted properly by using different browsers and Postman to retrieve it. The file can be accessed and the certificates look fine. Output of curl -v https://developffw.burns.fun/.well-known/apple-app-site-association * Host developffw.burns.fun:443 was resolved. * IPv6: 2a01:4f8:13b:340a::2 * IPv4: (none) * Trying [2a01:4f8:13b:340a::2]:443... * schannel: disabled automatic use of client certificate * ALPN: curl offers http/1.1 * ALPN: server accepted http/1.1 * Established connection to developffw.burns.
4
0
67
3h
UIBarButtonItem-The background color of UIBarButtonItem is missing?
UIButton *backBtn = [UIButton buttonWithType:UIButtonTypeCustom]; backBtn.frame = CGRectMake(0, 0, 44, 44); [backBtn setImage:[UIImage imageNamed:@back] forState:UIControlStateNormal]; [backBtn addTarget:self action:@selector(gotoBack) forControlEvents:UIControlEventTouchUpInside]; UIBarButtonItem *backItem = [[UIBarButtonItem alloc] initWithCustomView:backBtn]; // backItem.hidesSharedBackground = YES; // backItem.tintColor = [UIColor redColor]; self.navigationItem.leftBarButtonItem = backItem; I am using Xcode 26, which is compatible with iOS 26. After I set up the back button of the navigation bar, why are the background colors of the back buttons on some pages gray? When I pushed the new page, after popping back to the current page, the buttons with the gray background turned back to the white background. This issue will also affect the rightBarButtonItem.
Topic: UI Frameworks SubTopic: UIKit
1
0
176
12h
Reply to Xcode 26.1 re-release?
There was a release of Xcode 26.2 that was dated December 4th. Then there was a release of Xcode 26.1 on December 16. Which is the most current? Why was there a later release of 26.1 when there was a ralease of that level in November 11 followed by a 26.1.1? This release strategy is somewhat confusing.
13h
Xcode Cloud Export Archive Fails with Xcode 26.2 RC
Export archive step fails in Xcode Cloud when using Xcode 26.2 (17C48) RC. The same project exports successfully when switching back to Xcode 26.1 in Xcode Cloud workflow settings. The same project exports successfully when using Xcode 26.2 RC locally. Projects without Apple Watch app do not encounter this issue (not so sure about this). From Xcode Cloud UI: Exporting for App Store Distribution failed. Please download the logs artifact for more information. Run command: 'xcodebuild -exportArchive ... Command exited with non-zero exit-code: 70 From xcodebuild-export-archive.log: error: exportArchive Automatic signing cannot update bundle identifier io.***.***.watchkitapp. error: exportArchive No profiles for 'io.***.***.watchkitapp' were found error: exportArchive Automatic signing cannot update bundle identifier io.***.***. error: exportArchive No profiles for 'io.***.***' were found ** EXPORT FAILED ** IDEDistribution: App Store Connect request for store
6
0
279
14h
Reply to Xcode Cloud Export Archive Fails with Xcode 26.2 RC
@Gong Thank you for providing the comprehensive post and the bug report number. You made sure to use the release version of Xcode correct? 17C52? Please allow the engineering team ample time to investigate this issue, considering the upcoming holiday season. You can see the status of your feedback in Feedback Assistant. There, you can track if the report is still being investigated, has a potential identifiable fix, or has been resolved in another way. The status appears beside the label Resolution. We're unable to share any updates on specific reports on the forums. For more details on when you'll see updates to your report, please see What to expect after submission. Albert Pascual
  Worldwide Developer Relations.
16h
Questions about DeclaredAgeRange's isEligibleForAgeFeatures instance variable
Our team is in the process of updating our apps to comply with Texas's new state law. In order to minimize user confusion and provide the most ideal flow to access the app as possible, we have a few questions we would like answered. Summary of questions: Is isEligibleForAgeFeatures intended to be accurate and accessible before the user has accepted the Age Range permissions prompt? As other US states and/or other countries adopt a similar law going forward, will this instance variable cover those locations? Will the runtime crashes on isEligibleForAgeFeatures and other symbols in the DeclaredAgeRange framework be addressed in a future RC or in the official release? Details and Investigations: With regards to isEligibleForAgeFeatures, our team has noticed that this value is always false before the age range prompt has been accepted. This has been tested on the XCode RC 26.2 (17C48). Assuming the request needs to be accepted first, isEligibleForAgeFeatures does not get updated immediately when the user
1
0
401
16h
Reply to App Review Rejected, Invalid Binary, App Version
Thanks for the post. Have you search the forums for this issue? Are you utilizing any other software besides Xcode? Are you using Objective-C with empty names in the metadata? To identify the binaries with those conditions, you can run the following Terminal command on each binary inside the app: ‘% xcrun dyld_info -objc Payload/YourApp.app/YourApp | grep (null)”’ Can you check the build log in Xcode and provide me with those messages including the warnings are really important and may give us a clue. Can you share those warnings? Additionally, could you please share the Xcode version, the minimum operating system requirements, and any relevant build settings that may be pertinent to this task? I eagerly anticipate your responses to guide you toward a comprehensive resolution for this matter, provided the script yields favorable outcomes. Otherwise if is not the issue I am thinking with Objective-C, please get it touch with App Store Connect support as they’ll have the reason the bi
16h
Reply to Instruments Crash using swiftui instrument
Thanks for the post. It looks like you're encountering a specific crash related to the SwiftUI instrument in Xcode 26.2, which can be quite frustrating, especially when it interrupts a useful workflow. Given that you've already attempted some common troubleshooting steps like removing derived data, reinstalling, updating Xcode, and restarting devices, and that is a crash on the Instruments app let’s go ahead and file a bug: Once you open the bug report, please post the FB number here for my reference. If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why? Albert Pascual
  Worldwide Developer Relations.
16h
Instruments Crash using swiftui instrument
Instruments is crashing when the swiftui instrument is stopped (the session is finished) and the transfer begins from device to device: Crashed Thread: 11 Dispatch queue: com.apple.swiftuitracingsupport.reading Exception Type: EXC_BAD_INSTRUCTION (SIGILL) Exception Codes: 0x0000000000000001, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 4 Illegal instruction: 4 Terminating Process: exc handler [1633] I've tried removing derived data, reinstalling xcode, updating xcode (I originally thought this might be the issue -- I needed to update to 26.2 from the 26 RC -- the update didn't fix crash or change the crash report), and restarting both devices. I'm running Instruments/Xcode 26.2 on a MacBook Pro 15 (2018) running Mac OS 15.7.2 (24G325) with an iPhone 16 Pro Max running 26.2. Hoping someone else might have seen this or could help me troubleshoot. I find the swiftui instrument be helpful and like to use it :) I can post a complete crash report as well.
1
0
18
16h
Reply to XCTFail immediately aborts the test in Xcode 26 — no retry on failure
This is a known issue in Xcode 26 and later. When using XCTest in Xcode 26 and later, a test failure will cause the test runner process to terminate and relaunch before continuing to the next test if all the following conditions are met: The test class is written in Swift, The test’s continueAfterFailure property is set to false, Either the test method is async or the async overload of setUp or tearDown is overridden, and The test encounters a failure. Under these conditions, the first issue recorded by each affected test will cause the test runner process to be terminated after its tearDown sequence finishes. A new test runner process will then be launched, and execution will continue with the next test. This applies to any XCTAssert calls which fail, all calls to XCTFail, and failures encountered by UI automation API calls. This change was made to XCTest in order to improve reliability, since the XCTestCase.continueAfterFailure API uses Objective-C exceptions and can cause problems when us
17h
XCTFail immediately aborts the test in Xcode 26 — no retry on failure
Hi, I’m seeing an unexpected change in how XCTFail behaves in UI tests after updating Xcode. I use the following helper method: `func waitForExistance(file: StaticString, line: UInt) -> Self { if !(element.exists || element.waitForExistence(timeout: Configuration.current.predicateTimeout)) { XCTFail(couldn't find element: (element) after (Configuration.current.predicateTimeout) seconds, file: file, line: line) return self } else { return self } }` In Xcode 16.4, this worked as expected: – when an element wasn’t found, XCTFail was triggered, but the test continued running, allowing my retry logic to execute. After updating to Xcode 26.1 / 26.2 - the test now immediately aborts after XCTFail, without executing the next retry. The logs show: `t = 113.22s Tear Down t = 113.22s Terminate com.viessmann.care:81789 *** Assertion failure in -[UITests.Tests _caughtUnhandledDeveloperExceptionPermittingControlFlowInterruptions:caughtInterruptionException:whileExecutingBlock:], XCTestCase+Iss
3
0
159
17h
Reply to UIImageWriteToSavedPhotosAlbum doesn't working on Mac catalyst
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. If you post the Feedback number here I'll check the status next time I do a sweep of forums posts where I've suggested bug reports. Bug Reporting: How and Why? has tips on creating your bug report.
Topic: Programming Languages SubTopic: Swift Tags:
18h