LLDB crash

After a clean install of 10.11 - I cannot connect to my carddav server on OS X Server 5.0beta1 anymore. Computers that are still using an upgraded version from 10.10 to 10.11 won't have the issue.If I try to set everything up through Contacts -> Preferences -> Accounts, the preferences pane and Contacts will crash immediately.If I try to set it up as server account through System Preferences -> Internet Accounts, CalDav and CardDav won't even try to connect.If I set it up as CalDAV account through System Preferences -> Internet Accounts, Calendar is working correctly.If I set it up as CardDAV account through System Preferences -> Internet Accounts, CardDAV is still not connecting.I suppose, the automatic port configuration might be the issue.How can I set it up correctly and manually?username - okpassword - okserver address - okpath - what is os x server's default path for carddav - /principals/ will result in not connecting at allport - I suppose it's 443

Direct Tv GenieGo crashes everytime after a few minutes

Thank you for link. Forgot about when search criteria.Indeed NSData works for Mail, but it crashes TextEdit. Stanislav

Ok, I think I understand:In a where clause, it is currently not possible to include all generic versions of Optional<>But it is possible to include all implementers of a certain protocolSo, as a workaround, the OptionalType protocol can be created, and Optional can be extended with itNow when including the OptionalType protocol in a where clause, all generic versions of Optional<> will be included (but other implemeters of that protocol too)As it is not guaranteed that an implemeter of OptionalType actually is an Optional<>, the method flatMap needs to be used, which will definitely return an optional U?In flatten, the flatMap function will move the return type from Generator.Element to Generator.Element.T?Then filter and map are used to filter out nils and unwrap the remaining Some valuesGenerator.Element.T is provided as a typealias by OptionalType, which just makes the generic type of Optional<T> accessible>> I don't like this particular implementation, since it handles the ot

I am not sure what is going on, but I have the same problem. A lot of spinning rainbows. Mail seems to be having trouble with iCloud and has crashed on me once. Safari has crashed on me serveral times.I sure the beta will become more stable on future updates.

I found this one too. It had a Unity logo, so it may have snuck when I did some Unity work years ago.And removing all color pickers fixed my storyboard crashes.

> Could you give an example of a working implementation where `Generator.Element` is anything other than `Optional<Generator.Element.T>`? I tried but could not come up with one.Turns out not to matter. I messed up that part 😉. Because flatmap takes a T -> U?, it doesn't need you to provide it with a Generator.Element -> Generator.Element.T?—which is what I was saying wouldn't work—but instead a Generator.Element.T -> Generator.Element.T?, which means the implementation using flatMap will always work, since you can always write that function as {$0}. Sorry for any confusion my confusion caused.> Seems not to work, the Playground crashes when I enter this.Bummer. I was hoping you could use the associated type introduced by the OptionalType protocol to supply the type argument to Optional<>.Since it seems you can't, that means you can't make the extension more closely match your original intent, or remove the extraneous .map { $0.flatMap { $0 } } (or .map { $0.intoOptional()

There used to be a minimum quantity threshold (5?) before crash reports would become available - perhaps that is still the case in your example.◅▻

Haven't tried with a queue but even a single sound item causes crashes. Try running in simulator to see if it asks for a bluetooth headset as this is the behaviour I and a few others are getting.

Hi Stephen, Thanks for your post. Crashes for Apps distributed on TestFlight should appear in in the Crashes Organizer. I'm curious what you mean when you say Apple support says that Testflight does not send reports for prerelease builds. Is this something you see in the documentation or did you hear this from an Apple Developer Technical Support representative? You can find more information on the Crashes Organizer here ( https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/AnalyzingCrashReports/AnalyzingCrashReports.html). If you’re willing to start a Radar bug report on bugreport.apple.com, we can try to diagnose the issue. Please include in the report the following information about the app that you’re not seeing crashes for: bundle identifier, Apple ID for the app (you can find this on iTunes Connect when viewing your app’s version on the store under “General App Information), version number, and build number. After you've created