Apple Maps Guides

Please see the installation guide here: https://developer.apple.com/services-account/download?path=/Documentation/Beta_Software_Installation_Guides/watchOS_beta_Software_Installation_Guide.pdfThe configuration file that the guide refers to can be downloaded from here: https://developer.apple.com/watchos/download/

On my MacPro I have some few issues.Razer Synapse does not show any connection Razer device like my keyboard or my mouse.Chrome WebGL is falling back to software rendering which causes some websites to become very slowly and flickery when scrolling.Git-Tower is always crashing when opening a Git repository.Had 2 Kernel Paniks when my Mac is set to sleep - Power Nap is disabled already (hope that fixes the Issue now)LG TrueColor app for my 21:9 display says it couldnt find USB connection (I guess the same issue like with Razer Synapse)StarCraft2 shows a pesky issue with this cursor zoom effect when shaking the mouse cursor. Still an issue How to disable 'Call out your cursor'?Dropbox-experimental does not start at launch.Box does crash and causes a dialog to show up, asking to terminate Box synchronisation.Memory Monitor does not start all.Typing my password to allow installations of tools is very troublesom. When I type as fast as usual then OSX does stop recognizing my typings at 3rd or 4th character. I have

You might be right that it is part of the reason. But they didn't have to make it open source for that reason alone. Nothing prevented them from keeping their Linux port to themselves.You make it open source if there is a benefit in either driving adoption or in faster and more efficient testing and bug fixes. Swift probably reached a plateau in adoption and was surely straining their resources in testing and bug fixing given its evolution history. Now they can deploy more of those testing and maintanence resources into Xcode (which is falling behind in capabilities relative to the latest IDEs in my opinion) as well as Apple SDK support.

The new Apple Music app is not included on the ios9 beta.. Hopefully it will be shared soon. I just installed it and it is the same music app from 8.4

From the iOS beta Software Installation Guide, available on the download page:NOTE: Devices updated to iOS beta may not be restored to earlier versions of iOS. Registered development devices will be able to upgrade to future beta releases and the final iOS software.(emphasis added)

Right - people have noted that. But in the past Apple usually put the same release in the Downloads folder. Its not there. I don't want to pull it from the App Store due to reported complications by others (which may or may not exist, but the fact remains many devs are leary of using the App Store for Xcode).

Reading between the lines of this year's WWDC presentation: What's New in Core Motion, it appears that Apple doesn't intend to give us access to the gyroscope. They don't explicitly say, the watch doesn't have a gyroscope or developers don't have access to the gyroscope, but they do explictly call out with the accelerometer whenever they refer to the ability of the watch to access raw sensor data whereas they didn't make this differentiation when talking about the iPhone.Also, they do explictly say that there is no access to the Device Motion API for the watch which is consistent since this is processed motion data that depends upon the gyroscope.If I had to speculate, the gyroscope is being taxed full time in order to make the wrist turn activation perform as well as it does. Apple doesn't want to risk sacrificing this performance.

Was having same problem. It finally worked when restarted mac, logged into app store, logged into apple dev site in safari (osx 10.10.3 ), clicked download, redeem code appeared in app store page, BUT APP STORE THEN REQUESTED AGEE TO NEW CONDITIONS (this was first time app store asked this), then redeem worked and download began. Hope this helps.BTW, I wish the 'period' worked same way in OSX as iOS, double space. Confusing for me anyway.John

It looks like a bug, where the init(rawValue:) initializer isn't being created (or isn't available) if you have defined any other initializers. Presumably it still works in playgrounds because the line-by-line compilation creates a state where the enum exists and your custom initializers don't yet.Unlike the other automatic initializers for other types, the documentation doesn't say that it isn't created if you define other initializers. (The documentation explicitly states that default initializers for structs and classes, and member-wise initializers for structs, aren't created if you define your own initializers.)I would recommend filing a bug with Apple, so that either it gets fixed or the documentation gets updated to reflect its behavior (if it's intentional so that all automatically generated initializers have similar behavior).