Post

Replies

Boosts

Views

Activity

Reply to Group AppIntents’ Searchable DynamicOptionsProvider in Sections
Btw, I’ve learned now that it is not necessary to use a DynamicOptionsProvider for sections. It’s also possible to return an ItemCollection for the regular EntityQuery. When doing so, you need to return item collections for all returning functions except the entities(for identifiers: [UUID]) function. struct MyIntentQuery: EntityStringQuery { func entities(for identifiers: [UUID]) async throws -> [MyIntentEntity] { // Return fetched entities by ID } func suggestedEntities() async throws -> ItemCollection<MyIntentEntity> { // Get All Data let allData = try IntentsDataHandler.shared.getEntities() // Create Arrays for Sections let fooEntities = allData.filter { $0.type == .foo } let barEntities = allData.filter { $0.type == .bar } return ItemCollection(sections: [ ItemSection("Foo", items: fooEntities), ItemSection("Bar", items: barEntities) ]) } func entities(matching string: String) async throws -> ItemCollection<MyIntentEntity> { // Get All Data let allData = try IntentsDataHandler.shared.getEntities() // Create Arrays for Sections let fooEntities = allData.filter { $0.type == .foo && $0.title.localizedCaseInsensitiveContains(string)) } let barEntities = allData.filter { $0.type == .bar && $0.title.localizedCaseInsensitiveContains(string)) } return ItemCollection(sections: [ ItemSection("Foo", items: fooEntities), ItemSection("Bar", items: barEntities) ]) } }
Topic: Machine Learning & AI SubTopic: General Tags:
3w
Reply to Performance considerations using ViewThatFits
Thanks a lot for your comment and things to consider! 🙏 I use that for different cases already – from small large text tweaks to custom grid layouts that change depending on window size – so I’ll check out the alternatives and see if it makes sense to switch.
Topic: SwiftUI SubTopic:
SwiftUI Q&A
Jun ’26
Reply to Using .glassEffect in Charts
Liquid glass should mainly be used on UI control elements that sit above the content. Also, currently, there's no dedicated support for liquid glass effects in Charts. It's a good idea to file enhancement requests with design justification and mock-ups. I understand that currently there’s no support for Liquid Glass in Swift Charts. Especially for actual chart elements I can see the reasoning behind it. Nevertheless, it’s quite a bummer that it isn’t supported for .annotation. I have a selection lollipop that bubbles up above the chart when the user interacts with the chart. As this is literally floating in front of the chart it would be great to add some glass effect to the container view (a HStack) of my annotation. I’ve already filed a feedback for specifically that (FB19110760). Feel free to join me with a dupe or for Apple check it out.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
May ’26
Reply to Icon Composer icons together with iOS 18 icons
As posted in the other thread Steve4442 linked to: The way to go is the following (as John Siracusa) noted on Mastodon: Name your Tahoe .icon file the same as the name of your existing .appiconset in the Assets catalog. Set the ASSETCATALOG_OTHER_FLAGS build setting to: --enable-icon-stack-fallback-generation=disabled I can confirm that the Asset Catalog Other Flags still works with Xcode 26 RC! I’ve submitted two apps with that flag and both got approved by Apple. The App Store even displays the old icon in the iOS/macOS 18 App Store and the new icon in the iOS/macOS 26 App Store. You can see an example here in one of my apps.
Sep ’25
Reply to Icon Composer: Any way to add icons to the app bundle for older macOS versions?
Just want to confirm that the Asset Catalog Other Flags still works with Xcode 26 RC! I’ve submitted two apps with that flag and both got approved by Apple. The App Store even displays the old icon in the iOS/macOS 18 App Store and the new icon in the iOS/macOS 26 App Store. You can see an example here in one of my apps. So, to summarize in John Siracusa’s words again: Name your Tahoe .icon file the same as the name of your existing .appiconset in the Assets catalog. Set the ASSETCATALOG_OTHER_FLAGS build setting to: --enable-icon-stack-fallback-generation=disabled
Sep ’25
Reply to What can trigger "App uses the itms-services URL scheme to install an app" rejection?
I had the same issue recently. The problem was that my project readme.md had an example URL that started with itms-services:// (used from the Testing promoted In-App Purchases guide). I never used or initialized any of this in the actual code, though! It must have been an automatic check by Apple that triggered that. So, to solve that issue I just had to make sure that the readme was not included in the actual build files (by removing all target memberships) – which is probably a good idea anyway. 😅 Not it’s working for me. Tl;dr: Search for itms in all project files and see if you can hunt down the place where it’s mentioned.
Apr ’25
Reply to Group AppIntents’ Searchable DynamicOptionsProvider in Sections
Btw, I’ve learned now that it is not necessary to use a DynamicOptionsProvider for sections. It’s also possible to return an ItemCollection for the regular EntityQuery. When doing so, you need to return item collections for all returning functions except the entities(for identifiers: [UUID]) function. struct MyIntentQuery: EntityStringQuery { func entities(for identifiers: [UUID]) async throws -> [MyIntentEntity] { // Return fetched entities by ID } func suggestedEntities() async throws -> ItemCollection<MyIntentEntity> { // Get All Data let allData = try IntentsDataHandler.shared.getEntities() // Create Arrays for Sections let fooEntities = allData.filter { $0.type == .foo } let barEntities = allData.filter { $0.type == .bar } return ItemCollection(sections: [ ItemSection("Foo", items: fooEntities), ItemSection("Bar", items: barEntities) ]) } func entities(matching string: String) async throws -> ItemCollection<MyIntentEntity> { // Get All Data let allData = try IntentsDataHandler.shared.getEntities() // Create Arrays for Sections let fooEntities = allData.filter { $0.type == .foo && $0.title.localizedCaseInsensitiveContains(string)) } let barEntities = allData.filter { $0.type == .bar && $0.title.localizedCaseInsensitiveContains(string)) } return ItemCollection(sections: [ ItemSection("Foo", items: fooEntities), ItemSection("Bar", items: barEntities) ]) } }
Topic: Machine Learning & AI SubTopic: General Tags:
Replies
Boosts
Views
Activity
3w
Reply to Use ShowInAppSearchResultsIntent with custom Parameters
The issue has been resolved with iOS 27 beta 3. Thanks!
Topic: App Intents SubTopic:
App Intents & Siri Q&A
Replies
Boosts
Views
Activity
Jul ’26
Reply to Using EntityPropertyQuery with SwiftData
I haven’t tested it myself, but as mentioned in this Forums post, the new Predicate(all:) initializer should be ideal for that!
Topic: App Intents SubTopic:
App Intents & Siri Q&A
Replies
Boosts
Views
Activity
Jun ’26
Reply to Performance considerations using ViewThatFits
Thanks a lot for your comment and things to consider! 🙏 I use that for different cases already – from small large text tweaks to custom grid layouts that change depending on window size – so I’ll check out the alternatives and see if it makes sense to switch.
Topic: SwiftUI SubTopic:
SwiftUI Q&A
Replies
Boosts
Views
Activity
Jun ’26
Reply to Use ShowInAppSearchResultsIntent with custom Parameters
@Frameworks Engineer Alright, I’ve created a feedback for this with a sample project: FB23045879
Topic: App Intents SubTopic:
App Intents & Siri Q&A
Replies
Boosts
Views
Activity
Jun ’26
Reply to Group AppIntents’ Searchable DynamicOptionsProvider in Sections
Checking back on that it seems to be working as expected in iOS 26. At least I get the sections now. 👍
Topic: Machine Learning & AI SubTopic: General Tags:
Replies
Boosts
Views
Activity
Jun ’26
Reply to Using .glassEffect in Charts
Liquid glass should mainly be used on UI control elements that sit above the content. Also, currently, there's no dedicated support for liquid glass effects in Charts. It's a good idea to file enhancement requests with design justification and mock-ups. I understand that currently there’s no support for Liquid Glass in Swift Charts. Especially for actual chart elements I can see the reasoning behind it. Nevertheless, it’s quite a bummer that it isn’t supported for .annotation. I have a selection lollipop that bubbles up above the chart when the user interacts with the chart. As this is literally floating in front of the chart it would be great to add some glass effect to the container view (a HStack) of my annotation. I’ve already filed a feedback for specifically that (FB19110760). Feel free to join me with a dupe or for Apple check it out.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
May ’26
Reply to SwiftUI Button with Image view label has smaller hit target
Thanks for the tip to avoid this. Just tested it with iPadOS 26.6 beta 1 and it still is an issue. 😕
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
May ’26
Reply to Xcode 26 SDK/Simulator Download Issue: (-67061 invalid signature (code or signature have been modified)
This issue has been solved with the Xcode 26 RC and also the App Store version.
Replies
Boosts
Views
Activity
Sep ’25
Reply to Icon Composer icons together with iOS 18 icons
As posted in the other thread Steve4442 linked to: The way to go is the following (as John Siracusa) noted on Mastodon: Name your Tahoe .icon file the same as the name of your existing .appiconset in the Assets catalog. Set the ASSETCATALOG_OTHER_FLAGS build setting to: --enable-icon-stack-fallback-generation=disabled I can confirm that the Asset Catalog Other Flags still works with Xcode 26 RC! I’ve submitted two apps with that flag and both got approved by Apple. The App Store even displays the old icon in the iOS/macOS 18 App Store and the new icon in the iOS/macOS 26 App Store. You can see an example here in one of my apps.
Replies
Boosts
Views
Activity
Sep ’25
Reply to Icon Composer: Any way to add icons to the app bundle for older macOS versions?
Just want to confirm that the Asset Catalog Other Flags still works with Xcode 26 RC! I’ve submitted two apps with that flag and both got approved by Apple. The App Store even displays the old icon in the iOS/macOS 18 App Store and the new icon in the iOS/macOS 26 App Store. You can see an example here in one of my apps. So, to summarize in John Siracusa’s words again: Name your Tahoe .icon file the same as the name of your existing .appiconset in the Assets catalog. Set the ASSETCATALOG_OTHER_FLAGS build setting to: --enable-icon-stack-fallback-generation=disabled
Replies
Boosts
Views
Activity
Sep ’25
Reply to iOS26 - ITMS-90717: Invalid large app icon
Check out this other thread and the suggestion to disable blur effects. That helped for me. More information here: https://developer.apple.com/forums/thread/795411?answerId=855239022#855239022
Replies
Boosts
Views
Activity
Sep ’25
Reply to Xcode 26 SDK/Simulator Download Issue: (-67061 invalid signature (code or signature have been modified)
I’ve just tested it with Xcode 26 beta 7 and I get the same issue!
Replies
Boosts
Views
Activity
Aug ’25
Reply to What can trigger "App uses the itms-services URL scheme to install an app" rejection?
I had the same issue recently. The problem was that my project readme.md had an example URL that started with itms-services:// (used from the Testing promoted In-App Purchases guide). I never used or initialized any of this in the actual code, though! It must have been an automatic check by Apple that triggered that. So, to solve that issue I just had to make sure that the readme was not included in the actual build files (by removing all target memberships) – which is probably a good idea anyway. 😅 Not it’s working for me. Tl;dr: Search for itms in all project files and see if you can hunt down the place where it’s mentioned.
Replies
Boosts
Views
Activity
Apr ’25
Reply to iPadOS 18 TabView with Large Navigation Title
For those wondering why not to wrap the whole TabView in a NavigationStack, this leads to weird results. This places the whole toolbar below the title. Also the button to toggle the sidebar is placed below the title instead of above:
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Jan ’25