Popping Sound

I can understand the idea that adding an observer might not seem warranted in all cases, but think of the following. Whenever a transaction notice occurs - particularly a successful transaction, StoreKit deems the transaction to be incomplete. The application is expected to process the successful transaction notice, then notify the StoreKit that it has processed the transaction by making the finishTransaction call. This results in a URL notice to the StoreKit and on receipt, StoreKit marks the transaction as completed. This two way handshake is implemented as a means for StoreKit to know that a transaction has been received and processed by the app.You might have seen the alert when a purchase attempt occurs - You've already purchased this. Tap OK to download it again for free. This alert occurs because a previous attempt to purchase the item was successfully transacted on the StoreKit, but was left incomplete - for whatever reason, the URL command associated with the finishTransaction call, was not received

How is that segue defined? It sounds like UIKit thinks it's a custom segue, but there's no class specified to implement the custom perform.

I'm using an AudioQuest Dragonfly USB DAC. It worked without popping and cracking in 10.11 beta 1 but doesn't work without the popping in beta 2. Beta 2 went downhill for me!

If you are using SpriteKit, you can make an action which plays sound effects:let playPopAction = SKAction.playSoundFileNamed(yourPopSoundFile.caf, waitForCompletion: false)where the file yourPopSoundFile.caf is one of your assets.

Sure thing Jim. Thanks again for your help.I have the default template for when starting a spritekit game...GameViewController which creates my GameScene.swf along with its .sks scene file, GameScene.skslet scene = GameScene(fileNamed:GameScene)... skView.presentScene(scene)I have another scene file called Player.sks that is added as an SKReferenceNode in the GameScene.sks editor (similar to how they do it in the Whats New In SpriteKit 2015 WWDC video).I then try to access a few SKSpriteNodes that live my Player.sks from the GameScene.swift fileclass GameScene: SKScene { override func didMoveToView(view: SKView) { let playerArm = childNodeWithName(Player Arm) // player was dragged into the GameScene.sks file as an SKReferenceNode //also tried let player = childNodeWithName(Player) let playerArm = player.childNodeWithName(Player Arm) } )It sounds kind of confusing maybe, but I hope that makes sense.

Beta 2 fixed the low sound problem.Wasn't thinking of it until I heard a reminder. Nearly jumped out of my skivvies!

I had the same issue with beta #1; I haven't noticed yet with #2.I did notice that turning on the audio for the notifications brought back the haptics, at least some of the time.

Just got mine. This will sound odd, but all I had to do to get it was reinstall the original profie. There was nothing for the watch to do, so it just restarded but once it came up I was able to check for updates via the watch app on the phone and it came right up. 24MB of No more Beta 1. It's installing now so I don't know how good it is, but I hope this helps you and anyone else having problems.Credit: Original solution was posted in another thread by jw154j

I've done some testing and it seems CryptoSwift should be ok. I'm loading the entire song into NSData which is using a fair bit of memory but the audio files I'm using are no longer than 10 minutes in length and it seems to run fine on my old iPad.

Same issue - sometimes getting less than an hour with moderate - heavy usage (no external sound tho).

I have not been able to send a single message since installing the beta. iMessage or SMS. I have a reply button and can choose from predefined replies or dictate a new message. And it even animates off and makes it's sound as thought the message has gone. But nothing gets sent. The recipient receives nothing and the message do not appear in messages on my iPhone. All messages just disappear as though they never existed. This has been the case since initially installing Beta 1 and now with Beta 2.I have read some ambiguous message in these forums and can't really tell if others are having the same problem as me or not. Am I alone in not having anything send, at all, ever?

Same problem on my sideI have 7 POP accounts - all proper workingIf I activate one of mine 5 Exchange accounts Mail crashes - but new is a new Window which appears before the crash.This windows asks me if Mail should proceed OR crash with crashlog to Apple. If I select crash it is like it always was. If I select proceed then Mail does not crash, but also not work. Totally frozen. Always.As I mentioned it also at Beta 1 - it is a shame of the MAIL department to release always Beta versions were Active Sync and Exchange Integration does not work - so it is always stupid for developers to use the Beta because of missing company email accounts. And not every dev has two mac´s.