I'm observing that when a silent push notification is sent to our app, is is started up in the background for 30 seconds before being suspended until the app is launched by the user. This causes data to persist from the silent push notification to the user app launch. I couldn't find documentation on this behavior for silent push notifications, and was wondering if it's possible to have the app terminate after handling the silent push notification. Is there documentation on the general flow of silent push notifications as well? I'm able to handle the edge cases if the app has to be suspended until user launch, but just want to confirm that this is the expected behavior before I go about handling it this way.

I'm working on developing an AASA for an app that may be built by multiple teams, and I want to create a universal link that opens the app regardless of which team's app is installed on iOS. Right now the AASA is { "applinks":{"apps":[],"details": [ {"paths":["/abc/*"],"appID":"TEAM1.BUNDLE_ID"}, {"paths":["/abc/*"],"appID":"TEAM2.BUNDLE_ID"}, ] } } The AASA works fine for TEAM1, but when the app is built with TEAM2, it does not work (instead redirects to the appstore). I checked the swcutil.txt and it confirms that the is indeed not linked to any domains when built from TEAM2. Is there a known fix for this, or a potential cause?