Post not yet marked as solved
Exact same issue, and ran through the exact same steps. Got the "Install macOS Big Sur Beta" app (beta 9), but it fails when double-clicked with this alert: "This copy of the Install macOS Big Sur Beta application is damaged, and can‘t be used to install macOS."
I'd appreciate a comment from someone at Apple on how to update the DTK from 20A5299w to latest beta (currently 9), as there are all kinds of horror stories with bricked devices that I'd like to avoid (DFU modes, etc.). If there is a recommended procedure, please let us know so that we can get back to work. Thanks!
Just tested Xcode 12.0 beta 2 (12A6163b), same problem.
Exact same problem on Xcode 12.0 beta (12A6159). Fails very early in the target that uses an XCFramework, and I checked, there's no duplicate for that file (only referenced once). I suspect a bug in the build system.
My log for reference:
ProcessXCFramework /xxxxxxx/xxxxxxx.xcframework (in target 'xxxxxxx' from project 'xxxxxxx')
cd /xxxxxx
builtin-process-xcframework --xcframework /xxxxxxx/xxxxxxx.xcframework --platform ios --target-path /xxxxxxx/Build/Products/Debug-iphoneos
error: “xxxxxxx.h” couldn’t be copied to “Debug-iphoneos” because an item with the same name already exists. (in target 'xxxxxxx' from project 'xxxxxxx')
Post not yet marked as solved
in turn, virtualDeviceConstituentPhotoDeliveryEnabled is only supported with dual/virtual cameras, which is why I was asking this question in the first place. A virtual camera is not what I need, as they have limitations of their own (can't be fully controlled, can't shoot in RAW…), and I'm only interested in a single sensor data anyway.I guess this is a limitation of the current API. So please take my feedback (FB7377814) as a feature request. Note that use cases are real, and currently can only be implemented (without workaround) on other platforms. Thank you.
Post not yet marked as solved
Hi,it contains the image data, and the first 2 bytes are the red pixel, as a 16bit unsigned integer. Next is red, then green, etc.Min/max raw values are specified in the DNG dictionary (in particular, min is not 0). Note that there are also gains & other metadata, and you should setup a (pretty complex) chain to obtain accurate colors in a specific colorspace.Raphael
Post not yet marked as solved
This issue has been fixed in Mojave Beta 5 (18A347e). Initial message was posted when Beta 4 was the most recent version.
Post not yet marked as solved
For reference: I got the confirmation (via bug report) that this API is no longer supported as of 10.13 SDK. FBO should be used instead.
Post not yet marked as solved
Definitely. It makes sense that atomic changes in a zone is provoking failure to other clients trying to update data at the same time. Sure sounds like we don't have such granular iCloud-based APIs that enable implementing something similar to their iWork suite. Better off with other options for now.Thank you.
Post not yet marked as solved
Looks like Xcode 9b6 fixed that issue
