Sorry for taking time. But now I’ve sent aa minimum sample project to my original feedback: FB23877520. Please test it.

@z0rk, @DTS Engineer Correction: when I shipped the release build with Xcode 26.4 RC and new entitlements, there was no issue. However, when I submitted a build to Mac App Store TestFlight yesterday using Xcode 26.4 (17E192), it was rejected for the same reason as @z0rk. It seems the App Store review’s automated checks still haven’t caught up with the change correctly.

Thank you! I confirmed the new version of my app has been released today.

Thank you for your assistance and clear answer. It seems my app was one of the first in the Mac App Store to use the Enhanced Security feature introduced in version 26. Following your advice, I sent an explanation of this situation to the store review and requested a new review. Regarding filing the issue, I have responded in a separate email.

@kthchew Thank you for your investigation and response. I’m not particularly knowledgeable about security matters, so I wasn’t sure how to distinguish between the two. It is appreciated you specifically tested and verified it. As it appears the original entitlements were indeed correct, I resubmitted my version to App Store Connect without modifying the entitlements. I also included the URL to this thread in the notes in submission, just to be safe. I'll update again once the results come in.

Perfect! Thank you for your quick response.

Thank you for your response. However, it isn’t exactly the same as simply turning showsBorderOnlyWhileMouseInside on. In the SwiftUI.Form style, the pop-up button shrinks its width to match the width of each option when the selection changes. Additionally, the up-down arrows are drawn even when the button isn’t hovered over.