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 :)
I have a petty one:
- Go to Settings and disable Apple Intelligence
- use Siri voice control for a task
- the Siri icon thing remains at the bottom of the screen because it’s listening for the next command.
- tap elsewhere on the screen
Expected: Siri goes away
Encountered: the tap does nothing - Siri will continue listening until you say “thank you” or turn off the screen.
Workaround: restart the phone and the problem goes away.
I’d settle for Apple Intelligence not turning itself back on with every iOS update.
yeah that’s a good callout, thx!
Not really a bug, but I hate the blank space at the top of a macbook screen if you set your dock to auto-hide. It’s a waste of screen real estate.
?
I have my dock and top bar set to auto-hide and my windows typically take up the full screen, wasting no space at all.
On my iPhone 15 pro using the windows 11 phone link will cause my phone to stop connecting to other devices.
Basically set up phone link so it can send notifications to the PC, and use it for a bit. After that shut down (or just walk away) from the PC and try to connect to a Bluetooth device (AirPods for example). Most of the time it won’t work. My AirPods for example will get stuck connecting. I haven’t found the exact rhyme or reason of when it does work. But usually when it’s broken turning Bluetooth off and back on again (in system settings) fixes it.
Certain sites like Reddit and YouTube are painfully slow or just don’t work sometimes in Safari 18.3.
Also the Music app on macOS is horrible. Very simple things like searching and navigating are buggy and seem like they’ve never been tested.
I recognize this is a “feature” but I think it should be treated like a bug, or at least let us turn it off!!
Whatever egghead came up with the “keyboard hot zone” that dynamically (and invisibly) increases the size of the keys based on what it thinks you’ll type deserves to be tarred and feathered. Problem is, it’s always fucking wrong. It happened already typing this text, the above “increases” was first typed as “increased” because it expected “d” and thus made the “d” key zone slightly larger and the “s” zone slightly smaller. I tried typing “NCASE”, like the PC case brand, the other day, and I had to try repeatedly to get the “s” key to pop. I kept hitting the “a” key because it expected “NCAA” and increased that key zone.
Just the iPhone keyboard overall is bad. Inconsistent layouts based on where you’re typing. No number row. No period/comma (unless you’re typing a website). Just why.
Bruh I never made the connection that this was happening this explains so much
Glad I’m not alone! The predicting capabilities have become too aggressive.
Sometimes app icons stay in their dark version even though the UI is in light mode. Was still present in iOs 18.3. just updated to 18.4 so don’t know if it has been fixed yet.
The (picture) convert function in iOS shortcuts ignores HDR. So when I edit my HDR ProRAW photos and then convert them to HEIF to save space after I‘m happy with my edit, the image looks SDR/dull. It’s bad enough the only native way is constructing your own shortcut… How else are you supposed to use ProRAW without absolutely trashing your storage?
To add to this, iOS (and macOS) are very sensitive about what a file needs to have to be recognized as HDR. A lot of 3rd party HDR files just won’t render as HDR even though the data is all there.
The retro Mac screensaver in MacOS crashes like 97% of the time. I have confirmed it’s not just for me.
Also: Can you please ask someone to add the OpenDyslexic font to apple books?
Could you please clarify what you mean by
retro Mac screensaver
? To my knowledge this isn’t the name of any stock screensaver. Also could you please share the specs of your Mac?The literal name of the screensaver is “Macintosh”.
Specs:
Cheers!
💙
- Founder Supreme, The “Has Apple Ever Responded to Your Feedback?” Support Group
I have this notch in my MacBook Pro display, and system tray icons just disappear behind it once I have too many of them. I need a third party app like Ice or Bartender to fix this bug, and honestly, it’s embarrassing for Apple to not have fixed this in so many years.
The notch is a design crime.
yup that’s a great callout, thanks!
Bug Report: Missing AppleScript Introduction on First Login
Summary
After logging in for the first time, users do not receive any introduction or guidance on using AppleScript. As a result, one of macOS’s most powerful automation features remains hidden and underutilized.
Steps to Reproduce
Set up a new macOS device or create a new user account.
Complete the initial macOS setup process.
Log in for the first time.
Observe the lack of any AppleScript introduction or onboarding.
Expected Behavior
After logging in for the first time, the user should be presented with an introduction to AppleScript, including a brief explanation of its capabilities and an option to open the Script Editor with example scripts.
Actual Behavior
No introduction, tutorial, or prompt related to AppleScript is displayed. Users remain unaware of its presence unless they actively seek it out.
Environment
macOS Version: All
Device Model: All
User Type: First-time user (new account or fresh macOS installation)
Reproducibility: 100% (occurs on all tested machines)
Additional Information
AppleScript is a core feature of macOS but is not surfaced to users who may benefit from it.
Other macOS features, such as Shortcuts, receive more prominent onboarding.
A simple onboarding dialog or notification could greatly improve discovery and adoption of AppleScript.
Suggested Fix
Introduce a brief AppleScript onboarding experience upon first login, possibly including:
A welcome screen explaining what AppleScript is.
A button to open the Script Editor with example scripts.
A link to documentation or tutorials.
Just my personal opinion, I think this is unlikely to happen. Even the official docs for AS are part of the Documentation Archive. You’re better off using Shortcuts if you can.
dressing up your pet feature request up as a bug report isn’t going to work
It’s totally gonna work /s
lol he just made up an “expected behavior”.
Firstly, I have to thank you for doing this - you’re awesome.
Given your
Can’t help with general UI/UX complaints
I am unsure you can help, but I’ll drop it in here anyway.
Device: iPhone 14 Pro on iOS 18.4 (released by the time of this comment)
Issue: When screen recording, the Dynamic Island activity shows up in the recording - this is intended. However, if I do something in an app which full-screens the UI (as in the app hides the status bar - for example, I tapped a photo in the Photos app to hide everything but the photo, zooming in also works I think), the island activity disappears, but the black cutout remains in the video until a few seconds later, when it too abruptly and weirdly disappears with some weird flickers and other visual glitches. I can’t word it properly, so here’s a video (idk how to upload it so here’s the first way I found to do this - lmk of any other way to do this): https://streamable.com/ko8gsy
My test case: I am playing music, and the dynamic island shows the now playing activity. I start screen recording in order to demonstrate the issue. I then go into an app which has the capability to hide the status bar (clock, wifi/cellular, battery and the dynamic island activities) - in my case, I choose to tap on a photo in the Photos app to hide all but the photo itself. I zoom into the photo before I do that so that the island isn’t on the black part of the UI (issue would be invisible). After tapping and when the status bar disappears, the activity does so too, but the cutout/“pill” remains until a few moments later, when it glitches out when it abruptly disappears too.
Has been happening since the iOS 18 dev betas in the summer at the least.
Sorry for the incredibly bad wording. Lmk if you need more info
The monitor calibration tool on macOS does not support HDR properly, resulting in severe miscalibration.
Also while writing this post I realized “miscalibration” is not in iOS’s spellcheck dictionary lol.
Also Apple doesn’t fully support high refresh rate displays. My current display Apple supports as 100Hz when on Linux and Windows I can run it as 120Hz or 144Hz.
(M2 Mac Mini running 15.3.2)
External monitor is connected via thunderbolt to DisplayPort cable. It’s connected to my Windows/Linux computer via DisplayPort cable directly to the GPU.
Using a song as an alarm sound only works if it’s locally downloaded in Music and there are some codec and bitrate restrictions as well, but this is never explained anywhere. I’ve had to figure it out by trial and error.
At the very least there should be a warning in the Alarm app when you choose a song as an alarm that isn’t going to work.
Round 2 :)
This one is very annoying when I have Safari windows already open on my secondary display and trying to create a new Safari window on my primary display because it then needs an extra click to focus the window.
Since this occurs with multiple apps (and also third-party ones like BBEdit), this is very likely not an issue in each of the apps but rather in AppKit or the windowing system.
FB17088400 Opening a new window of various apps via the Dock icon while the app is inactive does not focus it when it is created on another display
Normally, opening a new window of an app that supports this via the dock icon (e.g. Finder, Terminal, Safari) focuses the newly created window. However, this does not work correctly when the app is not focused and the previously focused window of the app is on a different display. In that case, it will create the new window on the current display, but keep the previously focused window focused.
This does not happen if either the app creating the new window is already active, or there are no windows of that app, or the previously active window is on the same display as the new window is created from using the Dock.
I’ve found this issue to occur in the following apps:
- Finder
- Terminal
- Safari
- TextEdit
- QuickTime Player
To reproduce:
- Have at least two displays connected
- Open Terminal (or any other app of the list above) with at least one open window
- Focus another app (e.g. Finder’s desktop) on the display the Terminal window is not on
- Control-click on Terminal’s dock icon on that display
- Select “New Window”
Observed result: Terminal creates a new window, but does not focus it. Instead, the last focused Terminal window is activated.
Expected result: The newly created window is always focused (and appears on the display the Dock was used from).
System info:
- MacBook Air M2, 2022, 8GB RAM, 256GB storage
- macOS 15.3.2 (24D81)