Posts

Post not yet marked as solved
4 Replies
1.6k Views
Hi, I'm building an ARKit app that requires BodyTracking which in turn requires an A12 chip. I though I'd use the iphone-ipad-minimum-performance-a12 device capability option to prevent the app from being used on incompatible devices. However, adding the option fails XCode installations to my iPhone XS and latest iPad Pro with the message "<App name> requires the “iphone-ipad-minimum-performance-a12” capability which is not supported by <device>" when the XS and Pro are clearly A12 and above devices? I require iOS 13.5 so it's not a too low iOS version causing it. Any thoughts? Cheers, Kristoffer
Posted Last updated
.
Post not yet marked as solved
0 Replies
437 Views
Hi,With the latest iOS version 13.1, did the resolution of the currentDrawable texture change?I don't recall the exact resolution it used to be, but all of the sudden the texture is reported as 5275x520 on my iPhone XS.Anyone else seing this? Or is it expected? I'm reading the final rendered image as part of a command buffer completion handler:id<MTLTexture> drawableTexture = _renderDestination.currentDrawable.texture;[commandBuffer addCompletedHandler:^(id<MTLCommandBuffer> buffer) { dispatch_semaphore_signal(block_sema); //do stuff with drawableTexture here}];Prior to updating to 13.1 the resulting texture looked fine. The render destination provider is an MTKView with framebufferOnly set to NO.Update: I checked the resolution on two non iOS 13.1 devices and the currentDrawable texture resolution matches the screen resolution as expected so it seems ios 13.1 related.Cheers,Kristoffer
Posted Last updated
.