I did reproduce the issue in iOS 16.0 (simulator); the bug looks fixed in iOS 16.1 as the bug could not be reproduced in a simulator w/ this version and above.
It’s probably related to the shaders having their y axis inverted on iOS 16.0 too…
frizlab
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
From
Paris, France
Post
Replies
Boosts
Views
Activity
I have a workaround, but it clearly is a bug on Apple’s end.
I also filed a Feedback (FB13453227).
Bug filed: FB9733892
Tell me if there’s a better way, in the mean time, here’s a screen of the backtrace (nothing’s happening in thread 2).
The code is dead simple:
do {
logger.debug("Treating path \(p)")
var url = URL(fileURLWithPath: p)
let rv = try url.resourceValues(forKeys: [.ubiquitousItemIsExcludedFromSyncKey])
logger.info("Excluding \(p)")
var newRv = rv
newRv.ubiquitousItemIsExcludedFromSync = true
try url.setResourceValues(newRv) /* <- Hangs here */
} catch {
logger.error("Error treating path \(p): \(error)")
}
A possibly interesting note: it seems the ubiquitousItemIsExcludedFromSync value is never filled (it is nil after the resourceValues call)
Of course, never do that in prod. The code will break unexpectedly as soon as you start adding exotic locale…(For starter, the unit won’t pass the [A-Za-z/] regex.)