Hello, I am trying out Xcode Cloud for the first time. I could connect to Github in the initial setup and had a few failed builds (package resolution error), which I resolved fairly quickly. Now whenever I am trying to build, I get the following error: Xcode Cloud is unable to connect to the repository “”. Reconnect the repository to resume builds. I am unable to remove the connection from settings as well because it's stuck in a loading state. Is there a way to fix this?
Post not yet marked as solved
Currently seeing this with Github. I have allowed access from the GIthub side but Xcode Cloud fails to receive that access.
Post not yet marked as solved
When I have the Address Sanitizer option turned off in Xcode(version 15.3), the project builds successfully. However, as soon as I enable the option, the build fails with the error message: 'Could not find path to clang binary to locate Address Sanitizer library.' I found libclang_rt.asan_ios_dynamic.dylib in the Xcode directory and added it to the build Phases -> Link Library with Libraries. However, I still get the same error. But when I create a new project and enable the Address Sanitizer option, it builds successfully.
Post not yet marked as solved
We are using and iOS version 17.4.1 and 17.5(beta) , and when are we facing the issue for local network permission in our app. Success scenario steps: Don't allow the local network permission in our App Allow it manually in app setting for local network permission(works only in first install of the App) We are able to call the API successfully Error scenario steps: Allow the local network permission popup to app when asked for permission Call the API successfully Uninstall the app and install the same app again and don't allow the local network permission API call fail's Manually change the local network permission to allow in app settings Still the API call fails even if we allow the local network permission Conclusion : We are getting API error when re-install the app and if it is not allowed local network permission as well as when we allow the local network permission. Looks like caching issue. Note: Even if uninstall and install multiple time and allow the local network permission from
Post not yet marked as solved
URLSesison suspends its request timeout while waiting for the delegate to respond to an authentication challenge. However, that doesn’t guarantee that there’ll be no timeout. In the case of a server trust evaluation challenge, you’re called during the TLS handshake process. If you delay too long, the server might time out the connection. You generally deal with this using retry logic and caching. If a request failed during a challenge, you retry, and hopefully that’ll hit your cache of the challenge result. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Post not yet marked as solved
Hi, We recently released a version of our app where we use 'NWParameters.PrivacyContext'. On iOS 17.4 and iOS 17.4.1 the app crashes with a following crash: Distributor ID: com.apple.AppStore Hardware Model: iPhone12,1 Process: Path: Identifier: Version: AppStoreTools: 15E204 AppVariant: 1:iPhone12,1:15 Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd [1] Coalition: [4899] Date/Time: 2024-04-29 01:50:13.4113 +0300 Launch Time: 2024-04-29 01:13:47.6252 +0300 OS Version: iPhone OS 17.4.1 (21E236) Release Type: User Baseband Version: 5.00.00 Report Version: 104 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000054 Exception Codes: 0x0000000000000001, 0x0000000000000054 VM Region Info: 0x54 is not in any region. Bytes before following region: 4334124972 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL UNUSED SPACE AT START ---> __TEXT 102558000-1063e4000 [ 62.5M] r-x/r-x SM=COW Termination Reason: SIGNAL 11 Segmentation faul
Post marked as Apple Recommended
Hey guysI’ve been trying to pay for Apple Developer Program enrollment for about a week and still no luck. As well as I got from a small talk with the customer support – Apple never got my money. So it seems like my payment authorization fails all the time. But I don’t know what’s really going on.Have any of you ever had issues like that?Or maybe you just know what’s going on and how to fix it?
Post not yet marked as solved
I'm having an issue that I can't quite figure out. I'm new to Swift and Xcode, I set up Xcode last week and it worked fine all week.Then today I started getting an issue when I click on any storyboard in any project where it takes aprox 20 seconds of spinning before it loads and a long time when I try to change anything. The projects I created last week don't display properly anymore, no images, text fields resized to be unreadable. I even made a hello world project and added just one object (I tried different types) and I still get Internal error occurred. Editing functionality maybe limited and the link to report a bug has no file. When I try to build the project the project succeeds, but I get the following error:DetailsUnable to boot the Simulator.Domain: NSPOSIXErrorDomainCode: 60Failure Reason: launchd failed to respond.--System InformationmacOS Version 10.15.4 (Build 19E287)Xcode 11.4.1 (16137)When I try to build selecting my iPhone and putting in my team, it says device not available (however
Please run the following UIKit app. It uses a collection view with compositional layout (list layout) and a diffable data source. The collection view has one section with one row. The cell contains a text field that is pinned to its contentView. import UIKit class ViewController: UIViewController { var collectionView: UICollectionView! var dataSource: UICollectionViewDiffableDataSource! override func viewDidLoad() { super.viewDidLoad() configureHierarchy() configureDataSource() } func configureHierarchy() { collectionView = .init(frame: .zero, collectionViewLayout: createLayout()) view.addSubview(collectionView) collectionView.frame = view.bounds } func createLayout() -> UICollectionViewLayout { UICollectionViewCompositionalLayout { section, layoutEnvironment in let config = UICollectionLayoutListConfiguration(appearance: .insetGrouped) return NSCollectionLayoutSection.list(using: config, layoutEnvironment: layoutEnvironment) } } func configureDataSource() { let cellRegistration = UICollectionView.CellRegi
I have a Swift project with some C code in it. The C code creates a byte array with about 600K elements. Compiling under Xcode, the compilation takes a really long time. When I try to run the code, it fails immediately upon startup. When I cut this large array out of the build, everything else works fine. Does anyone know what's going on here, and what I might do about it?
Post not yet marked as solved
I use to archive my app all the time and never had this problem the other day i implemented apple pay in my app but when i wanted to archive the app i couldnt and kept getting this error over and over even tho i tried all the solutions online Error : error: shell-init: error retrieving current directory: getcwd: cannot access parent directories: Operation not permitted chdir: error retrieving current directory: getcwd: cannot access parent directories: Operation not permitted chdir: error retrieving current directory: getcwd: cannot access parent directories: Operation not permitted chdir: error retrieving current directory: getcwd: cannot access parent directories: Operation not permitted chdir: error retrieving current directory: getcwd: cannot access parent directories: Operation not permitted Standalone embedder initialization failed: Error determining current directory: Operation not permitted i tried to go to settings Security & Privacy->Full Disk Access then allow xcode
Post not yet marked as solved
Hi, I am running into an error on XCode 15 (iOS 17+). When I am trying to play an iframe on the app. I see this error popup. Warning: -[BETextInput attributedMarkedText] is unimplemented Failed to request allowed query parameters from WebPrivacy. How do I fix this issue? I never saw this before so I am sure it is new. The app use to run fine as well.
Post not yet marked as solved
Hello Geeks, After testing our iOS app using MobSF, the report highlighted that the binary has Runpath Search Path (@rpath) set. In certain cases an attacker can abuse this feature to run arbitrary executable for code execution and privilege escalation.
The Runpath Search Path directs the dynamic linker to search for dynamic libraries (dylibs) in a specified order of paths, similar to how Unix searches for binaries in $PATH. However, this setup introduces a vulnerability wherein an attacker could place a malicious dylib in one of the initial paths, thereby hijacking the legitimate library sought by the linker.
Despite attempting to manually strip the binary following instructions from https://inesmartins.github.io/mobsf-ipa-binary-analysis-step-by-step/index.html, the same warnings persist in the report. We urgently seek assistance in resolving this issue and eagerly await your response.
We have a legacy app written in a mix of C, ObjC, C++ and ObjC++ with .xib files. It is not sandboxed. It sends an Apple Event to TV (the app of that name from Apple, not a physical TV) using /usr/bin/osascript, calling a compiled Apple Script which is in our app bundle's Resources directory with parameters which we generate in our app at runtime. The first time it does this on a fresh system, the OS puts up a dialog asking for permission to control TV, and after the user clicks Allow, our app appears under Security and Privacy in the Automation section. That's all fine, but what is unexpected is that the app has no Apple Events entitlement (com.apple.security.automation.apple-events), and it doesn't have a NSAppleEventsUsageDescription string either. The documentation at https://developer.apple.com/documentation/bundleresources/entitlements/com_apple_security_automation_apple-events says Your app doesn’t need the Apple Events Entitlement if it only sends Apple events to itself or to other processes signed wi
Post not yet marked as solved
Running on a Core i9 MacBook Pro with macOS 13.4 (22F66) and the Xcode 15 beta. Running Export Localizations seems to work fine with smaller projects, but in my larger project, it's not working unless I do a Clean first. The way my project is set up is that the main project depends on a few dynamic frameworks built from other Xcode projects which are incorporated into the main project and set as dependencies. What happens is that I'm getting the error Unable to build project for localization string extraction. See the build logs for failure description. In the logs, I see that the Link (x86_64) step succeeds, but the Link (arm64) step fails, with a Could not find or use auto-linked framework 'MyFramework' message for each framework dependency that's in another Xcode project. This would suggest that the dependencies are being built only for x86_64. If I clean the project, the Export Localizations will then succeed, but if I do a regular build again, Export Localizations goes back to being broken. What
kushsolitary.