Search results for

Xcode

92,304 results found

Post

Replies

Boosts

Views

Activity

Abort trap: 6
I'm getting an Abort Trap: 6 after bringing in over a project from XCode 6.3. Here's what I'm getting in 7.0:CompileSwift normal x86_64 /Users/mike/Cocoa/BitBucket/bassoon-fingerings-3.0/Bassoon Fingerings/MusicStaffView/MusicStaffViewElementLayer.swift cd /Users/mike/Cocoa/BitBucket/bassoon-fingerings-3.0 /Applications/Xcode-beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift -frontend -c /Users/mike/Cocoa/BitBucket/bassoon-fingerings-3.0/Bassoon Fingerings/MusicStaffView/MusicStaffViewElement.swift /Users/mike/Cocoa/BitBucket/bassoon-fingerings-3.0/Bassoon Fingerings/MusicStaffView/MusicStaffView.swift /Users/mike/Cocoa/BitBucket/bassoon-fingerings-3.0/Bassoon Fingerings/NotePickerViewController.swift /Users/mike/Cocoa/BitBucket/bassoon-fingerings-3.0/Bassoon Fingerings/FingeringViewController.swift -primary-file /Users/mike/Cocoa/BitBucket/bassoon-fingerings-3.0/Bassoon Fingerings/MusicStaffView/MusicStaffViewElementLayer.swift /Users/mike/Cocoa/BitBucket/bassoon
10
0
4.3k
Jun ’15
Reply to Viewing console log for Apple Watch
I don't know if there's an easier way, but I found an iPhone app called System Console that displays all log messages from both iPhone and WatchKit apps. Even if there's a way to do it in XCode, the System Console app displays the log messages in real time in a relatively non-envasive manner (Disclaimer: I have no connection to System Console or its authors).
Topic: App & System Services SubTopic: Core OS Tags:
Jun ’15
Free Provisioning failing
So, I downloaded Xcode 7 and installed it to be able to use free provisioning to test my app on an iPhone running iOS 8.3 before subscribing to the developer program. Connecting my iPhone, I see it in the toolbar and on the device list in Devices window.I also added my Apple ID in the Preferences' Accounts Tab and it shows Free under iOS and Mac next to my name. Nevertheless when hitting the play/build-and-run button Xcode at first starts building the app but before transferring, I guess, it stops and tells me it was Unable to find a team with the given Team ID '<My ID>' to which you belong. Please contact Apple Developer Program Support. https://developer.apple.com/support, any suggestions what to do?I removed and added my account several times, getting the same message all of the times.
2
0
1.2k
Jun ’15
Reply to app won't run
I think the problem lies in that it takes a very long time to install the apps. 5+ minutes for me for simple apps.What I end up doing that works for me is Build/run the iPhone app from Xcode to deploy itStop debugging the app in XcodeMake sure Show App on Apple Watch is enabled for my app in the Apple Watch app on the iPhoneSwitch to the Watch and wait untill the new version of the app is installed (takes forever)Manually launch the app.For the most part I do the same using the Simulator as the install is instant.
Topic: App & System Services SubTopic: Core OS Tags:
Jun ’15
Reply to Xcode 7 crashes when trying to select the Main.storyboard.
Actually, I think the IBOutlets and actions have always shown as being unlinked until the storyboard is selected once. I hope that a number of other people discover that they have this problem too. Maybe it will push Apple to take a quick look at it.By the way, I noticed that the 'Crustacean' playground also causes Xcode to quit when I try to open the console to see the graphics.
Jun ’15
Xcode 7 crashes on startup
I've downloaded the .dmg, copied to Applications, waited for the verification - said 'open' once the verification is done then Xcode crashes. I'm running 10.10.3 which I think should work. I've tried uninstalling, re-downloading and re-doing the process with not luck. Has anyone else encountered this problem? Thanks.This is the error:Process: Xcode [396]Path: /Applications/Xcode-beta.app/Contents/MacOS/XcodeIdentifier: com.apple.dt.XcodeVersion: 7.0 (8123.26)Build Info: IDEFrameworks-8123026000000000~7Code Type: X86-64 (Native)Parent Process: ??? [1]Responsible: Xcode [396]User ID: 501Date/Time: 2015-06-10 17:25:29.684 -0400OS Version: Mac OS X 10.10.3 (14D136)Report Version: 11Anonymous UUID: A4A041F0-414B-EB94-4B70-43B0C8715464Time Awake Since Boot: 320 secondsCrashed Thread: 0 Dispatch queue: com.apple.main-threadException Type: EXC_CRASH (SIGABRT)Exception Codes: 0x0000000000000000, 0x0000000000000000Application Specific Information:ProductBuildVersion
6
0
2.0k
Jun ’15
IOS App Install Fail Over The Air
Hi, I'm using Xcode6 and created a test app for ipad. It compiles and runs fine in simulator. My next step is to distribute it using adhoc distribution mechanism. Here is what I've done1. Using Keychain Access to create a public/private key pair.2. Load it up into Developer Center to create a certificate, then download it.3. Add my ipad UUID under Devices.4. Create a adhoc provisioning profile by including my ipad in it, I only have one device in Member Center. Let's call the provision MyProv.5. Run the .cer file by double clicking it.6. Download the .mobileprovision file from Member Center to desktop. Then double click it.Now, in Xcode, under Build Setting, I change Provisioning Profile Debug and Release entry to point to MyProv, then run Product->Archive. When archiving the app, Xcode as me if I want to use my key created in step 1 above to sign the bundle. I allow it. I also choose to Save for ad hoc distribution when asked. In the summary page, I can see the Provisioning Profile colum
2
0
1.7k
Jun ’15
Reply to Strong reference cycle in a closure
If you add a bit of code and run it in a playground (Xcode 7 beta):class C { var m: () -> () = {} let identity: String init?(_ name: String) { identity = name print(init (identity)) } deinit { self.m() print(deinit (identity)) } } var ci = C(a) ci!.m = { var text = reference = (ci!.identity) print(text) } ci = C(b)when ci.m is run in deinit, it actually prints out reference = b even though it is deallocating a.The closure is actually capturing a reference to the local variable c1, not a reference to the instance that c1 is pointing to at the time. So no strong reference cycle is created.
Topic: Programming Languages SubTopic: Swift Tags:
Jun ’15