They promise 2 days That's just boilerplate on any Apple e-mail. It's never 2 days. Here I am, literally trying to give them my money How is it possible for a trillion-dollar company to make something as simple as accepting payment so infuriatingly difficult? I'm sure it has nothing to do with accepting your payment. Apple's got that down. The problem is giving you access to Apple's app installation infrastructure and Apple's 1+ billion user base. Apple doesn't need your $99. But Apple does want to protect that user base. Scams and frauds are epidemics these days and Apple is target #1 in the world. I've tried everything - even set up a whole separate account That probably didn't help.

Despite Xcode being the one and most used IDE for iOS, it is far from perfect No one ever said it was. People use Xcode to write apps for Apple's market, not because they like Xcode. I have used many tools in my career Perhaps that's the problem. Xcode is currently at version 16.2, and even that's not true. The original Project Builder app was 22 years old before it was discontinued. There's a whole lot of history and legacy that you seem to have missed. Slow debugger: not sure what bloat Xcode has or what it is doing, but sometimes it can take more than 10 seconds from breakpoint firing to actually see values. Try using print statements instead. In many cases, especially UI-related, breakpoint debugging simply isn't possible. There are far too many event loop iterations that happen in normal behaviour. Find usages: Have you tried "show callers"? That seems to be the equivalent functionality. Visual debugger: debugging SwiftUI with visual debugger is in 90% useless task and waste of time. Many of your complaints seem focused on SwiftUI. That's a delicate topic. I recommend focusing on why you're using Xcode in the first place. Because you love Xcode and SwiftUI? Or because you want access the market? Just because Apple publishes and pushes a given tool or framework, doesn't mean you have to use it. I have 64GB of RAM and sometimes it seems it is not enough My primary computer has 32GB of RAM and my test rig only has 16 GB. Both have no problem with Xcode. But then, the 32GB still runs Ventura and I gave up on SwiftUI a long time ago. Compiling SwiftUI previews and getting them to work. NIGHTMARE! Yeah. That was maybe the first thing I dumped when trying to use SwiftUI. I do not get it. first make SwiftUI framework, and then neglect all tools to make it easier and faster to use? I would understand some company with budget problems, but Apple??? Apple runs a very tight and lean ship. The teams behind the features, frameworks, and apps are much, much smaller than you might imagine. Why did IntelliJ managed to make better IDE in less time and even make it more expandable with extensions? Their developer and user market share is a tiny fraction of Apple's. With better tools you will get more developers and with that more apps Apple has many more developers and apps than it needs.

I have experienced similar problems. I don't know of any way to escalate. You just have to wait. Why do you need to update the number? These systems are all setup for automated processing. You have to try really hard to make sure all data is valid and will remain valid forever. Even if it looks like there's an automated update system, it may be much less automated than it appears. Any time you fall out of the automated process and need manual intervention, you are going to have to wait. The wait times you've described so far sound like what I would expect.

Look at some other example e-mails that don't exhibit the problem and compare what they are doing that is different than what you are doing.

The only way to force a release of an autoreleased object is to create your own autorelease pool with a smaller scope. In theory, you can use the method names to determine ownership and responsibilities. The documentation usually tells you too. With modern ARC code, it usually isn't too big of a problem.

Apparently, all you need to do is ask them. See: www macobserver com/news/anti-spying-tool-spybuster-arrives-to-ios-thanks-to-ukrainian-developer-macpaw/ and www igen fr/app-store/2022/07/spybuster-detecte-les-applications-de-votre-iphone-en-lien-avec-la-russie-131429 (I guess the forum doesn't like those external links.) But apparently, there is a way to do it via StoreKit and it is allowed as per the Guidelines: don’t collect information about which other apps are installed on a user’s device for the purposes of analytics or advertising/marketing So I guess if you're doing it for any other reason, you're good to go.

Apparently, all you need to do is ask them. See: www macobserver com/news/anti-spying-tool-spybuster-arrives-to-ios-thanks-to-ukrainian-developer-macpaw/ and www igen fr/app-store/2022/07/spybuster-detecte-les-applications-de-votre-iphone-en-lien-avec-la-russie-131429 (I guess the forum doesn't like those external links.) But apparently, there is a way to do it via StoreKit and it is allowed as per the Guidelines: don’t collect information about which other apps are installed on a user’s device for the purposes of analytics or advertising/marketing So I guess if you're doing it for any other reason, you're good to go.

I am working on adding RFC4217 Secure FTP with TLS by extending Mike Gleason's classic libncftp client library Why? I had an app years ago that supported FTP. One of the first bug reports I had was from someone connecting to a server on VMS. Any suggestions are welcomed that might shine a light on what native curl has access to that allows it to work with ST for these FTP secure-control+data use cases. That part is easy enough to solve. Just download Apple's curl source and look.

Metal uses a subset of C++. Most of that code you're looking at is just the boilerplate setup code from years ago. That's why it still uses Objective-C. It should be easy to convert to Swift.

I don't think you're doing anything wrong. I downloaded that SDK. It's not even signed. When I checked, all the static libraries are macOS. The included examples are strictly for Windows. I have no idea what's going on there.

He's saying ignore the amount of money Apple puts in my bank account as my revenue, that my revenue numbers that Apple reports to the CRA will be pre-commission and pre-sales tax on commission. I then count the commission and the sales tax on it as expenses. He says if I don't do it this way I'll get audited since the numbers from Apple won't match what I'm submitting to the CRA. I would be cautious about filing any tax forms based on what someone claims that some other party is filing as part of their taxes. You are responsible for your taxes, not Apple's. My accountant is saying though that Apple should be charging me HST/GST on the service they provide of distributing the app globally, managing payments globally, etc. (i.e. the 15% commission). Since they provide this service for all global sales he's saying the HST/GST would apply on commission for all global sales. Should be? Is that what is really happening? Back in 2021, Apple did operate like this for sales to customers in Canada, and provided clear tax invoices documenting everything. But in 2021, the Canadian tax laws also radically changed. I'm not sure how it works today. What you are asking about here is one very specific way of doing business. Is this HST due on payment for supply of services? If so, do you have an invoice for that payment? Or is it more like royalties? One problem with all of this is that this little business that we're doing is quite unusual. Few people, including accountants, really understand it. It has radically changed in the recent past, and will radically change again in the near future. Maybe you should consider contacting CRA directly and asking them. I did that back before I got my app into the Mac App Store. The CRA was quite helpful.

My accountant is telling me I can claim back the sales tax paid on Apple's commission. In my jurisdiction sales tax is 13% so I could get 13% of the 15% Apple commission for example, so almost 2% of my total sales (15 x 0.13 - 1.95%) as a tax credit. Are you sure that Apple paid, or was required to pay, HST on your total sales? Or only your Canadian sales? Be very careful of mixing and matching these different kinds of sales and taxes. In Canada at least, Apple sells software to consumers. Apple charges taxes on those sales to those consumers, then reports and remits those taxes to the CRA. That is totally separate from the income taxes that you pay to the CRA. You may be able to reclaim HST that you paid, but only if you are certain that said HST was actually payable and remitted to the CRA. The question here is the nature of of this commission that you pay to Apple. Is this commission taxed the same way as those "digital goods" that Apple sold to Canadians on your behalf? Back in 2021, the last time I was making any meaningful money from the App Store, Apple made a "Canada Tax on Commission Invoice" PDF available in App Store Connect. That PDF explicitly listed the HST paid on sales in Canada, much like my invoices from AWS and EasyDNS. The tax laws were crazy complicated in 2021 and they're only worse now. They will get even worse in the near future. The only advice I can give you is to make sure you have documentation to back up any tax claims that you make. If you don't have a form that explicitly lists the HST that you paid, then you're on thin ice if you try to take that money back.

Did you check the new uninstall functionality in Sequoia System Settings?

I'm not seeing the 2nd part of the behaviour you describe. When I change it to macOS 13.0, or iOS 15.0, it stays there. To be honest, any .0 version is a bit risky. Apple isn't shy about releasing API changes in .x versions.

I think I'm making some progress. Here is what I've learned. Indentation cannot be disabled. End of story. So there's that. The most important setting is "Indent solo { by _ spaces". This has nothing to do with the "{" character. It affects every line. There is a concept of indentation context. This is the "indent width" setting. It is the number of spaces after an opening "{" to indent the next line of code. The "indent solo { by _ spaces" defines a negative indent from the indentation context. So, if I want to code Objective-C in this style: - (void) foo { handleValue(3); if(YES) { handleValue(4); } } I need an "Indent width" of 2 and an "indent solo { by _ spaces" of 2. They cancel each other out and my code lines up. The indentation context in Swift is more complicated. At the top level, it works like Objective-C. After the top level, Swift ignores the position of the opening brace. The context is defined in terms of the parent expression. if "indent width" and "indent solo {" are the same, then they cancel each other out and my subordinate block is indented at the same level as the parent, which is wrong in any language. In order to get my code to work (after the top level), I need to set "indent solo { by _ spaces" to zero. Luckily this field does accept zero. "Indent width" does not allow zero. What this means for people dealing with leftward indent problems, you may be able to fix the problem by setting "indent solo { by _ spaces" to zero, but only in Objective-C/C++. C++ seems to work like Swift's inner block logic. Set "indent solo { by _ spaces" to zero and it should fix it everywhere. But alas, poor me. I waited ten years to switch to Swift, and I didn't wait long enough to iron out the daily bugs.