![]() ![]() I wonder if someone has some insight into why this might happen, and how to prevent it. I have received a few crash reports for my app "Find Any File" with an assertion failure as follows:Īssertion failure: "displayTiming != ((void *)0)" -> %lld I also tried replaceRegion and blitEncoder copyFromTexture: toTexture: as well as managed texture with syncing, but the result is always the same - only the first 22 pixels get filled and the rest is transparent. SaveOutputRaw(desc, surfPtr, getFileName("IOSurfaceTestCreateRaw")) SaveOutputRaw(desc, outBuf2.data(), getFileName("IOSurfaceTestCreateTex")) Id surfaceTex = Īuto region = MTLRegionMake2D(0, 0, w, h) Īuto bufSize = TextureDescriptor.storageMode = MTLStorageModeShared Īuto device = MTLCreateSystemDefaultDevice() age = MTLTextureUsageShaderRead | MTLTextureUsageShaderWrite MTLTextureDescriptor *textureDescriptor = [MTLTextureDescriptor texture2DDescriptorWithPixelFormat:CGMTLBufferManager::getMTLPixelFormat( fmt ) Now I want to create a MTLTexture based on the iosurface:Īuto fmt = IOSurfaceGetPixelFormat( ioSurface ) Īuto h = IOSurfaceGetHeight( ioSurface ) Īuto rowbytes = IOSurfaceGetBytesPerRow( ioSurface ) SaveOutputRaw(desc, surfPtr, getFileName("IOSurfaceTestSurfaceRaw")) extract raw surface data and write it into a file Memcpy(, src->getRawPtr(), src->getSizeInBytes()) Īuto surfPtr = (uint8_t*) I tested that the pixels are properly written into the iosurface: IOSurface *oSurface = initWithProperties:nsprops] Īuto ioSurface = (IOSurfaceRef) oSurface NSDictionary *nsprops = ( _bridge NSDictionary * )properties Properties, kIOSurfaceBytesPerRow, CFNumberCreate( kCFAllocatorDefault, kCFNumberIntType, &trowbytes ) ) Properties, kIOSurfacePixelFormat, CFNumberCreate( kCFAllocatorDefault, kCFNumberIntType, &pixelFmt ) ) Properties, kIOSurfaceHeight, CFNumberCreate( kCFAllocatorDefault, kCFNumberIntType, &height ) ) Properties, kIOSurfaceWidth, CFNumberCreate( kCFAllocatorDefault, kCFNumberIntType, &width ) ) KCFAllocatorDefault, 0, &kCFTypeDictionaryKe圜allBacks, &kCFTypeDictionaryValueCallBacks ) Int trowbytes = static_cast( ueRowbytes() ) // returns proper rowbytes valueĬFMutableDictionaryRef properties = CFDictionar圜reateMutable( I have this code to create an IOSurface from a bitmap image:Īuto src = loadSource32f() // rgba 32-bit float imageĬonst auto desc = src->getDescriptor() // metadata for that imageĪuto pixelFmt = CGMTLBufferManager::getCVPixelFormat( desc.channelBitDepth, desc.channelOrder ) // returns proper `RGfA` dlopen(/Volumes/workspace/TestProducts/Debug/.app/Contents/PlugIns/.xctest/Contents/MacOS/, 0x0109): tried: '/Volumes/workspace/TestProducts/Debug/' (no such file), '/Applications/Xcode.app/Contents/Developer/Platforms/atform/Developer/usr/lib/' (no such file), '/Volumes/workspace/TestProducts/Debug/.app/Contents/PlugIns/.xctest/Contents/MacOS/' (code signature in '/Volumes/workspace/TestProducts/Debug/.app/Contents/PlugIns/.xctest/Contents/MacOS/' not valid for use in process: mapped file has no Team ID and is not a platform binary (signed with custom identity or adhoc?)))) (Underlying Error: The bundle “” couldn’t be loaded. If you believe this error represents a bug, please attach the result bundle at /Volumes/workspace/resultbundle.xcresult. (.) encountered an error (Failed to load the test bundle. Here's the full error output, with and substituted for the actual: (It's using my developer account Team, and "Automatically manage signing".)Ĭan anyone relate the proper way to set up an XCTest scheme so that the tests will actually run in a Mac OS Xcode Cloud workflow? I'm using Xcode 14.0.1. I also tried changing the code signing certificate from "Development" to "Sign to run locally" to see if that made a difference, but I get the same error. So I created a duplicate scheme and set the build targets to Release - again I can run this fine locally (after creating a release build), but it fails with the same error in Xcode cloud. app bundle, I thought perhaps that was the problem (in case only the release app bundle actually gets built in the Xcode Cloud environment). I notice the XCTest target's scheme setup uses Debug builds and expects the test output to be in the Debug. When I run it locally from the IDE it works fine, either selecting the test scheme explicitly or as the test step of the app scheme. I am only running the unit test (XCTest) scheme, not the UI tests. There's also mention of a code signing error, but I have automatic code signing enabled with the same settings on test target as the app. Now I am trying to add a Test action the testing target builds but won't run, and the error indicates it can't find the testing bundle in the expected build output. ![]() I'm new to Xcode cloud - working with a Mac OS app, build is working great. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |