it looks like iOS 17 was treating .ascii as a synonym for .isoLatin1 [and now it isn't] That's going a bite a few people, isn't it! Was that mentioned in the release notes?

what is the recommendation to be informed about the status of a problem Run some test code to determine whether the problem still exists.

I believe there is no way to get the extra padding info. Yes I filed a bug ha ha ha. In principle you could render the UIImage into a graphics context and then create your SKTexture from that. Do you actually care about accurate typographic alignment of your symbol? If not, just use what you have. I know nothing about the colour issues you have mentioned.

UIImage and CGImage have different aspect ratios for SF Symbols, due to padding. Have a look at this thread: https://developer.apple.com/forums/thread/716773 It wouldn’t surprise me if SKTexture does the same thing.

I don't believe there is an API to get this directly. You need to get the model, i.e. the "iPad13,2" string, and look that up in a table. Get the model by calling uname() and looking in the machine field of the result.

It's interesting that the error says Vec4, not 3, isn't it?

Are you saying that you've called CGImageGetColorSpace(sourceCGImage) and it correctly reports that the image is CMYK?

How can I validate a phone number that can't be reached directly? You can't. In the end, I bought a "burner phone", used it once to get the code by text, and then discarded it.

I didn't realize that User Defaults contained anything other than the data I write to it. Isn't it strange that Apple chose to add this peculiar "required reason" thing, rather than just fixing NSUserDefaults to do what you and I always thought it did? Maybe it's time to reconsider using UserDefaults at all. Yes, this. The only essential feature of NSUserDefaults is when you implement a Settings.bundle to make your settings appear in the Settings app. (Which, bizarrely, is not covered by any of the reason codes - so you have to lie in your privacy manifest if you use that.) Otherwise, just store your data in the filesystem and avoid all this agro.

FB15090356 Anyway... does anyone else see this?

IAP Apple ID, transaction Ids, How would I get transaction IDs?

I directly want to use them in c++ as swift::UnsafeMutablePointer. Why? If it's not true what documentation mean, then what is the manifestation for exposing these UnsafeMutablePointer? We’ve already answered that, it’s just T* I guess you could write: namespace swift { template <typename T> using UnsafeMutablePointer = T*; };

Can you Explain what does this mean? If you want, file a bug against the docs asking for that page to be explicit about how those pointer types map. The answer, as mentioned above, is that the Swift mutable pointer types map to * and the immutable pointer types map to const *.

Are you trying to implement a singleton?

Is it not simply: swift::Int* x = Interop::GetPointer(); ? (That's just a guess, I've never used this. But I think the whole point of "unsafe mutable pointer" is that it's Swift's way of spelling "*".)