Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
What about banners? I was having this problem until i enabled banners

Yep, Banners enabled.

I think Tuck was onto something - if it's an app that doesn't play Sound on an iPhone notification, it doesn't buzz or make sound on Watch. Rightly or wrongly
 
Sound is enabled for my Fitbit notifications, and 'banner' selected as the notification type (it's always been set that way). The actual notifications appear on the iPhone and watch, and in accordance with expectation, with the watch paired, no sound or vibration on the iPhone - but none on the watch either.

Unpair the watch, and the iPhone pings and buzzes to fitbit notifications again.
 
Sound is enabled for my Fitbit notifications, and 'banner' selected as the notification type (it's always been set that way). The actual notifications appear on the iPhone and watch, and in accordance with expectation, with the watch paired, no sound or vibration on the iPhone - but none on the watch either.

Unpair the watch, and the iPhone pings and buzzes to fitbit notifications again
.

Bingo. We've nailed it, it's a bug I think.

Report here:

https://www.apple.com/feedback/watch.html

The more people report it, the better
 
Yep, Banners enabled.

I think Tuck was onto something - if it's an app that doesn't play Sound on an iPhone notification, it doesn't buzz or make sound on Watch. Rightly or wrongly

This what I also discovered when I was initially hav the same problem as you. What it essentially comes down to is notifications with sound. If you don't have sound enabled in notifications or is an app doesn't have that option in the notification settings, you will not get a 'tap' on your watch. And yes, I noticed that with the watch on, any apps that would make a notification sound on my phone don't. If I take my watch off, phone once again makes notification sounds.
 
This what I also discovered when I was initially hav the same problem as you. What it essentially comes down to is notifications with sound. If you don't have sound enabled in notifications or is an app doesn't have that option in the notification settings, you will not get a 'tap' on your watch. And yes, I noticed that with the watch on, any apps that would make a notification sound on my phone don't. If I take my watch off, phone once again makes notification sounds.

So you only have to take Watch off your wrist, not unpair it, to get it working on phone again?

For what it's worth, the apps I'm having issues with (Snapchat, Gumtree, Bacon Reader) all have Sounds = On and Banners = On in iPhone settings

----------

I'm currently on with Apple Support, and they're saying it's not necessarily a bug, it may just be that the apps are written like that by the devs.

I said it would be strange to write an app that notifies properly on iPhone (i.e. makes sound when Sounds = On) but then doesn't make sound when iPhone is paired with a Watch.

I also said that surely the mirroring of iPhone notifications to Apple Watch for apps that don't have a specific Watch app is handled by iOS, not the app?
 
what do you mean by the banner setting corresponds to the red dot?

I mean that if you configure a App to display a banner on your iPhone in notification settings, than a red dot will display on the watch when that app has a notification. I supposed it could be the notification center setting and not the banner setting. I'd have to test.
 
I'm currently on with Apple Support, and they're saying it's not necessarily a bug, it may just be that the apps are written like that by the devs.

I said it would be strange to write an app that notifies properly on iPhone (i.e. makes sound when Sounds = On) but then doesn't make sound when iPhone is paired with a Watch.

I also said that surely the mirroring of iPhone notifications to Apple Watch for apps that don't have a specific Watch app is handled by iOS, not the app?

You must be correct in that thinking. The simple fact that without an Apple watch in the equation, notifications work, including sound on the iPhone means the issue isn't with the apps, it's the way a paired watch handles those notifications. That makes it an Apple issue to resolve, not one for the various app developers.

I've reported it to Apple via the feedback page.
 
I mean that if you configure a App to display a banner on your iPhone in notification settings, than a red dot will display on the watch when that app has a notification. I supposed it could be the notification center setting and not the banner setting. I'd have to test.

Oh gotcha, thank you.
 
I went into Apple Store and they had no suggestions other than restoring iPhone and set it up as a new phone. They said if that didn't work, to contact online support (since it was bought online) and arrange a repair/replacement.
 
Let me get this straight: Some apps are buzzing your wrist and phone with notifications. Some are not. The same goes for me.

How in the world is that a Watch bug? The function either works correctly or it doesn't. And this "issue" occurs with the exact same apps for everybody.

I'm not saying this definitely is not a Watch bug, but it is more than likely a election the app developer has chosen to make. Has anyone actually contacted SnapChat, FaceBook etc?
 
Let me get this straight: Some apps are buzzing your wrist and phone with notifications. Some are not. The same goes for me.

How in the world is that a Watch bug? The function either works correctly or it doesn't. And this "issue" occurs with the exact same apps for everybody.

I'm not saying this definitely is not a Watch bug, but it is more than likely a election the app developer has chosen to make. Has anyone actually contacted SnapChat, FaceBook etc?

Mirroring of notifications from iPhone to Watch for apps that DO NOT have a dedicated Watch app are handled by iOS, not the app.

Also, as others on this thread stated, if you unpair the Watch, notifications for these "problem" apps work fine again on the iPhone.

What I DO know for sure is I DO NOT want notifications coming to my Watch with NO sound and NO vibrate (for apps where's I've set them to notify me) - defeated my main purpose of having a Watch - receiving notifications from my phone.
 
Let me get this straight: Some apps are buzzing your wrist and phone with notifications. Some are not. The same goes for me.

How in the world is that a Watch bug? The function either works correctly or it doesn't. And this "issue" occurs with the exact same apps for everybody.

I'm not saying this definitely is not a Watch bug, but it is more than likely a election the app developer has chosen to make. Has anyone actually contacted SnapChat, FaceBook etc?

Yeah I'm also pretty sure that this is something from Snapchat's and Facebook's end.
 
ONE other poster here has gotten it to "work" by pairing/unpairing, hardly a plurality.

And somehow the "issue" is with the SAME apps for EVERYBODY. Does that not clue you that this is by design? If this were indeed a bug, I'd think it would happen inconsistently and with various apps.

And again I ask, have you (or anyone) contacted the "problem apps" developer? They are usually quite quick and helpful with these sort of things.
 
By design? One of the core features of Apple Watch is to notify you of things on your phone! Why would it be designed so that an app with Sounds = On on iPhone and the Watch set to Sounds = On make no sound at all when the notification comes through. What kind of design is that?
 
So, because -you- don't like the design choices, it must therefore apply to everybody?

I can't answer your question, but I do know that IF this was a design choice, there is a valid reason. I can also tell you if they chose otherwise, there will be many on this forum whining how they DON'T want their watches to be so intrusive.

So again, why not just ask the developer? You would have used about 1% of the energy you've used here and would have long ago gotten your answer.
 
Same issue but on iOS messages

Hey guys,

I'm new to this and decided to create an account to list my problem. I also began having issues with my watch yesterday around noon. The only different thing I did was set my iphone to silent but was still getting my notifications with sound and haptic feedback on my watch. Around 3pm, i noticed that i no longer was getting any sound or haptic feedback from anything other than calls. Even normal iOS messages were not giving off sound or vibration on my phone or watch but i was receiving them cause i could see them once i clicked on my home button for my phone and watch. I did take it off silent, so that wasn't the issue. Since it happened on ios messages and whatsapp im assuming that it is the watch software. I reset the phone and not the watch and it didn't fix it. It was until i reset the watch, that everything began to work again.
 
Hey guys,

I'm new to this and decided to create an account to list my problem. I also began having issues with my watch yesterday around noon. The only different thing I did was set my iphone to silent but was still getting my notifications with sound and haptic feedback on my watch. Around 3pm, i noticed that i no longer was getting any sound or haptic feedback from anything other than calls. Even normal iOS messages were not giving off sound or vibration on my phone or watch but i was receiving them cause i could see them once i clicked on my home button for my phone and watch. I did take it off silent, so that wasn't the issue. Since it happened on ios messages and whatsapp im assuming that it is the watch software. I reset the phone and not the watch and it didn't fix it. It was until i reset the watch, that everything began to work again.

It's ok, apparently it's like that by design...
 
....So again, why not just ask the developer?....

In my case, because it's clear to me that since notifications from the app ARE getting to the watch, just not creating sounds and vibration which they do on the iPhone without the watch paired, it isn't something the app developer controls.

For what it's worth, what I think is happening here is that this is a consequence of the intended suppression of notification feedback on the iPhone when the watch is paired with it. And the (probably) unintended consequence of either iOS failing to pass notification feedback, or the watch OS being unable to handle notification feedback, from apps which are not Apple watch native.
 
In my case, because it's clear to me that since notifications from the app ARE getting to the watch, just not creating sounds and vibration which they do on the iPhone without the watch paired, it isn't something the app developer controls.

Unless you are a developer, you can't possibly know this. And the fact that only certain apps consistently behave this way leads me to believe it's a developer choice.

For what it's worth, what I think is happening here is that this is a consequence of the intended suppression of notification feedback on the iPhone when the watch is paired with it. And the (probably) unintended consequence of either iOS failing to pass notification feedback, or the watch OS being unable to handle notification feedback, from apps which are not Apple watch native.

This is not true, as I have third party apps that provide full feedback, and others that only display a red dot.

It may be, as you mention, an unintended consequence of an app's design. It could be intentional, as some developers are sensitive to being overly intrusive, especially apps that tend to have frequent notifications... like FaceBook and SnapChat.
 
Unless you are a developer, you can't possibly know this. And the fact that only certain apps consistently behave this way leads me to believe it's a developer choice....

Clearly it is possible to know, based on the description and circumstances I describe - unless the developer is able to switch off notification feedback in the watch when they don't have access to the SDK or APIs for it. iPhone settings control what notifications any given app produces, and whether feedback is also provided.
 
Clearly it is possible to know, based on the description and circumstances I describe - unless the developer is able to switch off notification feedback in the watch when they don't have access to the SDK or APIs for it. iPhone settings control what notifications any given app produces, and whether feedback is also provided.

The only thing you have clearly described is a situation where the developer may have opted "red dot" as the only watch notification.

If this were a bug, then we would see the same behavior in all third party apps. This clearly is not happening.
 
The only thing you have clearly described is a situation where the developer may have opted "red dot" as the only watch notification.

No, I have clearly described the entire circumstance. Above and beyond that, there's no point in further discussion.

Thanks for your time.
 
No, I have clearly described the entire circumstance. Above and beyond that, there's no point in further discussion.

Thanks for your time.

Yes, and your "entire circumstance" only proves the "bug" is more than likely by design. You have yet to explain why it only appears to affect certain apps. Nor have you explained your unwillingness to get developer input. It seems the goal here is to dogmatically assume OS error.
 
Yes, and your "entire circumstance" only proves the "bug" is more than likely by design. You have yet to explain why it only appears to affect certain apps. Nor have you explained your unwillingness to get developer input. It seems the goal here is to dogmatically assume OS error.

OK, against my better judgement, I'll bite, this once.

Two things:

1 - Design? By developers? Then tell me, why would a developer want to control a notification so the user doesn't know it's there? Particularly since the user has full control of notifications via their iPhone settings already? Why would a developer want to override the users preference and silence their own messages to that very user?

2 - How would they do this given they don't (yet) have access to the watch APIs, nor an SDK and therefore can't control the watch other than via iPhone apps - the very iPhones which already have notification controls for each app in user-accessible settings?

I don't have any resistance to talking to developers about this, or any other issue. Or Apple come to that. But it is a very closed environment which Apple controls completely, and I find it hard to believe that Apple would approve an app which bypassed their iOS APIs - they aren't that liberal with their submission rules.

But hey, let's not let that get in the way of an opportunity to accuse others of unreasonable behaviour and attitudes, just because they don't agree with you.

Thanks for that.
 
OK, against my better judgement, I'll bite, this once.

Two things:

1 - Design? By developers? Then tell me, why would a developer want to control a notification so the user doesn't know it's there? Particularly since the user has full control of notifications via their iPhone settings already? Why would a developer want to override the users preference and silence their own messages to that very user?

2 - How would they do this given they don't (yet) have access to the watch APIs, nor an SDK and therefore can't control the watch other than via iPhone apps - the very iPhones which already have notification controls for each app in user-accessible settings?

I don't have any resistance to talking to developers about this, or any other issue. Or Apple come to that. But it is a very closed environment which Apple controls completely, and I find it hard to believe that Apple would approve an app which bypassed their iOS APIs - they aren't that liberal with their submission rules.

But hey, let's not let that get in the way of an opportunity to accuse others of unreasonable behaviour and attitudes, just because they don't agree with you.

Thanks for that.

Yes, but the fact is you don't disagree with me. Your posts are self contradictory, and there's little point in debating with someone who just wants to make an argument with the usual penchant for straw man points.

And please try to actually -read- the responses before hiding behind imaginary insults to your intelligence. Several times I've explained VALID reasoning why a developer would want to mute active notifications on the watch. But you choose to ignore all that and claim some sort of bug that seems to ONLY affect the same app for all users. Then you top it off with condescending remarks about your so-called "better judgment".

"But hey", why bother contacting a developer when you can just blame Apple for everything. That's not disagreement, that's just laziness.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.