“xcode github”

Ok, here's what happened. To open the project in XCode 11 I had to convert Swift from 3.x to 4.x. When I made some manual changes to add the @objc tag, I errantly added it to a few private functions in the code. I'm guessing the 'out of range' message meant 'hey, we can't see those functions you idiot.I removed it and now builds fine on all devices & ios versions.Hopefully this helps someone in he future...

@DTS Engineer Having the same problem here: building an app on Xcode 16.0 on macOS Sonoma 14.7 results in an application that crashes on macOS Big Sur Intel machine with the same crash as mentioned above. Building with Xcode 15.4 does not have this issue. However, we cannot build this branch on Xcode 15.x anymore due to code changes for Xcode 16 compatibility. Is there a workaround? We're now stuck in an unreleasable state!

I also create GitHub sample project, which is shown a problem GitHub project - https://github.com/ChoadPet/NWListenerTest/tree/master

I use Source Control for this. My Xcode project is synced to my remote repository. A second machine can then pull the project from the remote repository. Either machine can work on the project, and push the changes. Remote accounts are available on GitHub, GitLab, Bitbucket, etc...

I used x code 7.1.1 and am on mac OS X Yosemite

Was able to solve the problem. This problem was caused by macOS 15.0, which I already installed. It did not matter, which xCode version I used. So I organized a cloud access to a Mac (with macOS Sonoma and xCode 15.4) (https://www.macincloud.com), cloned the project from GitHub and archived and sent it to Apple Store connect again. Now, was able to send it to Apple to check it.

@Paradigm777 Hi. I’ve checked everything and still get error. I’m starting to think the error resides in how I set up everything (I don’t know much about git but I’m currently learning about it) At first I didn’t set any repository or whatever. I added my account in Xcode settings (with a token). I clicked on « add a git repository » which I searched in the help research bar. After that, in the source control panel, I went to remotes, and clicked « add a new remote« which made the repository appear on my GitHub. i still had the untracked message. Do you notice anything wrong ? Was I supposed to set a local repository too ? Should I have first created the repository on GitHub then push the changes from Xcode project to it ?

I have a pure Objective-C project and I also get the XCode crash on every other build. (It is actually the second build because the crash puts one back at first build.) At least my code changes are saved! It appears to be one of the final seven or eight steps in the build process counter. These crashes happen whether or not the device is hardware or simulator, iOS 17.4 or 16.x or 15.x, etc.

I'm seeing exactly the same thing in Xcode 7 Beta 5. In my project this usually happens when I am editing Swift source such as: print(x = (x.somefunc()))The editor looses functionality pretty consistently as I type the x.. Everything compiles without issue but it is annoying to loose the code completion and keep having the window jerk up and down when the report problem appears.I couldn't find any crash logs anywhere.

I recommend you'd give a better title for your post. Including the error message is one way, if it's not too long.And you also show what version of Xcode you are using, just adding something like Xcode 6.4 on OS X 10.10.4 would be useful in many cases.I assume this sort of lines: /may be modified by the article editor's copying feature and your original code would be something like this: // Do any additional setup after loading the view, typically from a nib.as in the code template generated by Xcode. You'd better post-edit your code after pasting it.So, if I try to get the message Expected declaration, I need to write some other codes, other than your code shown above.Are you sure your source file does not contain any other codes?

HelloYou need tell to xcode what isthe version of iOS your code will be compiled, so if you put iOS9, Your app will not work in users devices because today the oficial version is 8.4. You can test in iOS9, but must be marked iOS 8.x to publish.

You can do all three without a Mac, but they're separate problems and no single tool covers them. Build and test. The Xcode toolchain only runs on macOS, so something has to run it for you. We use mac.doublespeed.ai (disclosure: Iwork there). It's a fleet of Mac minis behind an API. From Linux or Windows you install a CLI (npm i -g @doublespeed/ds), then ds xcode build . / ds xcode test . uploads your project, runs xcodebuild on a Mac, and streams the result back; ds xcode run . boots the app in an iOS Simulator and gives you a browser link to interact with it. It works with React Native, Expo and CocoaPods projects as well as native Swift. Billing is per second of Mac time, and there's a GitHub Action so the same build/test runs as a PR check from an ordinary Linux runner. Published timings vs GitHub-hosted macOS runners are at mac.doublespeed.ai/benchmark.

The provisioning profile is located in your keychain so is not part of the project.As for gitignore, I use the Objective C template located on github at github.com/github/gitignore.