Build, test, and submit your app using Xcode, Apple's integrated development environment.

Posts under Xcode tag

200 Posts
Sort by:

Post

Replies

Boosts

Views

Activity

The compiler is unable to type-check this expression in reasonable time
This is one of the worst errors you can encounter while developing with Xcode. It looks like it's related to a problem inside the compiler itself: when there are lot of lines of code, it becomes unable to identify them all and start asking you to break down the code in smaller pieces. Sometimes you can, sometimes not. First of all, in your code there is FOR SURE an error, so in case of the second option, begin commenting entires sections of your code: this can lead to two options: You commented a section that contains the error: Xcode give you the preview and you check the commented section to find the error You commented enough code to let the compiler do its job, and you'll have the normal error reported in your code: again, fix it! Once errors have been fixed, normally you can uncomment what you excluded and all will go up and ok again. The most common errors that can lead to this behavior (but it's just a hint) are those involving parameters got or passed to other SwiftUI objects: parameters label (mistyped, missing, exceeding) parameters values (not $/& present, $/& present but not required) parameters types (you passed a wrong type) Well, I hope that this post could be useful to others that, like I did, are struggling a lot to understand the exact nature of this peculiar error. Code well and Prosper!
0
1
582
Oct ’24
Xcode "Build For Testing" always returning x86_64 architecture for code coverage purposes
When using Xcode's "Build for Testing", I have noticed the resulting MyApp.xctestrun file has an array of CodeCoverageBuildableInfos. This array has all of our built targets. They all have an Architectures array property. For all of our targets this is set to x86_64 when we build for Any iOS Simulator. This is irrespective of what we have "ARCHS" and "ONLY_ACTIVE_ARCH" set to (in our case we only want arm64). We do have a number of local swift packages defined, each with their own test targets. We are using a test plan for these tests. This is causing issues when processing the resulting xcresult file since it is complaining that it can't find objects for the correct architecture when calculating code coverage. No object file for requested architecture No coverage data found. (Underlying Error: No object file for requested architecture)
0
0
533
Oct ’24
Using image instead of circles in particle system
Hi all, I'm working on a particle system. Got it to work using drawn circles. Now I want to replace the circle with an image. Trying to do so in Draw section, but not sure if that's the right place. Any suggestions for coding to: connect the image from BIN to Xcode to replace particles with the image(s). Kindly ty
1
0
331
Oct ’24
dispatch/block.h not found
This is definitely a weird one -- the laptop is running macOS 12, but it's trying to build using macOS 13 SDK? (The machine cannot run anything later than macOS 12, btw.) In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.1.sdk/System/Library/Frameworks/CoreFoundation.framework/Headers/CFStream.h:20: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.1.sdk/usr/include/dispatch/dispatch.h:69:10: fatal error: 'dispatch/block.h' file not found #include <dispatch/block.h> ^~~~~~~~~~~~~~~~~~ 1 error generated. I'm trying xcode-select --install but has anyone run into this before?
1
0
321
Oct ’24
Xcode 16 used in CI gets littered with empty user accounts
We have a Mac mini running our CI with Xcode 16, and empty accounts seem to appear in it as time goes by. I haven't yet isolated which job(s) are triggering this, it slows builds down considerably, especially because any code-signing related task yields a ton of error messages like IDEDistribution: Failed to log in with account "(null)" while checking for an App Store Connect account (Error Domain=DVTServicesAccountBasedSessionErrorDomain Code=0 "Unable to log in with account 'mobile-devs@sightcall.com'." UserInfo={NSLocalizedFailureReason=Unable to log in with account 'mobile-devs@sightcall.com'., NSLocalizedRecoverySuggestion=The login details for account 'mobile-devs@sightcall.com' were rejected., DVTDeveloperAccountErrorAccount=<DVTAppleIDBasedDeveloperAccount: 0x60000169c900; username='mobile-devs@sightcall.com'>, NSUnderlyingError=0x600001e71f50 This is obviously an Xcode bug, but has anyone found a work-around somehow ?
3
0
504
Oct ’24
xcodebuild linking error fille cannot be open()ed, errno=2
I very recently migrated our project on Swift 6. After fixing every issues, mostly due to Swift Concurrency, I’m getting the following error when compiling with Xcode 16.0, which doesn’t make any sense to me : Multiple errors: file cannot be open()ed, errno=2 path=/Users/.../Library/Developer/Xcode/DerivedData/MyApp-euxwyncffackymerzuntbjccezyq/Build/Intermediates.noindex/MyApp.build/Debug-iphoneos/MyApp.build/Objects-normal/arm64/Router.o in '/Users/.../Library/Developer/Xcode/DerivedData/MyApp-euxwyncffackymerzuntbjccezyq/Build/Intermediates.noindex/MyApp.build/Debug-iphoneos/MyApp.build/Objects-normal/arm64/Router.o'; file cannot be open()ed, errno=2 path=/Users/.../Library/Developer/Xcode/DerivedData/MyApp-euxwyncffackymerzuntbjccezyq/Build/Intermediates.noindex/MyApp.build/Debug-iphoneos/MyApp.build/Objects-normal/arm64/AccountRouter.o in '/Users/.../Library/Developer/Xcode/DerivedData/MyApp-euxwyncffackymerzuntbjccezyq/Build/Intermediates.noindex/MyApp.build/Debug-iphoneos/MyApp.build/Objects-normal/arm64/AccountRouter.o'; file cannot be open()ed, errno=2 path=/Users/.../Library/Developer/Xcode/DerivedData/MyApp-euxwyncffackymerzuntbjccezyq/Build/Intermediates.noindex/MyApp.build/Debug-iphoneos/MyApp.build/Objects-normal/arm64/AlertRouter.o in '/Users/.../Library/Developer/Xcode/DerivedData/MyApp-euxwyncffackymerzuntbjccezyq/Build/Intermediates.noindex/MyApp.build/Debug-iphoneos/MyApp.build/Objects-normal/arm64/AlertRouter.o'; file cannot be open()ed, errno=2 path=/Users/.../Library/Developer/Xcode/DerivedData/MyApp-euxwyncffackymerzuntbjccezyq/Build/Intermediates.noindex/MyApp.build/Debug-iphoneos/MyApp.build/Objects-normal/arm64/AlarmRouter.o in '/Users/.../Library/Developer/Xcode/DerivedData/MyApp-euxwyncffackymerzuntbjccezyq/Build/Intermediates.noindex/MyApp.build/Debug-iphoneos/MyApp.build/Objects-normal/arm64/AlarmRouter.o' (The '…’ is just me obfuscating the real name) I’ve checked the paths. The file are here and I can open them. I tried cleaning the project, removing every derived data. I removed every dependencies (cocoapods &amp; SPM). I’m using Tuist, so I fully cleaned the project and recreated it from scratch. Then I thought it might be an issue with my Xcode installation, so I tried running the project on another machine, I still get the same error every time. Anyone has a clue on what’s happening?
12
0
1.5k
Oct ’24
How to log app termination using Xcode organizer?
In my React Native mobile application, we are experiencing app termination issues on a few devices (iPhone 13 & 14). We are not getting any logs on Xcode organizer after app termination due to memory leak or terminates by OS. Could you please suggest a way to log app terminations or recommend any other platform where we can log such events? Alternatively, do you have any suggestions on how to resolve app termination issues?
1
0
570
Oct ’24
How to log app termination on firebase?
In my React Native mobile application, we are experiencing app termination issues on a few devices (iPhone 13 & 14). We have implemented Firebase Crashlytics, we are getting crashes logs but we are not receiving any logs for app terminations when app terminates due to memory leak or terminates by OS. Could you please suggest a way to log app terminations or recommend any other platform where we can log such events? Alternatively, do you have any suggestions on how to resolve app termination issues?
0
0
476
Oct ’24
Presenting a fullscreen viewController will cause crash in TabBarController when running iOS App in Mac(Designed by iPad)
Xcode Version 16.0 (16A242d) [_NSFullScreenMenuBarCompanionController layoutTitlebarViews] last stack error :Thread 1: EXC_BAD_ACCESS (code=1, address=0x6b414b754e0) A bad access to memory terminated the process. Presenting a fullscreen viewController will cause crash in TabBarController when running iOS App in Mac(Designed by iPad) A demo gonna recreate this crash. Demo is in attachment in Feedback issue (FB15183434). Or you can try yourself. Create a TabBarController Try to present a view controller as fullscreen mode. Crash will be occurred. #warning(": Bug is here when presenting a fullscreen view controller from a tab bar managed view controller,") let vc = UIViewController() vc.modalPresentationStyle = .fullScreen present(vc, animated: true)
1
1
373
Oct ’24
When building for physical iPhone throws Command PhaseScriptExecution failed with a nonzero exit code
I developed my app with React-Native-CLI, version 0.67.2. I use Xcode 16 on MacOS Sequoia 15.0.1 It builds and runs fine on any simulator, iOS 17 or iOS 18. As soon as I build it for my iPhone 12 iOS 17.6.1 or archive, it throws this error "Command PhaseScriptExecution failed with a nonzero exit code" at the last time. It actually starts the Metro. I made my iPhone into developer mode. Paired it with MacOS. The thing I don't get why it doesn't work on my iPhone when it works fine on simulators. It doesn't even archive. Anyone encountered something like this in the past?
0
0
696
Oct ’24
ios app products are only permitted in swift playground packages error
Hello all! I am currently facing an issue where I am receiving an "ios app products are only permitted in swift playground packages" error when trying to build the app. I forked a branch from the git repo that my friend made not too long ago, yet I still can't figure out what the issue was. I can provide the repo if needed.
1
0
695
Oct ’24
iOS 18 Simulator doesn't show logs from PreviewsAgentExecutorLibrary
I was trying to debug an issue with entry point not being found on iOS 18.0 simulator and device(iPhone 14 Pro) with no success since the Xcode console output just prints No entry point found. Checked '(null)'. Later when I tried to use iOS 15.0 Simulator of iPhone 13 to see if it makes a difference, I could see more verbose messages from the loader trying to look for entry points and was able to pin point the root cause of the issue. Nothing was changed in the project settings, env variables or anything except switching to iOS 15.0 simulator from iOS 18.0 simulator, so I don't think it is environment issue or project configuration issue. The absence of detailed logging got me stuck on this issue for sometime. The same issue (minimal logging) was observed on iOS 17.4 simulator as well but is not present on iOS 15.0. iOS 18.0 Log: No entry point found. Checked '(null)' iOS 15.0 Log: 2024-10-13 13:31:17.970323+0530 SideStore[62559:1632528] [PreviewsAgentExecutorLibrary] Looking up debug dylib relative path 2024-10-13 13:31:17.970533+0530 SideStore[62559:1632528] [PreviewsAgentExecutorLibrary] Found debug dylib relative path string SideStore.debug.dylib 2024-10-13 13:31:17.970560+0530 SideStore[62559:1632528] [PreviewsAgentExecutorLibrary] Looking up debug dylib entry point name 2024-10-13 13:31:17.970583+0530 SideStore[62559:1632528] [PreviewsAgentExecutorLibrary] No debug dylib entry point name defined. 2024-10-13 13:31:17.970615+0530 SideStore[62559:1632528] [PreviewsAgentExecutorLibrary] Looking up debug dylib install name 2024-10-13 13:31:17.970646+0530 SideStore[62559:1632528] [PreviewsAgentExecutorLibrary] Found debug dylib install name string @rpath/SideStore.debug.dylib 2024-10-13 13:31:17.970672+0530 SideStore[62559:1632528] [PreviewsAgentExecutorLibrary] Looking for Previews JIT link entry point. 2024-10-13 13:31:17.971776+0530 SideStore[62559:1632528] [PreviewsAgentExecutorLibrary] No Previews JIT entry point found. 2024-10-13 13:31:17.971797+0530 SideStore[62559:1632528] [PreviewsAgentExecutorLibrary] Gave PreviewsInjection a chance to run and it returned, continuing with debug dylib. 2024-10-13 13:31:17.971816+0530 SideStore[62559:1632528] [PreviewsAgentExecutorLibrary] Looking for main entry point. 2024-10-13 13:31:17.971846+0530 SideStore[62559:1632528] [PreviewsAgentExecutorLibrary] Opening debug dylib with '@rpath/SideStore.debug.dylib' 2024-10-13 13:31:17.971935+0530 SideStore[62559:1632528] [PreviewsAgentExecutorLibrary] Debug dylib handle: 0x205c2d2a0 2024-10-13 13:31:17.971969+0530 SideStore[62559:1632528] [PreviewsAgentExecutorLibrary] No entry point found. Checking for alias. 2024-10-13 13:31:17.972368+0530 SideStore[62559:1632528] [PreviewsAgentExecutorLibrary] No alias entry point found. Falling back to look up entry point name 'main' 2024-10-13 13:31:17.972926+0530 SideStore[62559:1632528] [PreviewsAgentExecutorLibrary] No entry point found. Checked '(null)' Questions: What is the difference between iOS 15 and > iOS 17.4 Is this a bug or expected behavior? if so how do I get back logging as in iOS 15.0 on iOS 18.0 (need detailed logging from the loader) which exact version of IOS was this change/bug got introduced?
1
3
1.4k
Oct ’24
The file couldn’t be opened in Xcode
I've completed my Environment setup for React Native but when I open my project in Xcode and click on left side folder i.e my project, an alert message appeared and says "The file couldn’t be opened." I'm using MacBook 2016 Pro and Mac Os is Monterey 12.7.6 and Xcode version is 14.0 (14A309). i also tried Xcode 14.2 but face same issue.
0
0
239
Oct ’24
iOS 18 features not working in Xcode iOS playground
When I create a new iOS playground in Xcode 16.0 with an iOS 18.0 SDK installed, I cannot use some of the new features such as the new way for programming tab layouts. When I just use an Xcode project, these features work as expected. In a playground, I get errors saying "x is only available in iOS 18.0 and later". I have noticed this for more than just this feature. Is there some way I can force the playground to run with iOS 18 as I have the appropriate SDKs installed?
0
2
547
Oct ’24
Xcodecloud Xcodebuild Failed With Exit Code 70
I'm running on xcode 16, the project archives just fine on the local machine. However, with xcodecloud. It's running into exist code 70 on the following command xcodebuild -exportArchive -archivePath ..... #output Showing All Errors Only Build Archive Export archive for ad-hoc distribution Command exited with non-zero exit-code: 70 Command exited with non-zero exit-code: 70 Export archive for development distribution Command exited with non-zero exit-code: 70 Command exited with non-zero exit-code: 70 Export archive for app-store distribution Command exited with non-zero exit-code: 70 Command exited with non-zero exit-code: 70
6
1
3.4k
Nov ’24
Cannot download basic app from testflight
Hi, I have made a very simple app (an app that shows "hello world" in a text field). But when I upload it to testflight I cannot download the app on my Iphone. I have the newest version of macOS (15.0.1 macOS Sequoia) and the newest ios version (ios 18.0.1). I have tried to change the name of the app, the change the bundle identifier, tried to change my certificates in the apple developer page, trying to delete testflight, restarting my phone and more. But it doesn't help. I will add that I cannot add external testers to my app in testflight (I also get an issue here). But for some reason I am able add internal testers (but the invitees cannot download the app in testflight) As written above, I just uploaded the most basic app to testflight and I still cannot download it on my phone (I have also tried to invite other testers and still doesn't work on their phone). I have had this issue the last year, and I have tried almost every solution I could find on the apple developer page, the internet and more. It would really help with a solution to this problem. Pls write a solution.
0
0
345
Oct ’24
Issue while adding App to Archive
CodeSign /Users/abc007/Library/Developer/Xcode/DerivedData/App-fjztkcxqsstohgfvqdfnedgpwltj/Build/Intermediates.noindex/ArchiveIntermediates/App/InstallationBuildProductsLocation/Applications/App.app (in target 'App' from project 'App') cd /Users/abc007/Documents/WorkSpace/RegulusIT/Release_Oct_2024/UI\ Backup/ios/App Signing Identity: "Apple Development: Yatin Ghat (JS84GYN3O4)" Provisioning Profile: "iOS Team Provisioning Profile: www.rightschool.net" (bdc0759d-b9d0-4470-8e3f-b5b67d3c2586) /usr/bin/codesign --force --sign 82C0E5904219E333688CE627A21522F732446038 --entitlements /Users/abc007/Library/Developer/Xcode/DerivedData/App-fjztkcxqsstohgfvqdfnedgpwltj/Build/Intermediates.noindex/ArchiveIntermediates/App/IntermediateBuildFilesPath/App.build/Release-iphoneos/App.build/App.app.xcent --generate-entitlement-der /Users/abc007/Library/Developer/Xcode/DerivedData/App-fjztkcxqsstohgfvqdfnedgpwltj/Build/Intermediates.noindex/ArchiveIntermediates/App/InstallationBuildProductsLocation/Applications/App.app /Users/abc007/Library/Developer/Xcode/DerivedData/App-fjztkcxqsstohgfvqdfnedgpwltj/Build/Intermediates.noindex/ArchiveIntermediates/App/InstallationBuildProductsLocation/Applications/App.app: errSecInternalComponent Command CodeSign failed with a nonzero exit code
1
0
500
Oct ’24