Visual Studio Maui IOS

I'm seeing the exact same thing as @mattreimer. This looks like an iOS bug because the exact same code using textContent works fine in Mac Catalyst. It also seems to work fine in the simulator.

Thank you for your post and for providing a detailed description of the issue. If I understand correctly, the UI was created using Storyboards? I always recommend starting with a simple, out-of-the-box UI in iOS 26 and then customizing it. Could you please provide a method to isolate the functionality of the FloatingBarContainerView into a single, focused, and simple project? So we can download and take a look? Do you get the same results with just the relevant code in a small test project? If so, please share a link to your test project. That'll help us better understand what's going on. If you're not familiar with preparing a test project, take a look at Creating a test project. Albert Pascual
  Worldwide Developer Relations.

Same problem, works fine in iOS 18.X not at all in iOS 26.01

While the technique of using the appearance APIs might remain valid for customizing the navigation bar in iOS 18 and earlier, starting in iOS 26, we recommend you reduce your use of custom backgrounds in navigation elements and controls and let the system determine the navigation bar background appearance. Any custom backgrounds and appearances you use in the navigation bar might overlay or interfere with Liquid Glass or other effects that the system provides. To learn how to customize your app’s navigation bar in iOS 25, please review the sample code provided in the Customizing your app’s navigation bar documentation.

I duped this one as well (FB20547079 for iPadOS 26, FB20376452 for macCatalyst 26.1, and FB20376479 for iOS 26.1). The problem still exists in beta 2.

Hi Albert, Thank you for the clarification. I have a few follow-up questions: Developer Mode Detection: Is there an official API to detect if Developer Mode is enabled on iOS 16+? We've found that third-party location spoofing tools (like LocaChange) require Developer Mode to be enabled. For location-dependent apps that need to assess spoofing risk, detecting this state would be valuable. What's the recommended approach? External Location Providers: You mentioned third-party tools are external location providers. Does this mean they use a different mechanism than CLLocationManager? Is there any way to distinguish between genuine GPS and external providers programmatically? Security Best Practices: For apps requiring location authenticity (fraud prevention, geofencing, etc.), what is Apple's recommended approach to detect location spoofing via third-party tools? Are there any APIs, private frameworks, or best practices you can suggest? Feature Request: Would Apple consider adding APIs like: isDevelope

Hello, We don't have specific points of the app code where it may be crashing, since it's random, we already seen code crashing at very different locations around the app. Currently, about 5% of our users base is having this crash, also another detail, we are seeing this around different versions of iOS, not specific to iOS 18 or 26. We suspected at first about the compiler of new Xcode 26 (since this was the first version compiled with new Xcode), but it seems it is not that. We have sent a new build out today, compiled with Xcode 16.4, but no luck, still crashes. I'm attaching 2 screenshots, from the crashing stacktrace, one from Sentry and the other one from Xcode crash reporter directly. Also, attached the .crash file with the full stacktrace that can be found at Xcode. 2025-10-01_14-37-42.7083_-0500-2937c5ddef763873e9e26e42e243231a23e27df5.crash

It looks like iOS 26.1 introduces a legitimate API to detect this https://developer.apple.com/documentation/foundation/processinfo/isiosapponvision

still an issue in ios 26.1 b2