There is some magic that you have to do to grant permission to cron to access your home directory. I forget the details, but a web search should find it.

I posted a thread specifically about stat() here: https://developer.apple.com/forums/thread/734750 I don't know whether your asm hack will avoid whatever checker they plan to use. Once they put that into effect, please let us know what happens. But of course if it does slip past the checker, they will probably consider that as you trying to subvert the app review process. Be careful! As I'm sure you know, checking the existence of files for security reasons is not one of the permitted reasons for calling stat(). So you actually can't declare that your app uses stat(), unless you lie about the reason. Did you submit a request for a new approved reason?

you should keep the .p12 file private as well Translation: you shouldn't have posted that screenshot. Think carefully before posting security-related things.

If you’ve been happy using a 10-year-old iMac until now, then a minimum-spec modern Mac mini will be fine. The first thing to consider upgrading is probably RAM. Regarding displays, is your eyesight good enough to tell the difference between standard and high-dpi?

It's not unusual for optimisation settings to reveal bugs. You're lucky that the bug happens with lower optimisation, as that should be easier to debug than the other case. Can you trigger the bug in the debugger? The stack trace seems clear to me. In thread 5, method Generate::randomSwap has hit a stack guard. One possibility is that you have run out of stack. Do you allocate large data structures on the stack? It does not seem to be a case of excessive recursion. The other possibility is that you are doing pointer arithmetic on a pointer to something on the stack, and you have gone out of bounds. Maybe someone else can extract some more clues from the stack log.

https://developer.apple.com/documentation/swift/function()

Return a swift::String. Convert that to a std::string in your C++ code, and then use its .c_str() method to get the char*. Be aware that the lifetime of the char* is the same as the std::string. Why do you want a char*, rather than a std::string?

My understanding is that Apple App Names are unique Where did you get that understanding from? I don’t know what the current policy is, but some years ago someone produced an app with the same name as one of mine. Even if you can find some Apple statement saying that app names are (now) unique, be aware that they can and do change such policies if it suits them to do so.

Can you explain me why it is not possible to work with VZVirtualMachine on iOS ? It would be great to create a Linux VM on an iPad pro That would allow you to install arbitrary software on the VM, bypassing the App Store. Are you familiar with UTM? https://getutm.app

the number doesn't match at all with the result I can see on the AppStore Connect website Where exactly on the website? The downloaded sales reports should exactly match the website's "sales and trends" numbers. The website's "financial reports" and "analytics" may be slightly different (but not 3X). Are you confusing "downloads" with "sales", or something?

There is a known issue with ASan when running on device with iOS 17. Thanks. I guess I'll downgrade my development devices back to iOS 16. Oh wait.... :-(

Are you large enough to qualify for the "Enterprise" program? https://developer.apple.com/programs/enterprise/

I worked out how to make these ASan errors not terminate the app: Near the middle of the top edge of the Xcode window, tap on the app name/icon. In the popup that appears, tap on "Edit scheme..." In the window that appears, tap on "Arguments" a little below the top-centre of the window. Below "Environment Variables", tap on "+". Enter name = ASAN_OPTIONS and value = halt_on_error=1 Unfortunately it's now difficult to see if there are any other errors in amongst all these (presumed) false positives.

I'm getting 'undefined symbols' but it doesn't say what symbols!! It took me a while to work this out.... Near the top left of the Xcode window there is a row of small grey icons. Click on the right-most one, which is a portrait rectangle with some broken horizontal lines in it. In the new panel that appears below that row of icons, about the 5th row down has a grey hammer icon and the word "Build". Click on that. Now look at the large top-right pane of the window. Scroll to the bottom and find the line that says "v (!) Link APPNAME". At the far right end of that line, there is a small icon with about five grey horizontal lines. Click on that. The pane will update. If necessary scroll down again. Look for lines with a yellow (or red?) background. You should be able to spot the names of the undefined symbols. Note that when you build again, the pane does not update; it continues to show the errors from the previous build. You need to click on all the buttons again.

Works for me: On further investigation, it works for me when I ssh to my Mac. In this case, ssh sets LANG from the client to en_GB.utf8. But when I run the same command in the Mac terminal, it fails as it does for you. In this case, LANG is set to en_GB.UTF-8. Note different capitalisation and hyphenation. Is the code that you are looking at conditional on UTF-8?