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.
Quirky Message Notifications
- Thread starter jwatters579
- Start date
-
- Tags
- alerts notifications
- Sort by reaction score
I’m really really tired of this issue. My gf is an icu nurse and my iPhone 12 pro on 14.2.1 is not showing messages. I’ll open the app and it’s showing I opened the message when I never did.
then she has to call me and say I read her message 20 mins ago when my phone 1. Never notified me and 2. Said I read it already.
this is a huge problem. What is going on?
then she has to call me and say I read her message 20 mins ago when my phone 1. Never notified me and 2. Said I read it already.
this is a huge problem. What is going on?
Thank you to her for doing what she does! 👏🏼👏🏼👏🏼😷
Yeah, it’s a massive issue. I imagine it’s happening to everyone, but most people either only notice it sometimes, and chalk it up as a glitch, or see it happening, don’t know what to do about it, and chalk it up as a big glitch.
Question some of my notification come in silent? Everything is on high vol. as I was TV I see my screen light up but I don’t hear anything? Doesn’t even vibrate and some times it makes sound perfect?
Is this a big with notification issues and related to txt messages and other like FB and IG also?
Is this a big with notification issues and related to txt messages and other like FB and IG also?
Had this bad on RC1 and iMessages but working OK for me on RC2 so far. Reading from the other posts, doesn't look like it's fixed.
Articles say Apple is aware of the issue but don't expect a fix in 14.3.0.
Looks like the issue is getting some much needed attention.
apple.news
iPhone Users Report Serious Messaging Problems With iOS 14 — Forbes
Widespread messaging problems are impacting iPhones running iOS 14...
It's ridiculous that Apple hasn't fixed this yet, it's been over a month, this has been a massive problem for me since day 1 of 14.2, I submitted a bug report over a month ago and haven't heard anything from Apple.
You can't have these kind of bugs in a release of an public OS and not acknowledge it for over a month, I thought Apple was taking steps to minimize these kinds of things happening after last year? Apparently that is not the case.
You can't have these kind of bugs in a release of an public OS and not acknowledge it for over a month, I thought Apple was taking steps to minimize these kinds of things happening after last year? Apparently that is not the case.
I say this as a software developer (who is no where near the skill level of a dev on the Apple payroll working on iOS)....
I think the problem is too much code that has been touched by too many hands over too long a time period.
As a developer, eventually the code you are working with starts to fall into "the mind of god". In other words, the code becomes too much for the human mind to follow. You eventually have millions of lines of code, spread across thousands of methods/procedures/subs/functions, written by so many different devs in so many different styles, written over so many years of time.
As a developer, once this happens, you become petrified of changing ANYTHING. Even the most simple code changes scare the hell out of you because there is a chance what you just changed will break something a developer 10 years ago wrote in a completely unrelated function.
I suspect that this is the state of iOS..... I think the codebase is probably such a tangled web at this point that they simply CANNOT push bug-free updates anymore. Every time they make a change, something somewhere breaks.
Part of me thinks this is actually a big reason they are making a big deal about the Apple Silicon version of MacOS being "written from the ground up" for that hardware.... they likely either did a huge rewrite (what we call in software dev "refactoring") of MacOS for ARM, or they were otherwise able to purge millions of lines of old code.
I would not at all be surprised if Apple at some point is forced to do a complete rewrite of iOS.... these bugs are becoming more and more frequent, and I suspect that this will be the only solution to the problem.....
I think the problem is too much code that has been touched by too many hands over too long a time period.
As a developer, eventually the code you are working with starts to fall into "the mind of god". In other words, the code becomes too much for the human mind to follow. You eventually have millions of lines of code, spread across thousands of methods/procedures/subs/functions, written by so many different devs in so many different styles, written over so many years of time.
As a developer, once this happens, you become petrified of changing ANYTHING. Even the most simple code changes scare the hell out of you because there is a chance what you just changed will break something a developer 10 years ago wrote in a completely unrelated function.
I suspect that this is the state of iOS..... I think the codebase is probably such a tangled web at this point that they simply CANNOT push bug-free updates anymore. Every time they make a change, something somewhere breaks.
Part of me thinks this is actually a big reason they are making a big deal about the Apple Silicon version of MacOS being "written from the ground up" for that hardware.... they likely either did a huge rewrite (what we call in software dev "refactoring") of MacOS for ARM, or they were otherwise able to purge millions of lines of old code.
I would not at all be surprised if Apple at some point is forced to do a complete rewrite of iOS.... these bugs are becoming more and more frequent, and I suspect that this will be the only solution to the problem.....
This is kinda what I was saying to another person on here: I wonder if it’s gotten too big, to the point where they‘ve lost control of the beast.
Even a ground-up re-write of iOS, or all of the OSs, may be insufficient because of all the background code working on their servers. They’d need a ground-up re-write’s for all of their services’ code, no? 😧
Here is what I see in the 14.3 release notes. I really hope it’s fixed in 14.3. I have missed so many messages because I never received any form of notification when they were sent.
This release also addresses the following issues:
This release also addresses the following issues:
- Some MMS messages may not be received
- Some Messages notifications may not be received
It would also be nice if the keyboard lag I experience all the time in messages would be fixed in 14.3. Guess I’ll have to test.
Is there any way to roll back to 14.2.1? That worked for me with minor issues from time to time. 14.3 so far has been a disaster.
All devices updated. Still having the same issue, but, once again, turning off BT in Settings worked for me.
I even tried an iterative process of getting out of the thread in Messages (that seemed to work for some people). Overall, turning off BT in Settings is the answer thus far For me.
I even tried an iterative process of getting out of the thread in Messages (that seemed to work for some people). Overall, turning off BT in Settings is the answer thus far For me.
Thanks for posting this. I've not been notified for "green bubble" texts for the last few days and it's been driving me nuts.
I installed 14.4 on my iPad and iPhone and 7.3 on my Watch 6 in the hopes that the Notifications fiasco might be fixed. It is not.
This afternoon I'm sitting in my living room watching TV. My iPhone is asleep beside me. My iPad is asleep in another room. The watch is on my wrist. I got a message. How do I know? Because I heard the Message notification tone on my distant iPad. Nothing on my watch. Nothing on my iPhone. I wake up my iPhone and have a look. Is there a notification or preview? No. Has the message arrived? Yes.
This is how it has been for months for me. I posted another thread on this, but it garnered no interest as someone moved it to an unlikely spot: Notifications - Why So Unreliable in the Apple Ecosystem?
Sometimes when I'm cycling with my watch on my wrist, the iPhone in my pocket and the iPad in my bag I'll get a message notification. Where does it go? To my watch. I stop and have a look at my iPhone. Is there a notification? No. Has the message arrived yet? No. The message is only on my watch. So, I'm stuck reading it on my watch and responding with the canned response, or finger scribbles or, horror of horrors, something that I deign to dictate. (Usually, much to my regret later.)
[rant]
This is a horrible and inexcusable failure on Apple's part. Notifications need to work. They need to go to all your devices if you so desire and manage to figure out to set it up right. They need to be sent on a timely basis. Otherwise, what good are they?
I happen to own a lot of Apple stock. I would gladly trade the dividend announced today for a notification system that works reliably.
[/rant]
This afternoon I'm sitting in my living room watching TV. My iPhone is asleep beside me. My iPad is asleep in another room. The watch is on my wrist. I got a message. How do I know? Because I heard the Message notification tone on my distant iPad. Nothing on my watch. Nothing on my iPhone. I wake up my iPhone and have a look. Is there a notification or preview? No. Has the message arrived? Yes.
This is how it has been for months for me. I posted another thread on this, but it garnered no interest as someone moved it to an unlikely spot: Notifications - Why So Unreliable in the Apple Ecosystem?
Sometimes when I'm cycling with my watch on my wrist, the iPhone in my pocket and the iPad in my bag I'll get a message notification. Where does it go? To my watch. I stop and have a look at my iPhone. Is there a notification? No. Has the message arrived yet? No. The message is only on my watch. So, I'm stuck reading it on my watch and responding with the canned response, or finger scribbles or, horror of horrors, something that I deign to dictate. (Usually, much to my regret later.)
[rant]
This is a horrible and inexcusable failure on Apple's part. Notifications need to work. They need to go to all your devices if you so desire and manage to figure out to set it up right. They need to be sent on a timely basis. Otherwise, what good are they?
I happen to own a lot of Apple stock. I would gladly trade the dividend announced today for a notification system that works reliably.
[/rant]
Addendum: I'm just now actually using my iPad to have a Messages conversation with my daughter. I'm holding the iPad. Messges is on the screen. My daughter sends a message. Where does the notification go? To my iPhone which is asleep on the floor of the living room.
