Hello Argun, thanks for the response. Well the issue is its not documented anywhere that these statuses can not be checked on the main thread. I will try pushing them to background thread. But what about checking (AVAudioSession.sharedInstance().category == .playback) giving error Hangs - Interprocess communication on the main thread can cause non-deterministic delays. ?

Only solution is to undo all stitchable kernels and go back to extern "C" kernels. Irritating and involves too much work if you have hundreds of Kernels.

But I have gestures on separate views in this case, I don't know how to adapt this solution.

That requires modifying hundreds of CI kernel methods, not a good workaround.

VPP users ARE facing issues I can confirm.

I have recently migrated to freemium model and can confirm that I am only getting build version (not app version). So I have set the build version to a high number like 11 and it works. Original purchase date also seems to be working, though I am getting some 2013 users but my app has been around since 2012. My own device through which I bought the app reports 2018, which seems correct.

I think it is best to avoid using originalAppversion and instead use originalPurchaseDate.

Did you find an answer to this?

Hello @App Store Commerce Engineer Can you please confirm whether AppTransaction.originalAppVersion field will be present for users who purchased the app previously using VPP? Or is this field only present for normal purchases only?

I believe originalAppVersion should be present in the AppTransaction, no matter the type of purchase. Only Apple Engineers can verify this, but I can only know once I push my update in the coming few weeks.

Hello @gchiste , yes the hardware cost comes to be 1.5 for simple ProRes 1080p@30 fps video. So it would not work for ProRes. But even for non-ProRes presets such as YcbCr420 10 bit where it works, there are frame drops when using 4K@60 fps activeFormat and using AVAssetWriter to encode. This happens even if you merely add preview video data output and do zero processing on the buffers delivered for preview (just a return statement in captureOutput delegate).

Was it resolved? I can not add the same flag in XCode 15.

@Frameworks Engineer Ok I undertstand color conversion needs to be done, but is there a way for 32-bit floating point format accomadate 10 bit integer format pixel format for histogram calculation? Or the 10-bit would need to be converted to 32-bit Floating point format first.

@Frameworks Engineer Thanks a lot, though I see the API only works for iPhone 15 family, not earlier devices.

The plist itself is type CFData in this case. Nothing works as I said, including the second code sample I posted in the question where I simply copy and paste the attachment from source sample buffer. Feel free to modify and post the sample code you think should work.