When I opened my project for the first time in Xcode 7, I was given the option to convert all of my code to Swift 2, which I did. But my WatchApp was never updated to WatchOS2. Now when I try to change the Base SDK, Xcode just crashes on me. Is there any other way to migrate my WatchApp and WatchKitExtension to WatchOS 2?
Search results for
xcode github
91,977 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
I host repositories on GitHub. I've noticed as of the 7 beta, the UI to authenticate is disabled. As a result I can't get any authentication settings into or out of XCS, so XCS can't access my repositories.http://i.imgur.com/Ilpjgqx.pngI've looked briefly through the XCS logs trying to understand what's going on here and there's nothing obvious.See also rdar://21334520
I am running into this problem: UI testing on MDM device. I can use the UI test to open the app and enroll, but I am not able to automate once the app went to safari to download the MDM profile or go to settings to install the profile. Is there any way I can manage to automate this whole MDM enrollment process?
That is what I'll try at first. We'll see what the bridging brings with the new Xcode 7 and Swift 2. I never tried it with earlier versions but it didn't look to be very seamless.Thanks/Peter
Topic:
Programming Languages
SubTopic:
Swift
Tags:
I have the same question. I still have the mentality of my computer as a digital hub, and also I like to keep backups of all of my apps for whichever devices they ultimately are destined for.In the WWDC talk there was a mention of Xcode Server being able to keep a complete copy of the app and doing the thinning locally. Perhaps the same functionality could be built into a future version of iTunes? I would think that iTunes would *have* to get a complete copy of each app, otherwise how would the store know which versions it will need to send? If I connect a new device to my Mac, I really would hate to have to fetch new copies of all of my apps...Of course the App Store would still have to do the compiling of all versions to send to iTunes, since the new upload format is some kind of bytecode (as I understand it). And I doubt *that* functionality would be added to iTunes.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
Good Day,Are they just not available yet?Or, I'm missing a setting or a tech note, but with Xcode 6.3.2 whenever I switch a project's settings ( iOS Deployment Target drop down ) to 8.3, all the simulatorsgo away and my current App scheme only has 1 value available iOS Device.Thanks!AdamThis was posted originally on 5/30 but now archived in the old forum.
The first step is probably to go to the Product menu in your project in Xcode and hold down the option key and choose Clean Build Folder..., to make sure there isn't any previously compiled code causing problems because of incompatibility.I don't think upgrading OS X to the El Capitan would improve anything for you, since a lot of us are just running Xcode 7 beta on Yosemite.If you haven't already backed up your project, you might want to do that before updating the code further, just in case you end up deciding to go back and wait.Assuming there isn't isn't anything really weird going on with your project, you would just need to work your way through it fixing the errors and warnings generated by the compiler. There can be a lot of new errors and warnings because of the changes between Swift 1.2 and 2 and the updates to Cocoa, but most of the errors and warnings should be relatively trivial to fix (changing var to let, updating the old generic sort/map/filter/find
Topic:
App & System Services
SubTopic:
Core OS
Tags:
The error message isThe iOS 8.2 simulator runtime is not available.Unable to open liblaunch_sim.dylib. Try reinstalling Xcode or the simulator runtime.I've checked XCode preferencaes -> download tab and it seems that extra simulators can not be installed.
I've always used beta versions of Xcode in the past during development and it was fine as long as I built the app for submission with the currently released version of Xcode. The real issue here is the forced Swift upgrade.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
Thanks for the idea but I'd actually just like to stick with the current version of Swift for now until closer to iOS 9/Swift 2.0 release. From what I can see online this isn't possible - Swift version is tied to Xcode and you can't run an older version.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
Same problem here. I managed to upgrade to 10.11 but cannot get the link to Xcode download or iOS 9 install. Dropped onto profile page too.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
They did, however, promise binary compatibility so I'm sure they could find a way to allow you to keep using Swift 1.2 in Xcode 7.It's a little disappointing that I won't be able to test the new APIs in iOS9 or take advantage of improvements to LLDB until this all goes stable already, at which point my feedback has much less impact.
Topic:
Programming Languages
SubTopic:
Swift
Tags:
With the newest releases of iOS and iTunesConnect, Apple is more and more restrictive about what´s happening in your CFBundleVersion of your Extensions.I tried to fiddle around with Run Script Build Phases, such as this:#!/bin/sh INFOPLIST_EXT=${TARGET_BUILD_DIR}/${INFOPLIST_PATH} echo Extension writing to $INFOPLIST_EXT PLISTCMD=Set :CFBundleVersion $(git rev-list --all|wc -l) echo -n $INFOPLIST_EXT | xargs -0 /usr/libexec/PlistBuddy -c $PLISTCMDHowever, this seems to work for some types of Extensions (WatchKit), but for some others it doesn´t (Today Widget). In my cases, I seem to access the $TARGET_BUILD_DIR before there´s content in it. Using $BUILT_PRODUCTS_DIR delivers the same error.Extension writing to /Users/marc/Library/Developer/Xcode/DerivedData/MyApp-focpnqzzpnqsfyaqwwocwpujmhmh/Build/Intermediates/ArchiveIntermediates/MyApp/IntermediateBuildFilesPath/UninstalledProducts/TopNewsWidget.appex/Info.plist Set: Entry, :CFBundleVersion, Does Not Exist File Doesn't Exist, Will Create: /Users/m
Hi,just wondering if the console output has been removed in playgrounds 7?A console panel is available for print() statements in playgrounds 6 when displaying assistant editor, but nothing shows up in (xcode) playgrounds 7. Is this a beta bug or have console panels been deprecated?.-nick
Nothing works. Upgraded to xcode 6.3.2 and now it shows Error Fetching Developer Info..Anybody have similar issues ?
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags: