If I go through the new project wizard, or try to open an existing project, I get the same crash every time. It's something from XCSService, and I see keychain mentioned, so I tried relaunching keychain accessing, restarting my machine, etc. Keeps happening. Any workaround?Process: Xcode [516]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 [516]User ID: 501Date/Time: 2015-06-11 16:20:14.544 -0400OS Version: Mac OS X 10.10.3 (14D136)Report Version: 11Anonymous UUID: A12E8E79-DAD1-FC5C-0724-7549D29029DATime Awake Since Boot: 200 secondsCrashed Thread: 0 Dispatch queue: com.apple.main-threadException Type: EXC_BAD_ACCESS (SIGSEGV)Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000VM Regions Near 0:--> __TEXT 00000001088e6000-00000001088e7000 [ 4K] r-x/rwx SM=COW /Applications/Xcode-beta.app/Contents/MacOS/XcodeApplication Sp
Search results for
build disappears
49,245 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Hi,I use a 3rd party/open source framework. I embedded its project in my main app's project, and I set my main app to be dependent on it. I can build, deploy and run my app in the test device using developers profile in xcode. The problem is when I try to build it from command line for distribution. I tried passing the adhoc cert and adhoc provisioning profile as parameters. It is complaining that the bundleId of the framework is different than the one defined in the provisioning profile. Which is obviously true because the bundleId of the framework is pre-defined by its developer.I use this command to build it:xcodebuild build -workspace <my wrkspace> -scheme <scheme> CODE_SIGN_IDENTITY=<identity name> PROVISONING_PROFILE=<provisioning name>CODE_SIGNING_REQUIRED=“YES” CONFIGURATION_BUILD_DIR=<path>The options that I can think of:1. Change the bundleid of the framework to match my app bundleid2. Do not sign when building, but pass the
Cannot download beta get the following:OS X v10.11 Developer betaPRE-RELEASEThis is a pre-release OS X v10.11 update.This download requires Apple Developer Program membership. Learn moreBuildBut I am a developer?
I am building an application and would like users to see their list of Facebook friends so they can see who is already using my application and add them to their contacts and be able to invite their friends that aren't using the application yet. I know that by default I get access to users friends that are using my application. Is there a way to get access to the rest so that the user is able to invite them to use the app?
I compiled my application (which targets 10.9 as minimum) with 10.11 SDK, but when I run it on a 10.10 machine, I get:dyld: lazy symbol binding failed: Symbol not found: _AudioUnitInitialize Referenced from: /Users/josh/Documents/depot/UE4/Engine/Binaries/Mac/UE4Editor.app/Contents/MacOS/UE4Editor-CoreAudio.dylib Expected in: /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox dyld: Symbol not found: _AudioUnitInitialize Referenced from: /Users/josh/Documents/depot/UE4/Engine/Binaries/Mac/UE4Editor.app/Contents/MacOS/UE4Editor-CoreAudio.dylib Expected in: /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolboxThe headers in 10.10 and 10.11 look the same, so I can't figure out why it wouldn't be able to find the function in 10.10 frameworks. Has anyone else seen anything like this?It's only an issue building on 10.11 and running on 10.10. Other configurations work fine.
Trying to implement the new menstrual flow object type in HealthKit, but getting an error when creating the sample. I coded it myself first, but it also fails with the code from WWDC 2015 session 203 video (about 11:24) below: let dict = [HKMetadataKeyMenstrualCycleStart: true] let type = HKCategoryType.categoryTypeForIdentifier(HKCategoryTypeIdentifierMenstrualFlow)! let value = HKCategoryValueMenstrualFlow.Medium.rawValue let date = NSDate() let sample = HKCategorySample(type: type, value: value, startDate: date, endDate: date, metadata: dict)This builds, but running results in the following on line 5 above:+[_TtCSs29_NativeDictionaryStorageOwner000000011941B4B0 hk_acceptsMetadataValue:]: unrecognized selector sent to class 0x11941b4b0Without the metadata dictionary, it complains at runtime that the specified key must be set in metadata. Either I'm missing something obvious and will have a big facepalm, or it'll likely be fixed in a beta++, but if anyone has better luck, please share.
Hello,I just installed Xcode 7.0 beta. In the Xcode 7 Simulator, when I go to Hardware (menu) -> External Displays I no longer see the options for Apple Watch - 38 mm or Apple Watch - 42 mm. They have disappeared!Instead, I only see options such as:640 x 480720 x 4801024 x 7681280 x 7201920 x 1080How do I get the Apple Watch external display options back?Thank you
Ok, I've got it sort of narrowed down. I setup a new user on my machine, checked out the source, and opened it with Xcode. No problems.Then I went to build and run, and hit the you don't have a profile, import one or revoke and re-issue dialog. So, I exported the profile from my regular user login, and imported it in the new user. Boom. Shortly all the ?s were showing up on my source files just like on my regular user login. So it's got something to do with whatever was imported. When I exported, I was surprised to find that it exported 4 accounts - not just the one I was expecting, so there must be something funky in one of those accounts.From my usual login, I had previously tried deleting all the accounts (under Xcode->Preferences->Accounts), to no avail. So I've a clue where the problem lies, but still no idea how to fix it easily (and I'm not counting having to create a new account as easy!).
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
This is a known issue in the Xcode 7 beta.To work around this issue for now, please:Delete all references to .tbd files from either your linked libraries phase, or from the copied bundle resources phase (where they sometimes will be added).Add the library you want to link manually to the Other Linker Flags build settings, by adding the argument: -l<library_name> for each library you want to link (for example, add -lsqlite3 (without quotes)).For those who are curious, the .tbd files are new text-based stub libraries, that provide a much more compact version of the stub libraries for use in the SDK, and help to significantly reduce its download size.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
ENABLE_TESTABILITY = YESis set to YES in debug, not in release, but if I have a scheme that compiles a release build of my framework (who also build the test target) build will fail with'Module was not compiled for testing' when using @testablein release mode ENABLE-TESTABILITY is set the NOcaused by @testable import inside test target@testable import Awesomekit
So I just downloaded Xcode 7 and start playing with Swift 2I use one of my previous project and also a playground for testing new syntaxes.However I get into trouble when I use this line of code to fetch raw data from an free online apilet dataSource = NSData(contentsOfURL: NSURL(string: http://api.openweathermap.org/data/2.5/weather?id=5375480)!)Inside playground, the code ran perfect and I get excactly what I what.However I got nil for the dataSource everytime when I build the App on iOS 9b1 or either simulator, since the class is excactly same, I just can't understant why this happened.I try the product I built from my previous project using Xcode 6.3.2 with Swift 1.2 Syntax which is running on the same iPhone with iOS 9b1, I still get perfect result back, therefore it shows that it's nothing to do with hardware settings or API problems.Since I'm not sure if either I have missed something is important or it just an other early-pre-release bug cause this problem, please let me know if you found my
Because constructing NSErrors—and, more importantly, building up error domains and codes—was tremendously awkward in Swift 1. I did it a few times, and although you could get some reasonably elegant things going if you tried, it was always a boilerplate-filled chore. If ErrorType can do what I need it to do, it's a tremendously better solution than the old way.
Topic:
Programming Languages
SubTopic:
Swift
Tags:
I have the same problem but only when building for the simulator, if you make your target an actual device xcode seems to use these .tbd files correctly
Topic:
App & System Services
SubTopic:
Core OS
Tags:
We do general Unix development on Mac OS X but because some of the libaries we link against are currently on 32 bit we have to produce 32 bit binaries.When using Xcode 6 we can debug Unix binaries by selecting My Mac (32-bit) in the scheme selector, on Xcode 7 we only get My Mac and it gives the error: the specified architecture 'x86_64' is not compatible with 'i386-apple-macosx' in '/usr/atc-5.00.5/dev/cust0400/xcust'.I don't see any method of specifying i386 or 32-bit anywhere in build settings.Thanks, regards, Rob.
I am seeing this problem as well when I activate whole module optimization in Build Settings.Since I have a ton of Swift files on the command line (shown in the dump), I was wondering if there was a way to tell the compiler to indicate which particular file it was working on just before the crash happens?----------------------------------------------------------------------Assertion failed: (D->getSourceRange().isValid()), function buildDeclarationRefinementContext, file /Library/Caches/com.apple.xbs/Sources/swiftlang/swiftlang-700.0.38.1/src/swift/lib/Sema/TypeChecker.cpp, line 946.0 swift 0x000000010378ae0b llvm::sys::PrintStackTrace(__sFILE*) + 431 swift 0x000000010378b54b SignalHandler(int) + 3792 libsystem_platform.dylib 0x00007fff8b2adf1a _sigtramp + 263 libsystem_platform.dylib 000000000000000000 _sigtramp + 19601246724 libsystem_c.dylib 0x00007fff8fe4cb53 abort + 1295 libsystem_c.dylib 0x00007fff8fe14c39 basename + 06 swift 0x0000000101defe92 (anonymous namespace)::TypeRefinementContextBui
Topic:
Programming Languages
SubTopic:
Swift
Tags: