1709942400000 is milliseconds since 1970, not seconds. Traditional "unix timestamp" values are in seconds; that is what the objC/Swift Date constructor timeIntervalSince1970 is expecting. In contrast the Javascript Date constructor takes milliseconds. If you divide the value by 1000 you'll get the right answer.

Which bank is this? Is it more like a bilding society / savings account, rather than a traditional current account?

I see that Apple have updated my feedback report to say "Investigation Complete - Unable to diagnose with current information". I've only just seen this - I didn't get an email. There is, obviously, more than enough information in the report for them to understand the problem. It has a complete example as shown above. @erdenkriecher , any response to your feedback?

I think the aim of the API is to let you automate bulk updates that would be tedious to do manually. For example, changing the prices of 1000 in app purchases. Apple don't want developers to have hundreds of (similar) apps. They would prefer you to have a single app with IAPs for all of the different variations. So they don't want to make it too easy to create lots of apps quickly, and it's therefore not in the API. Just my theory...

I don't believe they've started ending the emails yet - if they had, someone would have mentioned it here. I certainly haven't received any, and I've uploaded and released things without privacy manifests that contain calls to stat().

I suspect that you are not passing a -std=c++11 (or newer) flag. clang++ defaults to C++98. This style of initialiser list was added in C++11. It likely works on other compilers because they default to a newer C++ version. Apple Clang has good support for newer versions but they have chosen not to make them the default.

2 D 4 6 9 1 2 0 - 3 7 8 7 - 4 0 9 7 - B 8 4 3 - F 4 F A 9 7 6 1 3 3 6 E I think it has spotted " F A G " at the start of the last portion of the UUID.

MacBook Air 2022 | 13.6" | M2 | 8 GB | 256 GB SSD I have one of those. one Site mentioned Maximum OS Compatibility is macOS Monetery (?) For a less-than-two-year-old macbook that you can still buy new? No, that obviously supports the latest versions of everything.

I am getting a duplicate symbol error and I cannot pinpoint what part of my code is the issue Xcode hides this away. You need to look at the build log and then click to reveal the actual linker error messages. Search the forum for “undefined symbol” to find detailed instructions.

So, you are saying more or less that I should not buy a Refurbished one No, I'm saying "Don’t buy a used Intel mac obviously; otherwise get whatever you want." Why not going for Intel? Because the expectation for ongoing support in Xcode will be shorter.

There have been occasional reports of unexplained download spikes on the forum from time to time. More often for free apps. Sometimes they might be scams. See e.g. https://developer.apple.com/forums/thread/695036 You should ask Apple for an explanation, before they ask you.

So why do you think you need a privacy manifest for it? You've got the source. Edited to add: sorry, I see it is actually on the list at https://developer.apple.com/support/third-party-SDK-requirements/ . I find that surprising. Does it have a history of misbehaviour, or something?

I think that everything currently available will have similar levels of ongoing support. Breaks in support tend to happen when there is an architectural change, i.e. x86 to ARM and 32-bit to 64-bit. Don’t buy a used Intel mac obviously; otherwise get whatever you want.

In the past some apps have either added “do not buy” to the description or changed the price to $999. I don’t know if there is now a better alternative.

SwiftyJSON is an open-source thing from github, right?