Hi, Problem I have a widget which displays a bright red. When I display the same view inside the app, the red is bright. However when I use the same view on the widget, the color looks a bit dull. Note: Widget Style: Default (Always) It is the same dull red when in focus and when not in focus This happens on iOS (device and simulator) and macOS Questions How can I fix it on the widget? Does widget support Display P3 colors? Any help on this would be much appreciated.

On iPhone 18 Pro, the Now Playing panel and bottom Lock Screen controls can use different material opacity and foreground colors for the same wallpaper and settings. The final appearance depends on the preceding wallpaper-editing sequence. Environment Device: iPhone 18 Pro iOS: 27.2 beta (24B5084k) Liquid Glass: Clear / most transparent setting Wallpaper: Built-in iPhone 18 Pro wallpaper collection Variants tested: Silver and Black within the same saved wallpaper configuration Feedback Assistant: FB24866793 Two observed appearance states For clarity, I use the following labels: Higher-opacity state (S_s): The Now Playing panel and bottom buttons have a light or gray, relatively solid fill with dark foreground icons. Translucent state (S_t): The same elements are more transparent and use light foreground icons. In Sleep mode, they darken and blend into the background more naturally. No Liquid Glass setting is changed during the following sequence. Shortest reproduction sequence 1. Change Silver to Black Start with the Silver variant displaying the higher-opacity state (Silver S_s). Open the Lock Screen wallpaper carousel, tap Customize, change Silver to Black within the same iPhone 18 Pro wallpaper configuration, tap Done, and exit the carousel. Observed result: Black retains the higher-opacity state (Black S_s). 2. Save Black without changing it Reopen the same Black wallpaper in Customize, make no changes, tap Done, and exit. Observed result: Black changes to the translucent state (Black S_t). 3. Change Black back to Silver Reopen Customize, change Black back to Silver, tap Done, and exit. Observed result: Silver retains the translucent state (Silver S_t). 4. Save Silver without changing it Reopen the same Silver wallpaper in Customize, make no changes, tap Done, and exit. Observed result: Silver changes back to the higher-opacity state (Silver S_s). The complete sequence is therefore: Silver S_s → Black S_s → Black S_t → Silver S_t → Silver S_s The two actual appearance changes occur after reopening Customize and saving without changing the selected wallpaper. Actual result When switching between Silver and Black inside the same saved wallpaper configuration, the existing material state can be preserved even though the new wallpaper has a different brightness. Reopening the configuration and saving it without making a change can then alter: Now Playing panel opacity Notification material appearance Bottom shortcut-button opacity Foreground or icon colors As a result, the exact same Silver or Black wallpaper can appear in either state solely because of the preceding editing history. Expected result The material opacity and foreground colors should be determined consistently from the currently selected wallpaper and the Liquid Glass setting. Switching between Silver and Black should update the appearance immediately if different treatments are intended for them. Saving an unchanged wallpaper should not alter the Lock Screen appearance. Sleep mode impact The issue is especially noticeable in Sleep mode. In the higher-opacity state, the Now Playing panel and bottom buttons remain conspicuous gray elements against the darkened Lock Screen. In the translucent state, the same controls darken and integrate with the background. Supporting evidence The corresponding Feedback Assistant report, FB24866793, includes: A screen recording of the complete sequence in normal mode A screen recording of the same sequence in Sleep mode A detailed PDF report containing screenshots, terminology, additional observations, and reproduction paths Both recordings show the following sequence: Silver S_s → Black S_s → Black S_t → Silver S_t → Silver S_s The recordings and PDF cannot be attached directly to this Developer Forums post, but they are available to Apple through the Feedback Assistant report. Request for confirmation Could anyone else with an iPhone 18 Pro test this sequence on the same iOS build? If you can reproduce it, please consider filing a separate Feedback Assistant report and referencing FB24866793.

Hello everyone!! 😊🤗 I'm starting to learn development for Apple platforms and I'd like to ask for some guidance on how to get started. My goal is to gradually develop my own video game using Xcode and Reality Composer Pro. The idea is to create an educational game with 3D environments and elements, so I also want to learn programming, experience design, and 3D content creation as I progress ⭐️ At the moment, I don't have much money to afford to hire developers to mentor me or take expensive courses 😔( My mother is sick and all our resources and budget are focused on her and her treatment. ) but I do have something I think is very important: a strong desire to learn, time, and the willingness to study and practice. I don't expect someone else to do the project for me; I want to learn how to build it myself. My main question is: where should I begin? I already have experience playing Swift Playgrounds, and I find it fascinating 🤩 but I'm looking for the next step: I'd like to know what Apple concepts, courses, documentation, or resources you would recommend I study first to learn how to use Xcode and Reality Composer Pro correctly, especially with the Apple Developer tutorials. Which videos specifically do you recommend I study? If anyone started in a similar way or has experience developing apps or games with these tools, I would greatly appreciate any advice on a learning path. Thank you so much for taking the time to read this and for any guidance you can give me! You truly don't know what this means to me. Thank you so much. 🙏🚀

Hi. On my iOS app, both the app store and the device are making changes to my app icon to make it look more Liquid-Glass. See attached image showing my original icon, and then how it appears on the app store and on devices. There is an added bevel/3d effect. I'd like to not have this happen. Did anybody figure out how to turn this off? So that the icon appears as submitted. I've played around with Icon Composer a bit but haven't managed to turn this off there. And would prefer to just submit the png's. Thank you!

All of a sudden, I am not able to create a new event on my iPhone calendar and have it repeat. Repeat does not appear anywhere in my calendar is not restricted in any way. It worked before, but after the current beta update, it does not work

i suggested to customize the Bottom navigation bar with a classic rectangular version and a new circular version, such as the Liquid Glass option. Especially for iPhone SE screens feedback ID: FB24611709

When you use .navigationTransition(.zoom(sourceID: "placeholder", in: placehoder)) for navigation animation, going back using the swipe gesture is still very buggy on IOS26. I know it has been mentioned in other places like here: https://developer.apple.com/forums/thread/796805?answerId=856846022#856846022 but nothing seems to have been done to fix this issue. Here is a video showing the bug comparing when the back button is used vs swipe to go back: https://imgur.com/a/JgEusRH I wish there was a way to at least disable the swipe back gesture until this bug is fixed.

Hello, My game was rejected under Guideline 4.3(a) (Design - Spam), with the message stating that it shares a similar binary, metadata, and/or concept with other apps already submitted to the App Store. The issue is I can’t figure out where this is coming from: No shared source code, template, or assets with any other game. No duplicated metadata. The app’s concept is still fairly niche on the App Store (I could only find around a dozen apps with a similar concept, at most). I’m trying to better understand what might have triggered this rejection, and I’m fully willing to make changes if needed. Has anyone else run into this kind of rejection under similar circumstances? How did you go about clarifying things with the review team, and did requesting an App Review Appointment help in cases like this? Thanks in advance for any insight.

I would like to suggest reducing the excessive empty space between the main content and the bottom interface area throughout iOS 27, particularly on smaller displays such as the iPhone SE and iPhone mini. In several areas of the system UI, there appears to be more empty space than necessary above the bottom interface area. On smaller displays, this reduces the amount of content that can be shown at once and makes less efficient use of the available screen space. For example, in the attached comparison, the bottom spacing measures approximately 1.9 cm using the ruler in Apple Freeform. Reducing this spacing to approximately 1.4 cm would allow more content to be displayed while still maintaining comfortable visual spacing and readability. I suggest that iOS 27 reduce this bottom spacing, along with the related margins and padding, from approximately 1.9 cm to 1.4 cm on smaller displays, such as the iPhone SE and iPhone mini. I believe this adjustment should be applied consistently throughout the iOS system rather than being limited to a specific app or interface. This would be especially beneficial for smaller iPhones, where every bit of available screen space matters. I would love to see Apple consider this improvement for iOS 27 and review the bottom spacing throughout the system to make better use of the available display area. The goal is to provide more usable screen space while maintaining readability, accessibility, and the overall visual balance of the interface. feedback ID: FB24360982

I would like to see the old design of the battery indicator panel (top right) that was in ios 18-26. Right now, this one, which is currently available in iOS 27, looks too boring. I also mean the Home panel (bottom bar). It could be switched. So that you can keep it on all the time. (In iOS 26, it disappears after a couple of seconds) In my opinion, it betrays its sophistication, and I liked it when constantly displayed. Fight overheating when performing simple tasks, it also eats up your phone, which is not a good thing.

I really appreciate the improved layout in the Clock app in Beta 5. The app now makes better use of the available screen space, allowing more information to be displayed without making the interface feel crowded. I would love to see this approach applied more consistently across iOS. Many system apps and UI elements still leave unnecessary empty space or show less information than the screen could comfortably accommodate. My suggestion is to optimize spacing, margins, and element sizes across the entire system so that iOS can make better use of the available display area while maintaining readability and accessibility. This would be especially beneficial on smaller-screen iPhones such as the iPhone SE and iPhone 12 mini and 13 mini, where every bit of available space matters. Feedback ID:24257909

Hi everyone, We're experiencing a bug on iOS 26 that only occurs when the user has Reduce Transparency enabled in Accessibility settings. App structure: Our app uses a TabView with a standard tab bar. Inside each tab, we use a NavigationStack. The tab bar is visible on root-level screens, and hidden on all pushed destinations using: .toolbar(.hidden, for: .tabBar) The problem: On iOS 26 with Reduce Transparency off (Liquid Glass active) — everything works correctly. The tab bar hides as expected. On iOS 26 with Reduce Transparency on — a white bar appears at the bottom of the screen in every place where the tab bar is hidden. This white bar: Overlaps content at the bottom of the screen. Blocks scroll, tap, and all user interactions in that area. We also tried: .toolbarBackground(.hidden, for: .tabBar) Removing all custom UITabBarAppearance configuration The only workaround we found is setting UIDesignRequiresCompatibility = YES in Info.plist, which reverts the entire app to the pre-iOS 26 design — not a viable long-term solution. What can we do? Thanks in advance.

Hello Apple App Review Team, I'm looking for guidance regarding an App Review case that appears to be pending without a response. Our app was rejected under Guideline 4.3. We responded to the App Review Team through the Resolution Center with a detailed clarification regarding the app's purpose and functionality. Timeline: July 27: App rejected under Guideline 4.3. July 28: We responded through the Resolution Center. August 4: We sent a follow-up through the Resolution Center. August 5: We opened an Apple Developer Support case regarding the pending review. August 10: We still have not received a response from App Review or Developer Support. Developer Support Case ID: 20000128863068 We have also attempted to contact Developer Support by phone but have not received a call. The latest TestFlight build has already passed Beta App Review and is available for external testing. We have intentionally held off submitting the latest build for production while waiting for clarification on the current review. We completely understand that App Review can take time, and we are not trying to bypass or challenge the review process. We would simply appreciate it if an Apple team member could check the status of Case 20000128863068 and confirm whether the Resolution Center case is still actively under review, or whether any additional information or action is required from our side. Thank you for your assistance

Hi, I am trying to find out what this effect called or how is it implemented. We use it behind the text or title, where the scrollable content goes behind it and it first starts to blur gradually and fade out. I tried using material, .background(.bar), gradient masks. None of these reproduce the same behavior. Here's what I'm referring to: Please let me know what is it or how is it implemented. Tutorial would be appreciated. Thanks!

In the Pride wallpaper, the colors overlap with the scrolling points due to the small screen size of the iPhone SE 3 in iOS 26.6

Hi, I have created this UI using custom view and not a real sheet component. But the animations and interaction is not as smooth. Earlier I was using sheet component and it was working very well, but then I had a need to add a search button on top of sheet (not inside, that is very important). And so I created this whole sheet with custom view and not the sheet component. But it resulted in loss of fluid working and animations that sheet have. Including changing between Medium detent and Large detent. Is it possible to achieve this UI with native sheet component? Or using some other native swiftui view which will have good animation that sheet has?

On iPhone SE (3rd generation), several system UI elements use corner radii that appear much more rounded than the physical display corners. This creates an inconsistent visual appearance across the system. Examples include: Markup menu Home Screen context menu Customize sheet Apple Maps bottom sheet Find My interface Safari address bar Suggestion: Please adjust the corner radius for devices with displays such as iPhone SE (3rd generation), so that system UI better matches the physical display shape and provides a more consistent visual design.

iOS 27 Beta 4: Native Liquid Glass UITabBar renders with opaque milky/frosted background while identical code renders correctly on iOS 26.5 Environment Xcode 27 Beta 4 iOS 27 Beta 4 UIKit UITabBarController Storyboard based application Native UITabBar (no custom tab bar implementation) Device: iPhone 17 Pro Simulator (also reproducible on other iPhone simulators) Problem After upgrading to iOS 27 Beta 4, the native Liquid Glass tab bar appears significantly more opaque (milky/frosted gray) than on iOS 26.5. The exact same application binary and configuration render correctly on iOS 26.5. No custom blur or visual effect is being applied. Current Configuration let appearance = UITabBarAppearance() appearance.configureWithDefaultBackground() appearance.backgroundColor = nil appearance.backgroundEffect = nil appearance.shadowColor = .clear tabBar.standardAppearance = appearance tabBar.scrollEdgeAppearance = appearance tabBar.isTranslucent = true tabBar.backgroundColor = nil tabBar.barTintColor = nil tabBar.backgroundImage = nil tabBar.shadowImage = nil Runtime Verification Verified at runtime: tabBar.backgroundColor == nil tabBar.barTintColor == nil tabBar.isTranslucent == true standardAppearance.backgroundColor == nil standardAppearance.backgroundEffect == nil scrollEdgeAppearance.backgroundColor == nil scrollEdgeAppearance.backgroundEffect == nil View Hierarchy The runtime hierarchy contains Apple's native Liquid Glass implementation: UITabBar _UIBarItemPlatterView _UILiquidLensView BackdropView ClearGlassView _UIPortalView _UITabSelectionView Therefore UIKit is using the Liquid Glass implementation rather than falling back to a legacy blur. Investigation Performed The following were tested without changing behavior: Removed all custom blur views Removed custom overlays Removed refresh/recomposition code Removed layout invalidation Removed transform hacks Removed PageMenu Replaced entire first tab with a plain UITableViewController Replaced DiscoverVC completely Replaced nested collection views Rebuilt a minimal demo project using identical UITabBarAppearance code The minimal demo renders correctly. The production application renders with a much more opaque gray background. Question Has anything changed in the Liquid Glass compositor or backdrop sampling behavior in iOS 27 Beta 4? Is there any new API or recommended configuration required to achieve the same transparency level as iOS 26.5? If this is expected behavior, is there any supported way to control the opacity of the system Liquid Glass material? Screenshots Attach: iOS 26.5 screenshot iOS 27 Beta 4 screenshot

With the declining literacy rates I think it would be incredibly valuable for apple to implement a separate keyboard experience for minors. One without auto or predictive text, swipe to text, or even potentially also voice memos. These are all very convenient features that I think could unfortunately contribute or even enable the literacy crisis as more and more children grow up and rely on technology. I also think bringing back the ‘look up’ tool on highlighted text into the main options would support and encourage more education (or even adding a thesaurus option as well) From: A Gen Z adult who grew up learning how to spell at the same time I learned how to text. Without relying on all of the convenience features that in turn can remove the mental friction that learning to fix your mistakes provides, my iPhone was teaching me how to spell with simple red lines that required me to interact with my spelling in order to correct my mistakes. Note: Autocorrect was still a feature at the time however was often turned off by most people because of text slang culture which coincidentally helped create more intentional spell check interactions. I believe the decision to turn off autocorrect should be considered a more conscious responsibility so it should not necessarily be left up to a child to decide for themselves.

Our game was written by Cocos Creator version 3.8.5 ‌TypeScript, which took the team nearly 2 years to complete. At the beginning, my application was not defined as 4.3a. The first four reviews were all normal feedback questions. We revised the questions. After the last review rejected 4.3A, we also suspected that the reasons such as game creativity, game copywriting and game art might be close to other applications. Then our team added functional innovations that other applications in the Apple Store didn't have, and the original art was original. We created new art again because of 4.3a, and also revised many places that may be similar to other developers, including that we removed all SDK modules except Apple Pay and Apple Login, and it also showed that 4.3a refused, and we have revised no less than 20 versions or failed. Our business code except the game engine code is newly developed by us and should not be duplicated with other developers' code. Is it because the JSC file and binary file output by JavaScript code are similar to those of other developers? Can we check our original code? We really want to put it on the Apple Store. We guarantee that the game was originally written. We can provide any proof, including but not limited to (GIT code submission records and codes from the beginning to today, art original proof, proof that the game mode innovation ability is not consistent with other developers' concepts, etc.) Cocos creator Engine Address: https://www.cocos.com/creator-download We have been put on the shelves in app stores such as WeChat applet and Android, and we are deeply loved by users in other channels. Dear audit, can you manually check our game code and look at the game to experience it? I believe that as the greatest technology company in the world, Apple's official staff are very professional, knowledgeable and innovative, so that Apple players can get a unique and high-quality experience. However, this repeated 4.3a refusal makes me very suspicious. So many games that use cocos game engine in the world are on the Apple store, why do we independently write the rest of the code except the game engine? Every time the reason for refusing is this passage, we have revised it for half a year, and no less than 20 game versions have been changed in half a year. Hello, The issues we previously identified still need your attention. If you have any questions, we are here to help. Reply to this message in App Store Connect and let us know. Review Environment Submission ID: 68bd1e18-6eaa-4a19-976e-c7b2e1ff0e44 Review date: June 28, 2025 Version reviewed: 2.3.0 Guideline 4.3(a) - Design - Spam We noticed your app still shares a similar binary, metadata, and/or concept as apps submitted to the App Store by other developers, with only minor differences. Submitting similar or repackaged apps is a form of spam that creates clutter and makes it difficult for users to discover new apps. Next Steps Since we do not accept spam apps on the App Store, we encourage you to review your app concept and submit a unique app with distinct content and functionality. Support Reply to this message in your preferred language if you need assistance. If you need additional support, use the Contact Us module. Consult with fellow developers and Apple engineers on the Apple Developer Forums. Request an App Review Appointment at Meet with Apple to discuss your app's review. Appointments subject to availability during your local business hours on Tuesdays and Thursdays. Provide feedback on this message and your review experience by completing a short survey.