Chris Marshall OK. We have managed to give our apps a URL Scheme, so they can be opened, using a simple URL. But we aren’t actually doing anything with the URL, besides starting the app.
We have also avoided doing any coding. Time to change things up, and get coding. It will be quite simple, and all the action will happen in the SimpleAppDelegate.swift file.
We have three URL schemes that we’ll be adding to our example apps. We don’t need to do anything with the Web server. Everything here will be done on the applications, themselves, in Xcode.
Before we move on to Universal Links, we’ll begin with setting up classic URL Schemes (Deep Links). These are fairly simple, and use most of the same hooks as Universal Links.
This series will walk through the steps needed to implement URL Schemes (Deep Links), and Universal Links in iOS/iPadOS apps (Using Standard UIKit App Delegate, UIKit Scene Delegate, and SwiftUI). This post is an introduction, and will establish our baseline.
Even though it may seem that this was a comprehensive treatment of the Swift Package Manager, it was really just a fairly basic introduction.
The examples were shallow and linear, and we didn’t even get into writing executable code in the package manifest files.
But we did learn enough to make the Swift Package Manager a useful and productive tool for our development work.
Here is the GitHub link to the PackageConsumer project Version 7.0.0. You can check out that version, and reproduce the results here.
In this example, we include a package, represented as a static library, that embeds a dylib, that embeds another static library (“dylib sandwich”).
This has the same issue as Example 3, where dynamic frameworks can present challenges, when using the Hardened Runtime.
Here is the GitHub link to the PackageConsumer project Version 6.0.0. You can check out that version, and reproduce the results here.
In this example, we include a package, represented as a dylib, that embeds another dylib, that embeds a static library.
This has the same issue as Example 3, where dynamic frameworks can present challenges, when using the Hardened Runtime.
Here is the GitHub link to the PackageConsumer project Version 5.0.0. You can check out that version, and reproduce the results here.
