You really have to separate the concepts of running open source software on the Mac vs. running Homebrew. They are not the same! Virtually every Linux/Unix-based open source project will build and run on the Mac. You may need to install some dependencies. Some of those projects, and their dependencies, may be difficult to build and/or install. Homebrew is 100% different from that. If you have something that doesn't work in Homebrew, take it up with Homebrew.

Apple does not pre-approve apps for the Mac App Store. The Apple engineers who reply here in the forums do not work for App Review, so they can't tell you either.

Any update on this? All my native C applications compile for Apple Silicon. However, many scientists leverage my tools using R and their pipelines depend on Fortran for specific functions. Good support for R and Fortran is really important for many scientists. I have 100% confidence that Apple's level of support for Fortan will not change with the switch to Apple Silicon.

Not a chance.

For this reason I recommend that you either avoid categories like this completely Well that's just peachy. Or use Swift, where we finally resolved this problem (-: Well I've seen some hints of future C++ support in Swift. In summary, Catalina is not calling my convenience method. It is not, however, universal. I have lots of other methods in "MyStringAdditions" that are called correctly in Catalina. So far it appears only to be "unquote", but I cannot be sure and I don't know why the problem (hence the concern). After recovering from my Objective-C exception un-safe policy flashback, I checked my own code using the OBJC\_PRINT\_REPLACED\_METHODS environment variable. There is definitely an "-[NSString unquote]" defined in category CALExtensions in the CalDAV framework.

Big Sur hasn't been released yet so you shouldn't be using it to sign and release software. Notarized apps and packages from Catalina should support any operating system since 10.9. You can try notarizing in Big Sur if you want and see if it works on 10.9 and later.

Now we want to add a functionaliity in this website which can check ios available app names. God I hope not.

The main app launches the helper app when it needs to perform some background processing and it can outlive the main application. If the main app isn't running, how is it supposed to kill the helper? the helper app gets stuck and stops responding to messages Until you correct this problem, a solution is impossible. If your helper app is able to reliably and asynchronously monitor some external source for commands, then there are many ways to control it. Some system methods might be blocked by the sandbox, but there are still plenty more to choose from. If your requirement is that the helper stays live while the main comes and goes, then that will further limit your options, but there are still ways to do it. Maybe try a named FIFO. Or you can listen on a network port for commands. You will have to explain any networking to App Review.

How would I go about installing this library in macOS so that I can code for it in Xcode? Every project, including anything already in a packaging system and/or running on Linux, can be built from source.

You would have far more success learning about the existing accessibility features of the operating system.

What!!!??? Where did you hear that! <sigh>

Hmmm... I checked and I'm not seeing any console log errors. I run 'spctl -a -vv -t install <appname>' to verify the app and and it shows the app is properly signed and notarized Then it is almost certainly a runtime problem. Using console is quite tricky. You have to be fast on the keyboard. Launch Console.app. Recent (beta?) versions may have a button to "start streaming". Otherwise it will fire right up with thousands of messages per second. Get your app ready to run. Have it sitting in a Finder window ready for a double-click, but hold off. If Console is already streaming, then click the clear button to erase the window. Otherwise, click the "start streaming" button. Then, just as fast as you possibly can, launch your app. When it dies, just as fast as you possibly can, go back to Console.app and stop streaming, if possible. If not, make note of the time so that you can stop reading at that point. You will need to scroll up to the top. If you can't stop the streaming, Console will take about 100% of your CPU and wind up your fans. Nothing you can do about that. Search for your app. That entry may not be interesting. You may need to read line by line for a meaningful error message. There will be thousands, if not tens of thousands of log messages. The error message may be not from your app. I did this for one person who posted a download URL. It isn't that hard once you get used to it. I don't remember what the message was in that case.

Github?

How are you doing these tests? Test users are really tricky because parts of the operating system are still connected to your App Store under your account. Ideally, test this inside a VM where no user has ever logged in. Even then, it is going to default to the wrong App Store. You might also want to add a VPN and configure your VM for the expected region. But before you go in too deep in that direction, where are you getting the currency symbol from in the first place? You mentioned "resources I've found online" which sounds pretty bad. Generally the internet is wrong about most things. Here is my logic to get the price string: &#9;SKProduct * product = self.storeProducts[productCode]; &#9; &#9;if(product != nil) &#9;&#9;{ &#9;&#9;NSString * currencyCode = &#9;&#9;&#9;[product.priceLocale objectForKey: NSLocaleCurrencyCode]; &#9;&#9;[self.priceFormatter setLocale: product.priceLocale]; &#9;&#9; &#9;&#9;NSString * price = &#9;&#9;&#9;[NSString &#9;&#9;&#9;&#9;stringWithFormat: &#9;&#9;&#9;&#9;&#9;@"%@ %@", &#9;&#9;&#9;&#9;&#9;currencyCode, &#9;&#9;&#9;&#9;&#9;[self.priceFormatter stringFromNumber: product.price]]; &#9;&#9;&#9; &#9;&#9;return price; &#9;&#9;} priceFormatter is an NSNumberFormatter using NSNumberFormatterCurrencyStyle Technically, my output isn't "correct" according to style guides. I want to ensure people know the $ is in CAD or USD. Often, that isn't clear.

I did a quick search and found a number of people who have examined NSDecimalNumber and found some pretty serious integer overflow bugs. Apparently, it can only handle data in the same range as other basic types. If you try to go beyond that, you risk wildly inaccurate values. I can't post external links here in the forums, but just search for "NSDecimalNumber accuracy". Why are you bothering? Why not just use double, or long double?