• Apple troubleshooting guide
• Stackoverflow useful
• Stackoverflow getting error in validator

If the validator returns an error, curl the file

• In Terminal, curl -i https://arcascope.com/apple-app-site-association
• You should see: content-type: application/json
• If there’s no content-type for your aasa, this thread is very helpful

From that thread… first thing to try is: add this end of the .htaccess file: Header set Content-type "application/pkcs7-mime"

At Arcascope, we got it to work by adding this to .htaccess within /.well-known

RewriteEngine On
RewriteBase /.well-known/

# iOS
RewriteRule ^apple-app-site-association$ apple-app-site-association.json [NC,L]

The post Troubleshooting apple-app-site-association file appeared first on Forest and the Trees.

Universal linking allows url links to open an iOS app instead of opening the url in Safari.

Here are a few tutorials: Apple guide, older Apple guide, Kodeco.

Step 1: Create an apple-app-site-association file

• These are all over the internet: Square, Drizly, Alltrails, Arcascope, Apple
• There is an aasa validator which can be used to check the validity of your site’s aasa
• Aasas can be stored in root or in .well-known/ ← see Apple’s
• While the file cannot have a json suffix, it has to be of type json. To do that set the .htaccess file to..

<Files apple-app-site-association>
ForceType application/json
</Files>

• Apple’s documentation on creating the aasa file is helpful.
• Probably easiest to set “paths”: [”*”] initially (that will make all paths to your site open the app – more on this later)
• If your aasa file is not validating, here are some troubleshooting tips.

Step 2: Add the associated domains entitlement to your app

• Apple’s documentation on doing this is helpful. (Scroll down to find the info)
• Adding entitlements to the info.plist can be wonky. I ended up editing the entitlements file by hand. (yourApp.entitlements)
• At this point, make a build to your device or a sim. If you go to Safari and enter the url of the associated domain, you should go to the app.

Step 3: Setting the paths

• If you want the device to only go to your app for some urls, you need to edit the paths in apple-app-site-association file.
• The paths param specifies which url should open the app.
• The path must be a valid url. It needs to be visitable by a browser.
• Test, now you should only go to the app if you enter a url listed in paths.

Step 4: Deep linking

• By appending a query string to the url specified in paths, the app can retrieve the query string values and send the user to a specific part of the app.
• The Apple documentation on this is misleading as it only mentions modifying AppDelegate. If your app is in SwiftUI, it listen for events on top-level ContentView.

ContentView()
.onOpenURL {url in
	appState.handleUniversalLink(url: url)
}

• Once you have that working, it’s pretty easy to get the query params using URL and URLComponents. E.g. something like…

public func handleUniversalLink (url: URL) {
    let urlComponents = URLComponents(url: url, resolvingAgainstBaseURL: false)
    let queryItems = urlComponents?.queryItems
    guard let tabName = queryItems?.first(where: { $0.name == "tab" })?.value
    tabState.currentState = tabName
  }

In the above case, the url the user would tap would be something like: mydomain.com/thePathSpecifiedInTheAASAFile?tab=home

What about non-Safari browsers?

• Afaict, universal linking only works for Safari unless you want to spend money for Branch or do a bunch of work with Firebase Dynamic Links. (Here’s a link discussing using dynamic links – I have not tried the suggestions)
• None of the following apps open the app from Chrome or Firefox (iPhone running iOS16): Resy, Drizly, Amazon, or 1Password.
• I think the best solution is how Drizly does it, which is to put a link that reads “Open the app” on an html page listed in paths (e.g., myUniversalLinkPage.html). And that link goes to the same page (e.g. myUniversalLinkPage.html). If the user taps that link, the app will open. For whatever reason, that seems to work.

Finally, as part of figuring this out, it seems like Apple may eventually require apple-app-site-association files to be located in /.well-known

Again thanks to Arcascope for letting me publish this.

The post Universal Linking appeared first on Forest and the Trees.

To use your new color in your project, adding a color extension with the custom color’s name makes your life easier. Example below…

extension Color {
    static let myAwesomeClr = Color("theNameOfMyColorInAssets")
}

Then you can do things like…

Color(.myAwesomeClr)

If you want to include that color in a Package, you need to..

• Declare your extension public (like everything in a Package)
• Create a UIColor and cast that as a Color. (This took me a while to figure out which is why I am posting this.) See below…

public extension Color {
    static let myAwesomeClr = Color(UIColor(named: "theNameOfMyColorInAssets", in: .module, compatibleWith: nil)!)
}

• And, you need to add a resource target to your Package file…

let package = Package(
    name: "YourPackageName",
    
... some common package info here omitted for this example ....

    targets: [
        .target(
            name: "YourPackageName",
            dependencies: [],
            resources: [
                .process("Assets.xcassets"),
            ]
            ),
        .testTarget(
...  more code here ....

Where Assets is the name of the media file that has your color.

The post Asset Colors in Packages appeared first on Forest and the Trees.

I needed a way for a single view to show alerts with one button, with two buttons, and with two buttons and a destructive action (destructive actions are shown in red). I came up with a solution for Fasty, then I wanted to use it in another project, so I put it in a package.

To use:

1. Import the package
2. Add “@State private var alertParams: AlertParams?” to the view that you want to have the Alert.
3. At the bottom of that view, add: “.modifier(AlertModifier(alertParams: $alertParams))”
4. Add the following (or something similar) to the view: Button(“Pop up an alert with one button and an action”) { alertParams = AlertParams(title: “One Button”, message: “One button that calls an action”, primaryButtonLabel: “The button label”) { print(“The user clicked the Alert button”) } }

import SwiftUI
import AlertPopUp_iOS13

struct ContentView: View {
    @State private var alertParams: AlertParams?
    
    var body: some View {
        VStack {
            Button("Pop up an alert with one button and an action") {
                alertParams = AlertParams(title: "One Button", message: "One button that calls an action", primaryButtonLabel: "The button label") { print("The user clicked the Alert button") }
            }
        }
        .modifier(AlertModifier(alertParams: $alertParams))
        .padding()
    }
}

The readMe gives more details.

Here’s a sample project that uses the package.

The post Dynamic Alert Package for iOS 13 – 14 appeared first on Forest and the Trees.