Depth of Field in iOS12 beta broken? - ios

I'm recieving an error when enabling Depth of Field with iOS12. Didn't have this error with iOS11.
validateComputeFunctionArguments:843: failed assertion `Compute Function(downsample_4x_dof): missing buffer binding at index 1 for outbuf[0].'

Related

Errors while trying to capture HDR content with DXGI OutputDuplication

I'm facing a strange error while trying to Duplicate Output on an HDR screen, particularly this is triggered when launching Doom Eternal.
I handle DXGI_ERROR_ACCESS_LOST error by resetting the OutputDuplication object, like so:
_session.Reset();
winrt::check_hresult(_item->DuplicateOutput1(_device.get(), // dxgi device
0, // reserved, must be zero
std::size(duplicationFormats), // number of supported formats
duplicationFormats, // pointer to array of supported formats
_session.GetAddressOf()));
_session is defined at class level, it's a WRL::ComPtr, duplicationFormats is an array with
DXGI_FORMAT_R16G16B16A16_FLOAT and DXGI_FORMAT_B8G8R8A8_UNORM (that, according to docs
should always be present).
With this setup, I can switch HDR modes at will on the display settings and desktop is always captured. However, when opening the game I got an E_INVALIDARG error, I activated DirectX debug Layer, and this message is printed when that happens (triggered by above check_hresult):
D3D11 ERROR: ID3D11Device::CreateTexture2D: Invalid format. The Format(0, UNKNOWN) is not supported as a D3D11_RESOURCE_MISC_SHARED_NTHANDLE format. [ STATE_CREATION ERROR #92: CREATETEXTURE2D_UNSUPPORTEDFORMAT]
D3D11 ERROR: ID3D11Device::CreateTexture2D: Returning E_INVALIDARG, meaning invalid parameters were passed. [ STATE_CREATION ERROR #104: CREATETEXTURE2D_INVALIDARG_RETURN]
I think it is rejecting the supported formats, even though I'm using a >10bpp format for HDR content, what surprises me is the mention of a (0, UNKNOWN) format, the texture is being created internally by DXGI implementation, as far as MS PDB can tell.

_validateTextureView:557: failed assertion `Texture View Validation cannot create View from Memoryless texture

Run Simulator in Xcode 13 beta, I came across the crash,What should I do about it ?
_validateTextureView:557: failed assertion `Texture View Validation
cannot create View from Memoryless texture.
texture usage (0x04) doesn't specify MTLTextureUsagePixelFormatView (0x10)
'
dyld4 config: DYLD_ROOT_PATH=/Users/****/Desktop/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot DYLD_LIBRARY_PATH=/Users/****/Library/Developer/Xcode/DerivedData/Truckloads-cpaazflnngvcgdegppomicvsczis/Build/Products/Debug-iphonesimulator:/Users/****/Desktop/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot/usr/lib/system/introspection DYLD_INSERT_LIBRARIES=/Users/****/Desktop/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot/usr/lib/libBacktraceRecording.dylib:/Users/****/Desktop/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot/usr/lib/libMainThreadChecker.dylib:/Users/****/Desktop/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot/Developer/Library/PrivateFrameworks/DTDDISupport.framework/libViewDebuggerSupport.dylib DYLD_FRAMEWORK_PATH=/Users/****/Library/Developer/Xcode/DerivedData/Truckloads-cpaazflnngvcgdegppomicvsczis/Build/Products/Debug-iphonesimulator
_validateTextureView:557: failed assertion `Texture View Validation
cannot create View from Memoryless texture.
texture usage (0x04) doesn't specify MTLTextureUsagePixelFormatView (0x10)
'
CoreSimulator 772.1 - Device: iPhone 12 Pro Max (84610676-549B-47F6-A87E-D0B4877032ED) - Runtime: iOS 15.0 (19A5261u) - DeviceType: iPhone 12 Pro Max
(lldb)
This worked for me.
You should be able to work around it by turning off Metal Validation in Scheme -> Edit Scheme -> Run -> Diagnostics -> Metal API Validation
From Apple: https://developer.apple.com/forums/thread/683832

Scrubbing does not work on playing a network stream video vlcj

We are having the same issue that is descibed here https://trac.videolan.org/vlc/ticket/4888
When we try to scrubbing the video, it does not work, vlcj is buffering every time we scrubbing and we are getting the errors logs below
[163bdd44] core input error: ES_OUT_SET_(GROUP_)PCR is called too late (pts_delay increased to 101 ms)
[163bdd44] core input error: ES_OUT_RESET_PCR called
[2403dc04] core vout display error: Failed to set on top
[164a8284] http access error: error: HTTP/1.1 500 Object not found
[5:56]
[15c5f1d4] core input error: input control fifo overflow, trashing type=3
Does anyone know if using a convention of VLC Configuration we can fix it ?
Thanks
Francisco

Map Kit Bad Instruction Error

I sent out a functioning test build of my app on to test flight. To remove some errors I did the following:
Turned off device orientation left and right
ticked requires full screen
and finally, replaced the valid app icons.
However, I noticed my label and background was missing from this test build so I opened it up in the simulator and received this error:
Thread 1: EXC_BAD_INSTRUCTION(code=EXC_1386_INVOP,subcode=0x0)
about the line:
let distanceSpan:CLLocationDegrees = 2000
MapView.setRegion(MKCoordinateRegionMakeWithDistance(CLLocationCoordinate2DMake(-39.0556253, 174.0752278), distanceSpan,distanceSpan), animated: true)
I have no idea what has caused this also in the output I got:
fatal error: unexpectedly found nil while unwrapping an Optional value
but I don't see where the optional value is? I have attached my code here
Any help is much appreciated.
Thanks

Meaning Of Different Status Codes In APNS Error Response Packets

APNS returns the following status codes in error response packets when using the enhanced notification format.
0 - No errors encountered
1 - Processing error
2 - Missing device token
3 - Missing topic
4 - Missing payload
5 - Invalid token size
6 - Invalid topic size
7 - Invalid payload size
8 - Invalid token
255 - None (unknown)
I want to know which of these status codes actually indicate that the issue is actually with the device token (ie: I can mark that particular device token in my database as invalid or inactive). I am sure that I can safely do that when I receive a value of 8 as status code. Also, I am pretty sure about what status codes 2, 4, 5 and 7 indicate and when exactly are they returned.
But for the rest of the status codes, I am pretty much in the dark. Apple's website does not contain much information about them either.
Can anybody please enlighten me about each of these status codes in detail. Many thanks in advance.
You're right about the 2, 4, 5, 7, and 8.
0 is good news obviously.
We're left with:
1 - Processing error
3 - Missing topic
6 - Invalid topic size
10 - Shutdown
255 - None (unknown)
1 is a problem on Apple's side, not related to the token.
3 is, according to Apple :
The topic is currently the bundle identifier of the target application on an iOS device.
6 is related to 3.
10 is out of your control but good to handle as well.
And obviously, 255 will not be able to help you define if the token is the problem.
If your goal is to determine a token that was valid at some point and no longer is, you should really refer to the Feedback Service API.

Resources