Probably too soon to say / might take a few days, but for the love of macOS and MacBooks is the brightness flicker bug resolved?
So sketchy since Tahoe.
So sketchy since Tahoe.
i don't use claude ai, but... is anyone else reporting this?Copy some text from a Claude AI reply, paste it into iMessages and it crashes immediately 100% of time. Notified Apple about a dozen times.
Anyone notice if the screen flickering is completely gone?
I asked Claude AI a question and got this answer "Since today is Friday, January 16, 2026, there are 63 days until the spring equinox." If I paste that directly into iMessages, it crashes instantly, even before pressing Return. If I paste the answer first into TextEdit and then copy and paste that into iMessages, no problem. So there is something hidden in the Claude text answer that crashes iMessages.i don't use claude ai, but... is anyone else reporting this?
if need be (as a temp workaround), paste your text into a pages (or textedit) doc first, then paste that text into messages; see if that works. can you paste text from other sources? (website, a document, etc)...
ok, but is anyone else experiencing this? and have you tried 'messages>edit>paste and match style'? that might workI asked Claude AI a question and got this answer "Since today is Friday, January 16, 2026, there are 63 days until the spring equinox." If I paste that directly into iMessages, it crashes instantly, even before pressing Return. If I paste the answer first into TextEdit and then copy and paste that into iMessages, no problem. So there is something hidden in the Claude text answer that crashes iMessages.
I agree on that. I don't expect over-detailed changelogs such as in the open source projects (in which case you can even go and check the commits online). And surely many patches are not going to visibly affect the average users. However, "no new release notes for this software update" is completely useless.Until you discover that they have changed some obscure network parameter that is important for an application you rarely use and that now no longer works. Now that you notice it, you fill out the feedback form and pray that they fix it... This reasoning is fine in the very early beta versions, but later on, being clear and precise about the changes made could be much more effective.
its hard to describe. I sometimes think it's when the light changes in the room and the display is trying to change its True Tone or Brightness. But I haven't really narrowed down an exact scenario to reproduce etc. It's a very subtle fast flicker. It is happening on my Apple Display.What flickering do you mean exactly? Sometimes there is a short flickering somewhere. But I don't have an Apple display and also use Better Display, so I am not sure what is causing this.
Yeah, that is totally correct. I don't mine 00:00 AM, I am not getting 12:00 PM. I don't have it set to 24 hour time. I have hit set to PST (or is it PDT now?) but either PST and PDT show 00:00 PM.Strictly, there is no PM or AM appended to a 24-hour time display so the problem with 12:00 (no AM or PM) is that it means midday/noon. Since the last second before midnight is 23:59:59 and the first second after midnight is 00:00:01, should midnight be 24:00 or 00:00?
Got me but I'd bet there is an international rule.
And here it is:
In standard 24-hour clock notation, midnight is designated as 00:00.
However, there's a nuance: 24:00 can also be used to represent the end of a day, which is technically the same moment as 00:00 of the following day. So:
In practice, 00:00 is far more commonly used and is the standard in most contexts, including digital clocks, timetables, and ISO 8601 (the international standard for date and time). The 24:00 notation is typically only seen in specialized contexts like transportation schedules where it's important to clarify that something happens at the end of a particular day rather than the beginning of the next.
- 00:00 = midnight at the start of a day (e.g., 00:00 Monday means the very beginning of Monday)
- 24:00 = midnight at the end of a day (e.g., 24:00 Sunday means the end of Sunday, which is the same moment as 00:00 Monday)
Looks like an Apple coder needs to learn more about time conventions. What does it display when you set to 24-hour clock with PDT? It should be 11:58, 11:59, 12:00, 12:01 ... which is much less confusing and is correct too!Yeah, that is totally correct. I don't mine 00:00 AM, I am not getting 12:00 PM. I don't have it set to 24 hour time. I have hit set to PST (or is it PDT now?) but either PST and PDT show 00:00 PM.
11:58AM, 11:59AM, 00:00PM, 00:01PM....it not correct in any sense.
We are talking about noon, which is mid-day, I don't know anywhere that calls noon 00:00 PM. 00:00 AM is also not normal in 24 hour time..I am ok with that though, but 00:00 PM for noon is never right.. check out the highlighted files in the screen shots.
While the Paste and Match function gets around the problem, now iMessages has started crashing on EVERY message received from one person. Again, no idea why but the incoming message is received without causing a crash on iOS26.2 and looks OK with no unusual content or characters. Sent FBA to Apple each time this new crash happens.I asked Claude AI a question and got this answer "Since today is Friday, January 16, 2026, there are 63 days until the spring equinox." If I paste that directly into iMessages, it crashes instantly, even before pressing Return. If I paste the answer first into TextEdit and then copy and paste that into iMessages, no problem. So there is something hidden in the Claude text answer that crashes iMessages.
this is on your iphone... but the problem when you paste is on your mac? just confused here...While the Paste and Match function gets around the problem, now iMessages has started crashing on EVERY message received from one person. Again, no idea why but the incoming message is received without causing a crash on iOS26.2 and looks OK with no unusual content or characters. Sent FBA to Apple each time this new crash happens.
To clarify, there are no problems with iMessages receiving and sending on my iPhone running iOS 26.3. The problems (sending text pasted directly from Claude AI, and receiving message from one specific person) with iMessages are (were and still are) all on a Mac running MacOS26.2. In the hope that MacOS26.3 beta 2 might solve the problem, I just updated but both issues persist (cannot paste text direct from Claude AI response without causing iMessages crash and cannot receive message from one specific person without a crash).
(sending text pasted directly from Claude AI)
There don't seem to be any hidden characters in the text that would justify the error with this specific input.
if I set to 24 Hour time, them 12:00 PM will be displayed at 12:00, 12:01, 12:02, etc...Looks like an Apple coder needs to learn more about time conventions. What does it display when you set to 24-hour clock with PDT? It should be 11:58, 11:59, 12:00, 12:01 ... which is much less confusing and is correct too!
Calm down, they have a lot to think about... let's hope for a decent release, given that there are rumors that they want to introduce new ‘features’ (bugs) in .4. 😂Where the heck is Beta 3