User Profile

Posts

Posts

Post not yet marked as solved
9 Replies
2.2k Views

Can't capture metal GPU workload — Capturing MTLPipelineLibrary is not supported.

I'm trying to debug my metal shaders in Xcode 14.2. However clicking "Capture metal GPU" while debugging recently started showing the following error: Capturing MTLPipelineLibrary is not supported. Unsupported method: -[MTLDevice newPipelineLibraryWithFilePath:error:] To enable capturing, disable calls to unsupported APIs and relaunch your application. I can't find any info about MTLPipelineLibrary or how to disable it. I've also confirmed that Metal GPU Frame Capture is enabled in my build What's causing this issue and how can I work around it so I can debug my shaders again?
Posted
by mattbierner.
Last updated
.
Post marked as solved
2 Replies
1.3k Views

Export localizations — Workflow for multiple targets that share strings?

I am trying to localize an iOS app that also ships an App Clip. The main app and the App Clip share many (but not all) of the same localizable strings. Using Product -> Export Localizations..., I can generate a .xcloc file that contains all the localizable strings found for each of these two targets. However this results in a large number of strings being duplicated. For example, if I have a file with Text("bla bla bla") that is included in both the main app and the app clip, the string bla bla bla appears twice in the xcloc: once under MyApp and once under MyAppAppClip What is the recommend workflow when you need to localize multiple targets that share strings? Ideally I'd like to be able to send a simple set of files off to the translation and then import the results without having to manually copy arounds strings. Do I need to split all the shared code out to a shared package instead of just including shared code files in both targets?
Posted
by mattbierner.
Last updated
.
Post not yet marked as solved
2 Replies
1.4k Views

AR App rejected for showing error screen about device not supporting AR

I have an AR app that relies on AR plane detection (ARWorldTrackingConfiguration). The app has been rejected by app store review three times due to 2.1: App Completeness. The specific problem seems to be that when ARWorldTrackingConfiguration is not supported on the current device, we show an informative error screen telling the user that their device is not supported. A few points: I have tested the app on all the physical hardware I have access to, from an iPhone 6s to an iPhone 11, and have never seen this error. I suspect it may have something to do with the test environment. However the reviewers refuse to provide any information about their test environment. This makes it impossible to investigating the issue. Secondly, our app needs support for ARWorldTrackingConfiguration. If ARWorldTrackingConfiguration is not supported, the best we can do is show an informative error screen to the user. There is no fallback experience we can offer. As far as I know, Apple does not provide an API to prevent the app from being installed on whatever device out there that do not support ARWorldTrackingConfiguration (we already list ARKit in the device dependencies). We've done the work to make sure the unsupported device experience is easy to understand and looks good. I have tried to explain all these points to the reviewer without success and basically with no feedback from them. What should my next steps be? File an appeal? Submit a video of the app in action and that tries to explain all this?
Posted
by mattbierner.
Last updated
.