Thanks! That worked. Just to be super explicit about what I did in case any one else runs into this problem: Add a single new Localizable.strings file that is included in both the main app and the app clip Make sure that file is marked as localizable Run Export localizations again In my case, the resulting xcloc file now looks like: MainApp/ InfoPlist MainAppAppClip/ InfoPlist Shared/ Localizable Localizable contains all the strings from both targets

Thanks. I've opened FB12077893 For graphics, my app is using Scenekit, ARKit, MetalKit, MetalPerformanceShaders. As far as I know, we don't intentionally try to access any internal API Is there a way to figure out which framework is making this call? I tried adding a symbol breakpoint for the newPipelineLibraryWithFilePath function but it never gets hit

Some combination of updating to Xcode 14.3 and rebuilding my project (along with updating all packages) seems to have resolved this issue for me. It's still unclear how the reference to newPipelineLibraryWithFilePath was introduced or if it was simply a false positive

This requirement is a pain for AR apps as these don't run in the simulator. One possible workaround is to create images that aren't exact screenshots. For example, a graphic that features a screenshot prominently but also includes other graphic elements, such as explanation text and a background graphic. AFAIK this isn't against App Store guidelines so long as the screenshot is prominent, but your milage may vary for getting through review especially if the screenshots are obviously from a different format device For my AR apps, I usually build in functionality to capture just the AR content with all UI elements hidden. I then capture a few screenshots of the AR in action on a real device. Then I hack the app so it can run in the simulator, but in place of the actual AR content, I show one of the images I captured. That lets me create fairly authentic screenshots without having to own a huge number of old physical devices I really hope this requirement is relaxed though as it's quite burdensome if your app can't nicely run in the simulator