happyfeet, Are you an Apple employee? Usually Apple people have a little Apple logo next to their name.

That feature can't be used by 3rd party apps on macOS.

Who told you that?

Rotated by how much? 27.6238 degrees? Or flipped? If you just need them flipped, you could create images or perhaps custom SF symbols and display them inline in a rich text view.

The only parts of Xcode that can't be moved to external storage are the parts that take up the bulk of your storage. You haven't said anything about your storage (internal or external) or your development needs, so I can't provide any more detailed information. In some cases, you can reduce Xcode's storage. You may be able to remove some or all of the simulator runtimes. Generally speaking, this is one of those cases where you have to weight the cost of your time and trouble against the cost of a computer with more internal storage.

Don't use the comment feature here in the forums. It's hides your response. Unfortunately, a 256 GB with Xcode is going to be a significant challenge. I've had problems with my 1 TB drive. One of the more problematic issues with Xcode are all the iOS simulator runtimes. Perhaps you could try to delete all of those except one. Or perhaps you could look into a cloud server. Sometimes those have small drives too. If you only need it for a couple of days, AWS might be more cost effective than a monthly fee.

You are only required to create an account once you reach $30k in revenue. You can always voluntarily register, which you would need to do in this case. The problem here is that Apple is the retailer and Apple handles all of the tax collection and remission to CRA. Apple wants to have its CRA account tied to your CRA account because of the commissions that Apple charges you. If you have further questions, I recommend contacting CRA directly. They're usually very helpful. Unfortunately, this kind of business arrangement is actually very unusual as businesses go. But Apple is large enough so that CRA will understand the business from your perspective and should be able to provide assistance. Unfortunately, the entire process of connecting your CRA account with Apple can take a long time. And since Apple is a US company, there are also IRS forms you'll have to fill out. All of these forms can take some time to fill out - think months, not days.

Git repos can be big source of this problem. But there's one more to check. Xcode projects actually consist of two parts - the project and the workspace. The source code integrations are based on the workspace. Xcode uses a shared workspace by default. But you can create a dedicated workspace file for your project and then just open that file instead of the project file.

Apple only provides the data documented by MapKit. And that data is subject to extremely restrictive licensing. It's better suited for a secondary data source, where you display your own data against an Apple Maps basemap. Apple's map data isn't unique in these respects. Any map data is subject to similarly restrictive licensing. I'm unaware of any data source for this kind of street-level data. That doesn't mean it doesn't exist, just that I don't know about it. Any company that has gone to the trouble of collecting this kind of detailed data is not going to provide it for free. And any company that's ever tried has quickly found out that the data is way more complicated than they anticipated. Google is able to leverage a large user base for Free Labour. Apple's trying a hybrid approach that clearly isn't working. When someone finds some data in your app that's wrong, it's your app that gets the 1-star review, not your data source. It's a real mine field. It's simply not something that any "indie" developer could ever manage.

Well what the F do they want me to name it? You can name it whatever you want. What is it you want me to learn here? Because you pose a giant riddle of name something that you should be given a name for... This looks like an exercise where you need to save multiple pieces of associated data based on some criteria. My friend said to me that this is a common thing you will have to do and they were right however... You have good taste in friends. What are you asking me to do? As the description says, "keep track of which kind of number was the largest". those are math terms from 20+ years ago Math is not the same as programming. It doesn't change. Technically they are math terms from "20+ years ago". They are concepts that are thousands of years old. The Fibonacci sequence is the newest of these. It was named over 800 years ago, but even then, was just a European discovery of a concept that had been known to non-Europeans for hundreds of years before that. But it's Europeans who typically impose their cultural nomenclature across science. I have no idea how to classify those terms... You aren't being asked to classify them. They're already classified. You're just being asked to identify the one that includes the largest number from the provided data. Are you asking me that? No. So why is that in the problem. I'm not sure what you're asking. Perhaps you should consult your friend again. They seem quite knowledgeable. These conundrums mixed in with legitimate problems honestly make me not want to learn Swift at all. This has absolutely nothing to do with Swift. This would be a legitimate exercise in any language. There are some interesting follow-on questions that would involve useful things to know about in Swift.

I see that too. Luckily, I only use the new QLThumbnailGenerator flow if the url has the "com.apple.icon.folder#S" extended attribute. I'm sure that's an "implementation detail", but still a good idea. Most folders display properly and immediately. It's only the folders that are customized using the new system that don't appear correctly.

This might be an older bug. I experienced this years ago. In addition to using the main thread, I even moved this method call to an XPC service. And then later, I added another crash-happy API call to my service as well.

How are you getting the icon otherwise? It's not quite "otherwise". Normally I just use "NSWorkspace.shared.icon(forFile:)". But folders require special logic. If the folder name has a "." prefix, then I call "NSWorkspace.shared.icon(for: .folder)". I'm not sure why. Probably should have commented that. But if the folder doesn't have a "." prefix, I use the standard "NSWorkspace.shared.icon(forFile:)". Then, I check to see if I need to do more. I the URL has the "com.apple.icon.folder#S" extended attribute, I try QLThumbnailGenerator. QLThumbnailGenerator is async anyway, so it really always requires the two-step process.

A non-empty folder results in an icon with paper sticking out on macOS Tahoe but an empty folder doesn't have the paper sticking out. Interesting. I didn't realize that. However, it doesn't seem to always work. I just now figured out that if the folder has a "." anywhere in the name, then it will display in the Finder as the old default, empty folder, even if it has contents. If you remove the "." then it will add the paper. And Finder has its way of being exempt from all of this, natch! But of course! Edit: This is strange. There's some kind of heuristics in the Finder. You can put a "." up towards the beginning of a folder name and it displays correctly. But if the "." is towards the end, then it reverts to the default folder appearance, losing any "modern" folder customization. Ironically enough, adding a "." doesn't affect the old folder icon customization method, which, from what I hear, is completely broken on Intel.

Just to clarify, "console" is Apple's UI for viewing data from the "unified logging system" and crash reports. If you want to localize a command-line tool using Apple's localization framework, then you must bundle it in an app. But you can directly run the executable in Contents/MacOS and it will run in the current localization. You can even supply: -AppleLanguages "(fr)" on the command line to force a specific language. All of this might only work if you are actually running a full user session and running the app in Terminal. If you are logging in remotely or something, all bets are off. That's a different environment and sometimes these things won't work. Some Apple command-line tools get around this by linking to bundled frameworks that are, themselves, localized. I guess you could to that too.