This bug or "feature" is still present in iOS 14.7 beta 3.

mailto:__@_?subject=Hello&body=11 (Accidentally missed the body)

iOS14 + iOS15beta2 only recognizes nopass, WEP, WPA, WPA2 or WPA/WPA2 within QR code You can check it using Hopper at: /Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot/System/Library/PrivateFrameworks/BarcodeSupport.framework

Dear Apple. Either update following documentation (remove conformance to RFC2368) https://developer.apple.com/library/archive/featuredarticles/iPhoneURLScheme_Reference/MailLinks/MailLinks.html#//apple_ref/doc/uid/TP40007899-CH4-SW1 or fix this annoying bug.

I am currently facing this issue.

I have the same problem - cannot generate promo codes. I also remember a day prior I accepted changes to the paid user agreement but it was flaky (it missed some steps). Nevertheless the status is I accepted it and got confirmation email. I have contacted support but so far they requested screenshots and steps to reproduce and sent it to technical team. Issue has been present since 29APR22

Can you open WEBP file from disk and add it to album?

Documentation: If the pixel density or color space of the destination graphics context changes, though, the image representation throws away any caches and executes the block again to obtain a new version of the image. While the NSCustomImageRep is of Generic RGB colorspace it doesn't produce any backing cgImage. Backing cgImage is only created when needed based on destination cgContext. XCode quicklook (bug?): <<CGColorSpace 0x600001288180> (kCGColorSpaceICCBased; kCGColorSpaceModelRGB; sRGB IEC61966-2.1)> Directly asking for cgImage <<CGColorSpace 0x600002935aa0> (kCGColorSpaceICCBased; kCGColorSpaceModelRGB; Color LCD)> If you use the method to resize an image and assign it to NSImageView it will display it correctly. For this reason I wouldn't recommend using NSImage drawingHandler to resize image. The only way is to set custom context inside the drawing handler) The image representation copies the block and stores it for later use. This is a huge memory waste if it's a bitmap image rep. E.g. you have 5000x5000 image hanging around in memory.

Xcode15 quicklook renders this as a one solid red color square on a P3 display, while the NSImageView displays it as a 2 different shades of red on a P3 display. let size = CGSize(width: 250, height: 250) let image = NSImage(size: size, flipped: false) { drawRect -> Bool in let rects = drawRect.divided(atDistance: drawRect.size.width/2, from: .minXEdge) NSColor(displayP3Red: 1.0, green: 0.0, blue: 0.0, alpha: 1.0).set ( ) NSBezierPath(rect: rects.slice).fill() NSColor(red: 1.0, green: 0.0, blue: 0.0, alpha: 1.0).set() NSBezierPath(rect: rects.remainder).fill() return true } imageView.image = image

Same issue is observed with TIFF

Same behaviour on 14.4.1. Not fixed.

Fixed in 14.5. However something has changed internally. Count of data bytes when compressing image with 0.1 compression factor: 14.5: 37393 14.4.1: 399845 14.2: 36408 12.7.4: 36409

My problem was daemon running in background Little Snitch . Kill it/disable it + turn off wifi u/Mareks-MacBook-Pro-M1 LaunchDaemons % ls -al /Library/LaunchDaemons  total 16 drwxr-xr-x   5 root  wheel   160 May 14 13:49 . drwxr-xr-x  71 root  wheel  2272 May 15 14:50 .. -rw-r--r--   1 root  wheel   621 Apr 20  2023 at.obdev.littlesnitch.daemon.plist lrwxr-xr-x   1 root  wheel   103 Dec 17  2022 com.oracle.java.Helper-Tool.plist -> /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Resources/com.oracle.java.Helper-Tool.plist -rw-r--r--   1 root  wheel   572 Jul  6  2022 com.xk72.charles.ProxyHelper.plist

You did your bindings wrongly. The KVO should be done on "indeterminate" instead of "isIndeterminate" progressIndicator.bind(.isIndeterminate, to: progress, withKeyPath: "indeterminate")

From WWDC 2015 Session 232 Best Practices for Progress Reporting: NSProgress properties are key value observable Add KVO observers to update your UI Not necessarily called on main thread. I wouldn't risk doing bindings as it might crash your app.