I did as you suggested, and my own executable worked fine, successfully creating a file in the container directory. You'll have to contact the developer then.

I don't think toolbar items really support resizing. This thread has suggestions that someone received from Apple: https://developer.apple.com/forums/thread/73357 It is little more than a hack. I don't know how well it is going to work with Big Sur's new toolbars. PS: In the future, don't wait for Apple to fix bugs. Report the bug in hopes that one day you will be able to remove your hack, or at least remove it on OS versions where it is fixed so you get more consistent behaviours. But once you find a bug, you'll have to work around the problem yourself and your fix will have to last until you drop support for the OS version(s) affected.

I don't know if this will work, but try "arm-apple-darwin20". More and more often, I am just porting these things to Xcode. Build them in verbose mode first on a platform where they work. That alone can be difficult. Save any generated config files. Then build an Xcode project to spit out the same output. This can take up to a day, or longer for complex projects. But then you don't have to worry about it. Just start with a base distribution, copy your project files into the directory and build with xcode-build.

Some people have reported solving this problem by changing the name of the Xcode executable. It may be related to having one or more beta versions installed. Personally I think it would be better to look at "xcode-select" first.

Maybe try replacing that 3rd party tool with one of your own that creates files with the same name, or dummy files. You can then add debug statements in your file and figure out what is going wrong.

Is this your app?

it doesn't work.  Can you clarify what you are expecting to happen? A basic test would be something like: #if MYSCENE #error It's working! #endif I was originally just kinda guessing what you were talking about because you were mentioning user-defined settings. It looks like you may be still trying to combine my advice about preprocessing defines with edford's advice about Xcode-settings. Both are valid, but not necessarily at the same time. They are two different things.

You are confusing Xcode user-defined settings with preprocessor directives. Xcode user-defined settings can only be used inside Xcode itself. They are useful to define as placeholders inside your Xcode project, so you can build a representative debug version perhaps. Then, for your production builds, you use xcodebuild on the command line and specify platform-specific values for those user-defined settings. Preprocessor defines are specified in build settings under "Other C flags". You would add something like -DMYSCENE.

Some of those restrictions are part of the operating system. You may be able to bypass those with an enterprise developer account and/or MDM profiles. I've never used those so I don't know what capabilities are possible.

 So to make them equivalent, you would need to do 8 x/y pairs in metal. As I said before, I tried doing this in a loop. It had no effect. If you need double, you are indeed out of luck. Precisely.

The script can't handle your path: /Users/Das\'s/Desktop/Deploying/Jyotish\ Studio\ 5/Jyotish\ Studio\ 6.zip Copy it to /tmp or somewhere else. Never assume that any other programmer's script can successfully handle spaces or single quotes.

is there anything I can do? Update your apps to work on Catalina. I have heard similar reports, even regarding Apple's own apps. It isn't that difficult to support new feature and maintain backwards compatibility.

the app needs access to user home dir to add logs and permanently stored keys for the MacBook/user. Why does the app need access to the user home directory for this? You can store logs anywhere. Put them in NSHomeDirectory() and you're done. What are these "keys" you are talking about? You could store those in NSHomeDirectory() too. But it sounds like they could be user default settings which should go into NSUserDefaults(). If they need to be more secure than that, you can store them in the keychain. By "secure" I don't necessarily mean encrypted, just safe from user and 3rd party app vandalism. Users will often delete first and ask questions later. Sometimes, they use "app zapper" or "clean up" tools to do this at scale.

When you say you return a custom row, you are populating your own custom row and not returning anything on the viewForTableColumn data source call ?  No, everything is using default settings otherwise. My view is used in conjunction with a web view, but the web view screws around with focus. The only thing I am doing in my row view is setting the active status by overriding the "isEmphasized" method.

No. You can change the icon at runtime and do that only on Big Sur. That's what I'm doing. One day I might change it when more users are on Big Sur.