Skip to content

Conversation

@theproducer
Copy link
Contributor

Adding documentation to address ionic-team/capacitor#8172

@theproducer theproducer requested a review from a team February 5, 2026 14:52
@vercel
Copy link

vercel bot commented Feb 5, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
capacitor-docs Ready Ready Preview, Comment Feb 5, 2026 2:52pm

Request Review

Comment on lines +71 to +72
To fix this add the following entry to your `Info.plist`:
`UIDesignRequiresCompatibility = YES`:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What other changes does UIDesignRequiresCompatibility YES create on Capacitor app UI?

Docs aren't exactly clear on that https://developer.apple.com/documentation/BundleResources/Information-Property-List/UIDesignRequiresCompatibility - It makes the app look like it was run on iOS 18? Disables Liquid Glass (which I guess Ionic doesn't support yet), and...?

Also there's this

Warning
Temporarily use this key while reviewing and refining your app’s UI for the design in the latest SDKs.

Which makes this seem like it won't be a solution forever, probably won't work on 27?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, the problem is that Capacitor itself isn't SwiftUI yet, so we can't support some of the more intricate controls available for iOS 26. Changing that should be one of our goals for Capacitor 9 to get ahead of iOS 27.

The docs aren't clear, but since this was introduced in iOS26, I'm going to strongly assume the "compatibility" mode means disabling some assumptions in Liquid Glass that might be a problem if you haven't fully adopted it in your designs yet. The blast radius of that setting shouldn't be that wide.

Copy link
Contributor

@OS-pedrogustavobilro OS-pedrogustavobilro Feb 5, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense, not much to do for right now then, but hopefully soon heh

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, maybe we want to remove the storyboard and use very minimal SwiftUI in Cap 9 or 10?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we should call this a temporary workaround here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants