“xcode github”

Thanks Matt. I have a pared down sample project that demonstrates the condition. I am going to submit a TSI this morning. I will have a private repo on github containing the project. Can you give me a github username to invite for access to the repo?

I should have written it clearly, but `recently` meant Swift 1.2 (comes with Xcode 6.3) and after.Till Swift 1.1, I used something like this:class UserInfo { class var sharedInfo: UserInfo { struct My { static var instance = UserInfo() } return My.instance } var userFirstName: String? var userLastName: String? }(Sorry, I removed all Xcode 6.1.x installations, and I cannot check if the above code actually works in Xcode 6.1.1 .)If you don't have some specific reasons, you'd better upgrade your Xcode.

First, thanks for re-posting. Second, I’m going to drop a link to Unicode Technical Standard #35 Unicode Locale Data Markup Language (LDML) Part 4: Dates, just for the benefit of Future Quinn™. Third, I apologise in advance for harping on about the old API, but you’ll understand why in a second. You wrote: I could use formatter.setLocalizedDateFormatFromTemplate(isTwentyFourHourClock ? HHmm : hhmm) Unfortunately that doesn’t work, even for ‘simple’ cases like US English. Consider the code at the end of this post. Put that code into a test app and run it on an device. Now configure your device as follows: Set Settings > General > Language & Region > Region to United States. Set Settings > General > Date & Time > 24-Hour Time to On. Now run the code. It prints this: locale: en_US (current) format: X .standard X .preferred X .force12Hour X .force24Hour X AM: X 09:42 X 09:42 X 09:42 X

Hello @mauri870. Thanks for reporting this issue regarding SharedWorker in WKWebView on iOS 16.1, and for the bug report. While our engineers work on a long-term solution, the suggested workaround is to disable SharedWorkers for the web site you're loading. You can either do this in your web source, if you control it, or in your native app, if you are loading arbitrary web sites. As an example, the sample code in Code Listing 1 disables SharedWorkers when loading a page in WKWebView, by injecting a script using WKUserScript. Code Listing 1. func makeViewConfiguration() -> WKWebViewConfiguration { let configuration = WKWebViewConfiguration() let dropSharedWorkersScript = WKUserScript(source: delete window.SharedWorker;, injectionTime: WKUserScriptInjectionTime.atDocumentStart, forMainFrameOnly: false) configuration.userContentController.addUserScript(dropSharedWorkersScript) return configuration } var view = WKWebView(frame: CGRect(x: 0, y: 0, width: 400, height: 400), co

Found this ; they mention OmniGraffle, but it seems to have limitsanda freeware (github, so you could customize):h ttps://stackoverflow.com/questions/29186136/uml-class-diagrams-for-xcode-swift-programmingEditedI tested, it's very interesting ; clearly, the set up on the page could be improved (up to us to improve the freeware), but a very good starting point.

Hi @edford, I am experimenting with adding custom modifications to the default toolchain. I expect the local build of the apple-llvm toolchain to behave the same as the pre-built toolchain that’s included in Xcode. Right now there’s a difference between the two, and I am not sure whether I missed anything. So, Is there any difference between the toolchain on Apple’s Github and the one came with Xcode? Or is there anything specific that I have to pay attention to when I try to build the toolchain locally?

You need to generate a new key since the one Xcode auto-generates is not supported... ssh-keygen -t ecdsa -C our_email pbcopy < ~/.ssh/id_ecdsa.pub Go to https://github.com/settings/ssh/new, paste the key and save. Go to Xcode -> Preferences -> Sign into the github account if not already. Select SSH for Clone using For SSH Key select id_ecdsa.

You can add support for iOS 14.5 (and watchOS 7.4) by copying the relevant DeviceSupport folders from Xcode 12.5 to Xcode 12.4. For example the one for iOS 14.5 is located at is Xcode.app/Contents/Developer/iPhoneOS.platform/DeviceSupport/14.5 You can download the xip for Xcode 12.5 from here: https://developer.apple.com/download/more/?=xcode and extract that folder from the XCode.app inside it and move it to your installed XCode.app. There are also publicly hosted GitHub repositories with these folders, a quick search will turn them up. It is obviously better to extract it from the official source yourself, but I think the archives are signed anyways.

>it's pretty straightforward to just use git and ssh on the server. I never used the xcode server option for it - are you really losing anything (besides time having to set up something new)? I have a ton of self hosted git repositories set up on my Xcode Server and having to set up remotes elsewhere or to configure them from the command line is a a time consuming task. Just a coulple clicks in the GUI was pretty nice.>But I am sincerely curious. Mostly just want to encourage you to look into setting it up yourself as a git+ssh type thing before you feel like you have no option besides switching to paid setup.Paying Github to host private repositories was never going to happen from me. But don't kid yourself, they made a deal with them for this integrated setup in Xcode 9 and money was involved. Self-hosting repositories is an easy way to not pay Github, so I bet they agreed with them to remove the feature in exchange for that open in xcode stuff on

This is not github

Thanks for your answer.Yes it is an iPad mini 2 - forgot to add the number at the end. The error I get consistently, both in the simulator and on the device is EXC_BAD_ACCESS at line 38 of ViewController.swift for Thread 1 with code=1, address = 0x0. I am running OS X v 10.11.5. I should say that I have both Xcode 7.3.1 and Xcode 8 beta installed. Since this error seems to be uncommon, I'll try a fresh install.

I tried the code you last posted in new project (both Xcode 8.3.3 and Xcode 9, Swift 3.x and 4) and it works fine. At this point, I'd say the problem is not the ExamineError declaration, but something else is going wrong in your project. If you're using a current version of Xcode, I'd suggest you submit a bug report and see what comes back.Incidentally, just for interest, you could try:catch { let e = error as! ExamineError print (type(of: e)) }and see what it says.

I have the exact same issue. Any help would be greatly appreciated!If it''s of any help, my Xcode crash log is overe here gist [dot] github [dot] com [slash] thomax [slash] b338a8d02fb0c230fb1ec8e6cda41be9. Sorry for mangling that URL, but it seems the only way to avoid the moderation flag, and moderation around here seems to take a while.

Is it possible to share it on github?