Post

Replies

Boosts

Views

Activity

Reply to Support request regarding missing params in Redirect URL and inconsistent Universal Link behavior on iOS 18.4
Thanks for the reply and the explanation Quinn. Our issue wasn't specifically with authentication, like the original post, but just with loosing the query parameters. But this gives me a direction to discuss with our product team for how to handle these urls for the time being. Hope that a resolution can be found soon though. Thank you again.
Topic: Safari & Web SubTopic: General Tags:
Jul ’25
Reply to Universal link not working for multiple apps
I'm curious if it's the structure of the app site association file? 🤔 The structure was updated at some point, sorry I don't remember exactly when. https://developer.apple.com/documentation/xcode/supporting-associated-domains#Add-the-associated-domain-file-to-your-website Here's what it would look like with the current structure. I'm not entirely sure why it doesn't work with your current file, but maybe this might help. { "applinks":{ "details":[ { "appIDs": ["E5R4JF6D5K.com.demo.App1"], "components":[ { "/": "/app1/*" }, ] }, { "appIDs": ["E5R4JF6D5K.world.demo.App2"], "components": [ { "/": "/app2/*" }, ] } ] } }
Topic: App & System Services SubTopic: Core OS Tags:
Dec ’23
Reply to GenerateAssetSymbols wrongly renaming image assets
I am having this issue as well. I have tried to turn off that setting, but it does not work. Our asset catalog is in a Swift Package. I tried this in the package file, but it also doesn't work. It actually says that conditional statements like this don't have values. So I take that to mean that the absence of this flag would indicate that it is a NO. But that doesn't seem to be the case. swiftSettings: [ .define("ASSETCATALOG_COMPILER_GENERATE_ASSET_SYMBOLS=NO"), ] Am I trying to configure this wrong for the Swift Package? 🤔
Dec ’23
Reply to NSDiffableDataSourceSectionSnapshot with more than 80 sections causes UI hangs
Hi @Polyphonic, So, section.builds is an array. We have an array of all available builds. The first element in this array is the current build, and I want to highlight it as such. In that line it is grabbing the first item from the builds array and then mapping that to the SectionItem type. currentBuild itself is just a single item and not an array. I decided to restructure the Section type to remove this confusion. struct Section: Hashable { public let branch: String     public let currentBuild: Build     public let additionalBuilds: [Build] } // Updated snapshot code for the above type var snapshot = Snapshot() snapshot.appendSections(sections.map(\.branch)) apply(snapshot, animatingDifferences: animatingDifferences) sections.forEach { section in var sectionSnapshot = SectionSnapshot() let currentBuild = SectionItem.currentBuild(section.currentBuild)     sectionSnapshot.append([currentBuild]) if section.additionalBuilds.isEmpty == false { let additionalBuildsHeader = SectionItem.additionalBuildsHeader(forSection: section.branch) sectionSnapshot.append([additionalBuildsHeader]) let additionalBuilds = section.additionalBuilds.map({ SectionItem.additionalBuild($0) }) sectionSnapshot.append(additionalBuilds, to: additionalBuildsHeader) if expandedSections.contains(additionalBuildsHeader) { sectionSnapshot.expand([additionalBuildsHeader]) } } apply(sectionSnapshot, to: section.branch, animatingDifferences: animatingDifferences) } The issue is still present, however.
Topic: UI Frameworks SubTopic: UIKit Tags:
Jan ’23