My understanding is if you are happy with your existing icons, and the way they look on iOS/macOS 26 - there is no need to change. I created an icon file for my existing icons and built with the latest Xcode 26.1RC: 5Mb was added to each app (which is significant if your existing app size is only 10Mb), iOS 18 icons looked wrong (appeared to be using the clear icon for the default), the end result on iOS/macOS 26 was visually the same as using my pre-existing (non glass) icons. So no useful benefit.

iOS 26.1 RC. Updated FB.

Partially resolved in iOS 26.1 Title is wrong color after an immediate change in Appearance, but is correct on re-display.

The code submitted is the entire project. Sorry - I don't have a spare device to try the beta.

iOS 26.0.1 iPadOS 26.0.1 XCode 26.0 (17A324) Worked fine with previous iOS versions.

Yes there is no checkbox - but where the arrow leads to is where you confirgure info.plist properties...

Confirmed the network scan occurs on the invocation of the Passwords App seven days after the previous scan.

Worked this out: iOS18 introduced [ASCredentialProviderViewController prepareInterfaceForUserChoosingTextToInsert] and [ASCredentialProviderExtensionContext completeRequestWithTextToInsert:completionHandler] To insert user selected text from a 3rd party credential provider. This is the interface required to satisfy such requests. If it doesn't exist and your credential provider is the only one selected you will see that message.

I've seen this dialog too with my password management app, and don't understand why it appears. The message indicates the developer needs to do some work to resolve the issue. What is it?

HI I'm having the same issue - and same need. Ideally I would like to link the file so the app extension can access it. But if I have to - a copy is ok.

OK - this was unexpected: the quicktype bar started working some time after using Safari for a couple of hours.

Same problem for me - with an app extension. To change anything (including the version), I need to use XCode 14. This needs to be fixed!

Resolved in Safari 16.5 supplied with macOS Ventura 13.4.

Ventura and XCode 14.3 is working!

who -b