I’m not seeing any change. The little square next to Sort by: Newest (instead of the usual down arrow) suggests your browser is using the wrong font for some reason, rather than being a deliberate change. I’m seeing the usual correct font everywhere in Safari 16.3 on macOS 13.2.1. Ha... after I posted that reply, then when returning to the main page I got the incorrect font too as shown in the picture. Then after logging out and back in, the fonts are correct again. Maybe just a sporadic server issue.

Seems to be connected to your Mac’s keyboard mapping. That’s a U+00AC NOT SIGN character (in Unicode terms) which is mapped to Option+L on the U.S. English keyboard layout. And I see that Option+L is how you type the @ sign on the German keyboard layout. Trying typing Shift+2 which is how to get the @ sign on U.S. English. Could be a bug, or maybe there’s a setting to control this. The simulator does have a menu option for Use the Same Keyboard Language as macOS.

It’s still confusing to figure out exactly what you’re doing. I'm assuming my app is actually supposed to be on the simulator You need to run the app on either the simulator or on real devices. You are the developer of the app, right? So you have the source code and can build it in Xcode? Then from Xcode you should be able to launch the app to run on the simulator or on a connected iPhone or iPad. Then you can operate the app just like a real user until you get to the screens you want to capture pictures of. so that I don't have to go through safari to access it. What does that mean exactly? What URL do you enter into Safari? how do I take my app from my app store connect page and make sure it is on the Xcode simulator You don’t get anything from App Store Connect. You are the one supplying the app and the screenshots to App Store Connect. Xcode does the uploading of the app itself, and you generate the screenshots and upload them via the App Store Connect web interface. Or... are you developing your app using a 3rd party development tool (not Xcode)? That could have a different workflow for launching the app in the simulator. If so, please clarify what you are using and maybe someone will have some advice.

Interesting utility there. My first advice would be to just remove it. Does your project actually suffer the sort of merge conflicts that xUnique claims to address? It mentions conflicts due to the same file being added on different machines, but that sounds like a larger process problem. There are definitely lots of large teams and large apps that get by fine using robust branching strategies and plain old Xcode. Or if you do still need it, then you probably need to modify xUnique to sort the way Xcode now does. Maybe see if the original author still plans to maintain it even after all these years.

Here’s a good WWDC presentation for getting started: Developing CarPlay Systems, Part 1.

do we need to update our "Minimum Deployment Target" to 16.1? Definitely not. You need to use Xcode 14.1 or later but can still target as far back as iOS 11.

Our project files are sorted alphabetically. It’s not clear what you mean: are you just manually sorting the files in your target’s Build Phases → Compile Sources list in Xcode? By my experiment in 14.2, hand sorting that list still works correctly and persists as expected. Or are you modifying the underlying .pbxproj file outside of Xcode? I imagine Apple’s response would be something like: don’t do that because it’s not supported. I suspect the latter since your screenshot shows the PBXBuildFile section of the project file. That’s not the section that defines the order of the user-visible Compile Sources list. If you don’t modify the project file outside of Xcode, do you still experience unwanted changes to the file every time it is opened?

Also, standard practice is that type names start with a capital letter and all other names start with a lowercase letter: static let defaultLocation = CLLocationCoordinate2D( /* ... */ ) // ^

We generally don’t answer “why” questions @eskimo That could be a candidate for tip 3 in Quinn’s Top Fourteen DevForums Tips.

But why exactly do you need Rosetta on simulator? Is it due to a 3rd party framework that doesn’t yet have an ARM slice for simulator? If so, the right solution is to get that 3rd party vendor to update their framework. Easier said than done, of course. ours is an enterprise project that uses video and audio calling My company’s app has this exact problem due to a framework from the vendor of very well-known video conferencing app (maybe the same one). A workaround that works for many of us is to add a local no-op stub for the framework classes are missing on simulator. (You add the minimum needed to eliminate linker errors.) This lets the app build, and is sufficient for those of us who don’t actually need to use the functional area of the app that uses that particular framework. Maybe this trick could work for you too.

Old versions including 11.3.1 are available, but you may need a full paid developer account to access them. If you do have access, here’s the link.

"com.example.GettingStarted" cannot be registered to your development team Are you using the actual bundle prefix com.example or are you just redacting your real domain name in order to post the question in the forum?

Question A: Is there an existing API call or data type that allows me to pass in a class object and returns all the byte data ? I don’t actually know, but consider a case where an object does reference other objects. Does “all the byte data” mean you want to capture the entire object graph? That’s not necessarily what you really want. Question B: If question A is no, could you recommend/suggest a way to achieve this? Sounds like you just need a serialization scheme to convert an object to a byte stream. Grabbing the underlying bytes via Data(bytes:count:) is one way of course, but you could also implement a custom scheme to explicitly serialize all the object properties you need. Then I’m guessing that however you generate a byte stream representing an object, the fun part is that you are using XOR to diff successive entries in your undo stack and storing these diffs efficiently, probably taking advantage of the diffs containing a lot of 0x00 bytes. Is that the idea? If so, then any serialization scheme that produces the desired behavior should work.

Note that your struct needs to conform to Decodable in order to use JSONDecoder, like this: struct Vinyl: Decodable { // assuming the same name as in your 2019 Stack Overflow post And you should definitely switch if possible to Decodable and JSONDecoder as shown by @Claude31. Consider JSONSerialization unofficially deprecated for Swift. Now as for this issue in the original code: But it can't get through the line of the if let localData statement. I don't know why. The “don’t know why” is due to using try? which silently eats any error thrown by the JSONSerialization.jsonObject() call. If you change it to regular try and enclose it in a do / catch block, then the error it catches will tell you exactly what the problem is.

You should treat Xcode like any other Apple product: :warning: No user serviceable parts inside. What are you trying to accomplish?