that was/is a beta 2 bug. double press the button again and it'll change to ready
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Seeds Third WatchOS 2 Beta to Developers
- Thread starter MacRumors
- Start date
- Sort by reaction score
If you are running Beta Software and didn't do an 8.x Backup you can restore to a signed 8.4 device, you're stuck with it. I however, don't run beta software like that.
No. I had a backup of WatchOS 1.0.1 done on 8.4 prior.
When DP2 came out - I was able to restore my phone, and my watch (in that order) and restoring it from an 8.4 Install replaced everything on it, and set it back to 1.0.1.
Last edited:
No. Doesn't work. Never had an issue with ApplePay in Beta 2. It currently loads my card and the icon for the card when double tapping button. Double tapping again and again just gives me the alert sound and the same text over and over. again, never had this issue in Beta 2...
Actually, I think this feature was there at least in beta 2, maybe even earlier. I turned this on when it gave me the option for beta 2, that's how I know. Still a really good feature that Apple implemented though.
Hey, I have an issue sending iMessage. I can't send them at all... how can I fix it? unpairing doesn't work
Did you follow the beta instructions that said to sign out of iMessage on your phone prior to installing the watchOS beta? I'm assuming not. Try signing out of it on your phone and then signing back in.
So far I haven't had the greatest successes with the update. It was a miracle getting it to install to begin with, but once I finally did (after 1.5 hours approximately - on gigabit internet with 802.11ac wifi) I found it still incredibly buggy. My battery life drained 5% in an incredibly short period of time.
I did notice that previously I was hanging on installing apps and the entire device would freeze, this seemed fix in this iteration. iMessages still weren't working at all and it permanently showed that I was near a Walgreens when I was not and wanted me to use my loyalty card. All in all, seemed pretty wonky. I decided in light of that, since the previous Beta was so c0rrupt that I would start over fresh and wipe and not restore a backup.
The wipe process looked to succeed, however upon finishing, it just sat at a black screen and never rebooted, and I had to hard reboot it (both buttons). Upon restarting, it presented me with pairing, which I attempted. It started out smoothly, but upon finishing the iPhone portion, the watch reverted back to the language selection to restart the pairing process, and the phone still said it was syncing. I then canceled out of the phone portion and tried to pair again, and it hung on verifying my Apple ID.
Finally I rebooted both devices and the pairing process was successful. Upon completion, iMessage worked successfully and the overall behavior/performance was a lot better. Unsure of battery life currently, not enough time to tell. Seems better than the ultra fast drain from before though.
Just wanted to report my findings to everyone in case this is helpful.
TLDR; if you are having funny behavior after installing the update, wipe and setup as a new watch. This process might be wonky and take a few tries, but life is a lot better afterwards.
I did notice that previously I was hanging on installing apps and the entire device would freeze, this seemed fix in this iteration. iMessages still weren't working at all and it permanently showed that I was near a Walgreens when I was not and wanted me to use my loyalty card. All in all, seemed pretty wonky. I decided in light of that, since the previous Beta was so c0rrupt that I would start over fresh and wipe and not restore a backup.
The wipe process looked to succeed, however upon finishing, it just sat at a black screen and never rebooted, and I had to hard reboot it (both buttons). Upon restarting, it presented me with pairing, which I attempted. It started out smoothly, but upon finishing the iPhone portion, the watch reverted back to the language selection to restart the pairing process, and the phone still said it was syncing. I then canceled out of the phone portion and tried to pair again, and it hung on verifying my Apple ID.
Finally I rebooted both devices and the pairing process was successful. Upon completion, iMessage worked successfully and the overall behavior/performance was a lot better. Unsure of battery life currently, not enough time to tell. Seems better than the ultra fast drain from before though.
Just wanted to report my findings to everyone in case this is helpful.
TLDR; if you are having funny behavior after installing the update, wipe and setup as a new watch. This process might be wonky and take a few tries, but life is a lot better afterwards.
read the releaes notes ppl lol https://developer.apple.com/library...asenotes/General/RN-watchOSSDK-2.0/index.html
apple pay is disabled for this beta.
and interestingly it says haptic feedback is not functional for this beta; but ive had no issues in fact its been perfect---confused about that
apple pay is disabled for this beta.
and interestingly it says haptic feedback is not functional for this beta; but ive had no issues in fact its been perfect---confused about that
100% new that apple watch activates and recognizes it. https://developer.apple.com/library...asenotes/General/RN-watchOSSDK-2.0/index.html
Darn, I went by this article and they called it 13S5293e, guess "Apple Insider" is no MacRumors! http://appleinsider.com/articles/15...9-watch-os-os-x-1011-el-capitan-to-developers.
Thank You for bringing this to my attention.
How can you pair your Apple Watch with watchOS 2 with iOS 8.4, I tried and in iOS 8.4 that I need to update to make it work. I even put an older backup of watchOS 1.0 from April 26th and it was still in watchOS 2...
Unfortunately my battery life in beta 3 seems to only be slightly improved from that of beta 2. We'll see how tomorrow goes. Do you think all this unpairing, repairing, etc is corrupting the file system such that processes are running erroneously, thus causing premature draining?
Happy to report this beta is much better, battery seems to be about normal with what I was getting at launch , iMessage works( for anyone having the issue , reset your watch and skip signing in with apple ID and it will ask you to set up messages separately, fixed the issue for me right away). Calls, emails and notifications all coming through now and the music app is working better, although if I go to play a playlist thats on Apple Music and not saved to my iCloud Library I get an error about Wifi. Apart from that the watch has a proper purpose again other than looking cool.
Can you clarify or be more specific about the steps you took to get iMessage to work? My issue is that some but not all iMessage conversations are on my Watch.
I erased the watch and went through the initial set up again. When it asked for the Apple ID I skipped the step and this then asked if I'd like to sign into iMessage independently of other iCloud services and Apple Pay. When I signed in on the iMessage sign in screen I got a notification on all my other iOS and Mac devices that iMessage was now being used on Apple Watch, as far as I can tell all messages are coming through since.
Thanks for replying!
By erasing the watch do you mean unpairing it with the iPhone or actually choosing in the Wath App General>Reset>Erase All Content and Settings?
To be clear I am receiving all new iMessages on my watch, but not all of the older iMessage conversations on my iPhone have synced to the watch.
Just wanted to say that Beta 3 fixed the absolutely HORRIBLE Beta 2. My watch works again 
If you were on the fence about a watchOS Beta, this is the one to try IMO.
If you were on the fence about a watchOS Beta, this is the one to try IMO.