Post

Replies

Boosts

Views

Activity

Inconsistent ios app launch with same URL for app clips using NSUserAcitivty in AppDelegate
Before App Clips, our app (if installed) could be launched by scanning a QR code. In such a case, AppDelegate would call NSUserActivity with the payload and we would extract QR code data for parsing and actioning. After App Clip launched, the same behavior continued until recently (assuming before 14.4). Now, if the user has the app installed and they scan the QR code, they get the App Clip card to open the app. If the user taps on 'Open', the full app is launched. However, now the initial view controller launches before AppDelegate is able to receive and parse NSUserActivity data. This creates, I assume, some kind of a race condition where majority of the times initial root controller has malformed or no data. My understanding is that NSUserActivity is the best way to handle application launches so I am not sure how to properly address this problem versus writing some hacky workarounds. In our testing, we have noticed interesting situations where iOS would sometimes launch the full app without showing the app clip card (less frequently) and the full app would work fine. But majority of the times, it will show the app clip card and it would break our full app if it is installed. Our full app and app clip use the same domains (universal applinks) and we do the decision making based on URL params within the app. Basically, our applink is configured to be example.com and within both apps (i.e. full and app clip), we extract business_name=FOO and item_id=BAR within AppDelegate (where full URL might be: hxxps://example.com/Order?buiness_name=FOO&item_id=BAR. I am hoping someone can offer advice on how to solve/fix this problem.
0
0
590
Mar ’21
Notification settings for App Clip with SNS
As we understand that App Clips are embedded within a main application however we are not sure if we need to provide and setup another notification platform with SNS to allow notifications to be received. Our backend system is capable of distinguishing the SNS platform based on the token and application platform (e.g. ios-sandbox, ios-release) based on the APNS configuration we have stored within info.plist and configuration schemes. If we do need to setup another SNS platform for notification to be received, do we have to specify another configuration scheme and corresponding plist setting for App Clips or does it rely on the parent application. We believe that the parent app configuration scheme will be used for archiving the app and result setting up the wrong APNS endpoint. Moreover, do we need to call didReceiveRemoteNotification in AppDelegate to handle notifications? Are there any suggestions to handle this situation?
0
0
470
Dec ’20
App Compilation Errors with App Clips
We are integrating App Clips into our existing App. With Xcode12 beta, we are running to framework challenges with App Clips. See this post for the framework issues: https://developer.apple.com/forums/thread/652683. We have unblocked ourselves by deleting the entries under 'Other Linker Flags' and manually importing the frameworks into the project. However now our main app is refusing to compile on an actual device and throwing this error which is linked to the App Clip target: Target Integrity Building for iOS, but the embedded framework 'Alamofire.framework' was built for iOS Simulator. I have looked around and can't figure out how to get it to compile for the actual device. Any suggestions?
0
0
311
Jul ’20