There is no public API to get the serial number. That would be a massive privacy vulnerability. If your point-of-sale iPad devices are managed, then maybe you could push down an app-readable setting or file with each device’s own serial number. (But I’m no MDM expert.) Or worst case, you could manually provision each device by copy-and-paste from the Settings > General > About screen into your app. Hopefully this would satisfy the legal requirement.

JSONSerialization is not the right JSON API to use with Codable or for Swift-only types generally. It’s designed for older Objective-C types (NSDictionary, etc.) and can’t handle Swift struct types. Instead, use JSONEncoder with Swift types; see here.

Looks good, @App Store Connect Engineer. I’m able to downvote your reply above and report it for moderation. BTW, an unrelated issue: inserting an at-mention for your name doesn’t work right. If I hit the @ key it pops up a menu of thread participants as expected (you and @Claude31) but selecting your name results in just plain text in the final message as shown above.

Yep I can upvote yours. (And can un-upvote by just clicking the upvote button a 2nd time, removing the blue highlight.) But I think upvoting is free for everyone regardless of reputation points. They want the forum to be a happy place. :wink:

If an error is getting thrown, can you provide the exact error message? Or is something else going wrong? Just “it is broken” is not helpful for troubleshooting. And what do “before” and “now” mean in terms of OS version, Xcode version, anything else that may have changed? BTW, I tried out your code here (Xcode 14.3.1, iOS 17 simulator) and it actually works fine for me.

If you mean the order of keys is now different (and you aren’t using the sortedKeys output option) then see this thread for discussion of why that is. how do I revert to the previous JSONEncoder while using current OS & Xcode versions? You can’t. That class is built into the Foundation framework in the operating system. But one workaround could be to try the old JSONSerialization class. It’s not great with Swift but (when I tried this a while ago) you may get the old key ordering behavior, at least for now. (Or is your issue different from key ordering? It’s not clear from the original question.)

Can you give details of exactly which devices and sizes you are trying to upload, and exactly which screen size sections you are trying to upload them to, and exactly what the resulting error message is?

Just use the normal DateFormatter and you should get the new style in iOS 17. See this thread for more discussion.

You’ll probably get a gentle invitation to re-post this question in the user support forum, but on top of that: note the available emoji are defined in the Unicode standard which Apple simply uses. The Unicode Consortium presumably has some process for submitting feedback like this.

Looks like you encountered this known and reported bug.

Note that SCDisplay’s width and height properties are specified in points, while SCStreamConfiguration may expect width and height to be specified in pixels.

Is this the Xcode version I should install to work with macOS Ventura 14.6? Yes. What is the extension ".xip"? (See #3 in image above.) It’s a self extracting archive. After downloading, just double-click on the file and go grab a coffee.

try to avoid relying on the exact order of events @eskimo This could go with the topic of relying on undefined behavior that I proposed here.

See this thread for discussion of why you shouldn’t expect to find it. Why do you believe your project requires that exact version?

I can confirm your finding on iOS 17 and macOS Sonoma: JSONEncoder’s encoding of strings now stops at the first zero byte. It appears to be this bug which was introduced in the Swift rewrite of JSON encoding: JSONEncoder: Fixed escaping of certain strings. Since there’s no good workaround, is it feasible to change your blob encoding? Your current encoding scheme is pretty unusual. If you directly encode your image to JSON as a Data object, it uses base64 and just works.