@DTS Engineer Just want to highlight that I could see below error/warning in Console area when app clip is running using Xcode 12 Beta 5
2020-08-26 15:34:38.030645+0530 MyAppClip[40692:290645] [connection] nw_proxy_resolver_create_parsed_array [C1 proxy pac] Evaluation error: NSURLErrorDomain: -1003
2020-08-26 15:34:38.072669+0530 MyAppClip[40692:290645] [] nw_protocol_get_quic_image_block_invoke dlopen libquic failed
2020-08-26 15:34:39.996914+0530 MyAppClip[40692:290644] [connection] nw_proxy_resolver_create_parsed_array [C2 proxy pac] Evaluation error: NSURLErrorDomain: -1003
2020-08-26 15:34:40.152378+0530 MyAppClip[40692:290123] [plugin] AddInstanceForFactory: No factory registered for id <CFUUID 0x60000132e140> F8BB1C28-BAE8-11D6-9C31-00039315CD46
2020-08-26 15:34:40.338279+0530 MyAppClip[40692:290123] Metal API Validation Enabled
2020-08-26 15:34:40.813305+0530 MyAppClip[40692:290123] libMobileGestalt MobileGestalt.c:1736: Could not retrieve region info
Even though its not impacting app clip, just want to know whether we can ignore them?
Post
Replies
Boosts
Views
Activity
@DTS Engineer This issue is fixed in Xcode 12 beta 5. Now UI is rendered instantly without any delay.
As you mentioned App Clips have different target, it can not be signed with same provisioning profile as the main app. This is because App Clip target will have separate bundle identifier than your main app, mostly it will have ".Clip" as suffix.
e.g. if you main application's bundle identifier is com.example.app then app clip bundle identifier will be com.example.app.Clip
Do you initialise an audio device once your data comes back? Maybe by using an object from AVFoundation? We do not use initialise an audio device or AVFoundation.