How should Full App handle URLs?

https://developer.apple.com/documentation/app_clips/configuring_the_launch_experience_of_your_app_clip

This document contains the following information.

Important

When users install the corresponding app for an App Clip, the full app replaces >the App Clip. Every invocation from that moment on launches the full app instead >of the App Clip. As a result, you must associate the full app with your website. >Additionally, the full app must handle all invocations and offer the same >functionality that the App Clip provides.

How exactly can we do?

The same Associate Domain is described in the entitlement of App Clips and Full App.


Q1. is it only the Bundle ID of the App Clips that should be listed in the AASA file?

For example,

XXXXXXXXXXXX.jp.awesomeapp.Clip

Only,

XXXXXXXXXXXXXX.jp.awesomeapp.

is not necessary?


Q2. Is it sufficient to use onContinueUserActivity for Full App to process URLs in the same way as App Clips?

Is the following correct?

App Clips:

@main
struct AwesomeAppClip: App {

    var body: some Scene {
        return WindowGroup {
            ContentView()
                .onContinueUserActivity(NSUserActivityTypeBrowsingWeb, perform: handleUserActivity)
        }
    }

Full App:

@main
struct AwesomeApp: App {

    var body: some Scene {
        return WindowGroup {
            ContentView()
                .onContinueUserActivity(NSUserActivityTypeBrowsingWeb, perform: handleUserActivity)
        }
    }

I also looked at the sample code, but it didn't look like Full App was responding to the URL.

https://github.com/apple-sample-code/FrutaBuildingAFeatureRichAppWithSwiftUI

Q1. You should list both the app and the app clip in their relevant places within the AASA file.

Q2. Yes, I'd expect that you would use the same .onContinueUserActivity approach in the main app as in the app clip.

Thanks!!

How can I test the full app? _XCAppClipURL does not seem to work unless it is an App Clip.

How should Full App handle URLs?
 
 
Q