I’m an Apple software QA engineer (yes, we exist) and I’d love to hear about bugs you’ve encountered. I can create bug reports (aka radars) and/or bother the right teams/people to get bugs fixed. To be clear this is not official company business, thoughts/opinions are my own, and I’m doing this in my free time to keep Lemmy awesome and because I love you guys.

Alt/throwaway account for obvious reasons.

Want to try and help as many folks as possible so please feel free to share this thread with any other communities where it is relevant.

In the interest of keeping the scope here narrow, rules for bugs:

  • iOS/iPadOS and macOS issues only. Please ensure that you are running the latest version of iOS/iPadOS (18.3.2) or macOS (15.3.2)
  • Please provide detailed step by step instructions on how to reproduce the issue. If I can’t reproduce it on my test devices, then I can’t report it.
  • Provide as many hardware details as you can (e.g. iPhone/iPad/Mac model, year, device specs)
  • Can’t help with general UI/UX complaints, use the feedback form for that.
  • Can’t help with vague power/performance/battery drain issues unless you can provide exact steps to reproduce.
  • Can’t help with services (e.g. iCloud, App Store, Apple Account).
  • Can’t help with 3rd party software
  • Can’t guarantee that anything I report will be fixed and due to the nature of how we work I won’t be able to share status updates, but I’ll certainly try my best to move things along internally.
  • Please don’t ask me about upcoming hardware/software; whatever it is, I have no idea what you’re talking about and no it doesn’t exist.

Edit 1: thanks for the reports everyone! Some of these require a little more research/testing so while it might take me a little longer to get back to you, that doesn’t mean I haven’t seen your message :)

  • 2xsaiko
    2·
    2 days ago

    Oh hey, awesome!

    I’ll just paste here what I’ve already written in Feedback Assistant.

    FB15922287 Messages sometimes only allows you to send SMS despite the recipient supporting RCS
    • Device: any
    • App: Messages
    • Conversation type: 1-on-1, RCS

    Sometimes, Messages only allows you to send SMS despite the recipient supporting RCS. During a conversation, receiving an RCS message even briefly changes the text in the input bar to RCS before switching back to SMS.

    This seems to be caused by failing to deliver an RCS message sometime before, which can always happen (bad connection on either side, recipient is offline, other network error, etc.)

    To reproduce:

    1. Take recipient phone offline
    2. Send an RCS message
    3. Wait for it to fail to be delivered
    4. Take recipient phone online

    Observed result: Messages shows the recipient as supporting SMS only, even when they are actively sending you RCS messages.

    Expected result: RCS is never artificially disallowed by Messages.

    This also happens if you use the “Send as SMS” entry in the context menu on a stuck message.

    Looks like at this point receiving an RCS message fixes this. However one sent RCS message that falls back to SMS will still lock the conversation to SMS until you get a reply.

    FB16920262 Separate window for single conversation does not mark messages as read
    • Device: Mac
    • App: Messages
    • Conversation type: 1-on-1, RCS (probably any)

    When opening a conversation in a new window, this window does not mark the messages as read when active like the main window.

    To reproduce:

    • Open conversation in new window (Control click on conversation, Open in New Window)
    • Receive a message
    • Focus the separate window/scroll to the bottom

    Observed result: The received message is not marked as read

    Expected result: The received message is marked as read like in the main window

    FB17053263 When "Group windows by application" is enabled, selecting a specific window from Mission Control does not actually focus the window
    • Device: Mac
    • App: Mission Control

    In Mission Control, with the “Group windows by application” setting enabled, you can scroll up to unstack the windows of an application to allow you to select a specific one. In this view, clicking one of them focuses the application but not the window, leading to a weird state where the application is focused but none of its windows are, and the menu bar also isn’t interactible until you click on another window.

    Steps to reproduce:

    • Turn on “Group windows by application” in System Settings (Desktop & Dock)
    • Open an application such as TextEdit, open one or multiple windows
    • Open Mission Control
    • Scroll up on the TextEdit group to expand its windows
    • Click one of the TextEdit windows

    Observed result: The application is focused but none of its windows are, nor are they ordered to front. This also looks really glitchy because Mission Control will show the animation that the selected window is expected to be in front but it will then move back behind any other windows that were in front of it after the animation is done

    Expected result: The selected window is focused and ordered to front, like when you don’t scroll up.

    System info:

    • MacBook Air M2, 2022, 8GB RAM, 256GB storage
      • macOS 15.3.2 (24D81)
    • iPhone 13 mini, 128GB storage
      • iOS 18.3.2 (22D82)

    I have a couple more watchOS ones, and a couple wonky ones that I either don’t know how to reliably reproduce, or can’t reproduce anymore right now but also don’t know if they’re fixed yet. But these should be the bugs I can think of right now that I can reliably reproduce that aren’t watchOS. If I find/remember more I’ll post them.

    This also just made me check and close 2 feedbacks that did get fixed in the meantime :^)