xcode github

This is also happening for me, both projects downloaded from GitHub using Xcode's Clone... menu item as well as directly from the command line in Terminal.

I'm in the same situation. I'm working on finishing up my first app for iOS 13 and have wondered about what is supposed to be done with a new iOS comes out. This is answering some questions, but I'm not familiar with git (I assume GitHub) or branches of code. Can anyone point me in the direction of how to use GitHub with Xcode? And how to branch code... :D

You can make your app work on 8 and 9, but it will take more work. You won't be able to submit the app from Xcode 7 until shortly before iOS 9 is released. You can install Xcode 6.4, target iOS 8, and submit to the store now. But, this almost certainly means you will have to make some code changes (especially if you used Swift) and do some testing on the 8.x simulators and some devices that still have 8.x on them. Or, if you want to wait to submit the app until it is possible to do so from Xcode 7, you can set your project's deployment target to iOS 8.x, and again, modify your code and test on iOS 8 simulators/devices. There are several ways to handle things that are different or missing in different iOS versions, such as the if #available statement (Swift), comparing NSFoundationVersionNumber, testing respondsToSelector, or testing the result of NSClassFromString().EDIT: Changed ... project to target iOS 8.x... to ... project's

Hi guysI have been having the same problems, along with many other xcode problems. I am wondering if it is specific to a type of computer. I am running a late 2015 iMac. Could you all put down what computer you are using.For info, I have been having various major problems with all versions of x code since I started using it about 9 months ago. So it has included 9.0 - 9.3, and all the macOs updates since then. See my posts under 'X code 9.3 Multiple problems' and 'Multiple problems with x code, is it the Mac?'ThanksGeoff

Hi, My app only runs on iOS 10 and higher so I cant test on iOS 9. However I do not think its an iOS version issue. The simulator bug occurs even if I use iOS 10.x in the simulator instead of iOS 11.x. And the same code worked perfectly in XCode 8.x

@Michaelrowe01, Please review and apply the instructions in Grant Xcode Cloud access to your source code and Resolve GitHub Enterprise connection issues.

Apple can make XCode Light or XCode for iOS. Like MS make Visual Studio for OS X. But it's based on Github Atom, instead rewrite Win32 app.

App submissions tend to be about the code submitted, not the OS that generated it. XCode is the focus here and the store rejects any code that comes from Beta XCode version (having done that by mistake more than once,). Im not sure they care about the OS part, as it doesnt leave trails in the code that seem to care about. Today you can submit on a range of OS X versions, basically anything that runs XCode 6.x and meets the other code requriements.In the past they have always had both a GM version of XCode for each OS beta, to support submissions and other testing. With XCode7, I have not seen the normal words about no submittal using the beta that normally is there. Maybe its there and I just missed it. Do we know for sure that current XCode7 cant be used for submission?

Yes. See the final section of this page of documentation: In Xcode 13 and later, you can create, view, and comment on PRs, and merge changes into your codebase if you host your Git repository with Bitbucket Server, GitHub, or GitHub Enterprise. You can also configure Xcode Cloud to detect new PRs, or changes to an existing PR. When it detects a change, Xcode Cloud merges the involved branches in a temporary build environment, and automatically builds your project and runs your tests to verify the merged code. After verifying the changes, Xcode Cloud adds a status message to the PR to inform you of the result.

This is probably due to the fact that Xcode tries to download the zip file, specified by the url, without knowning that it's an attached file at a private github repository, and does't add the personal access token in the headers. As a result: 404 file not found. The exact same logic is working on a publicly accessed github repository.

I tried your code with Xcode 12.5.1 and it shows the same error. And trying with Xcode 13.1, it compiles without any problems. I'm not sure what is causing this issue, but until the problem is solved, you may need to use Xcode 13.x .

I did try out your php solution in github on my Mac OS X (El Capitan) using the default apache server and the php modules that shipped with Mac OS X. I couldn't get it to work because of the following:executing apple_pay_comm.php with &u=https://apple-pay-gateway-cert.apple.com/paymentservices/startSession{curlError:SSL: Can't load the certificate /Library/WebServer/Documents/applepay/applepay_includes/ApplePay.crt.pem and its private key: OSStatus -61}I looked up the curl issue of OSStatus -61 and it led me to https://coderwall.com/p/h3zzrw/using-client-ssl-certificates-for-php-curl-requests-on-osxIn the end, I couldn't get your php server code to make a HTTP post request to apple's web servers (production or sandbox).