What language would you suggest I use? Which of the following best describes you: (a) I've been programming for decades, and now when I see a new language I quickly realise that it's mostly features that I've used before in other languages, maybe years ago, combined differently with worse different syntax. (b) I've been programming in one language for decades, and whenever I'm forced to use a different language I work out how to write code in the style of my preferred language using the syntax of this new inferior language. ? If your answer is nearer to (a), learn some Swift and SwiftUI. If your answer is nearer to (b), look up what GUI toolkits Ruby has best bindings to (GTK? Qt?) and use that.

Are you referring to the $99 developer programme membership fee? Or something else?

Your app will not be woken up by battery notifications Are you sure about that? It does not seem to be supported by my experiments.

@GrayDev, I think you should lookup the price_point_id each time; don’t hard-code it. Anyway thanks for posting that, I hope OurBigAdventure will be pleased. It is quite similar to the code I linked to before for setting IAP prices ( https://developer.apple.com/forums/thread/732527 ), as I thought it would be.

Does "App Store Connect Engineer"'s avatar image mean that it is a bot?

it does have the "Title" field I need to fill in with something to make the "Submit" button enabled. Isn’t “title” Mr/Mrs/Ms/Dr ?

Those methods can be called from within the app to request a refund. They do not let you “handle inquiries about refunding in-app purchases”.

There is no API or similar. Direct them to their purchase history in the App Store app.

I asked the same question in June: https://developer.apple.com/forums/thread/757159 It’s interesting that the video hasn’t been taken down. I think that if they had abandoned the idea they would have erased it from history. So maybe we’ll get it sometime before WWDC2025? I wouldn’t delay your update to wait for it!

I do see this sometimes, but normally there is some sort of error message. I recall something maybe related to symlinks, once. Do you not see any details?

Stripping that down a bit: runtime error: call to function through pointer to incorrect function type Which is interesting. Maybe it's a bug in libc++. I would be interested to see if it is specific to having monostate in the variant. Try changing that to int. I've tried to search to see if it's a known/resolved clang / ubsan / libc++ bug but I've not found anything obvious.

What is the solution here if I want to open specific section in device settings without taking a chance of my app getting rejected while submission process? You present a message that says "go to the Passwords section of the Settings app". Most users can manage to do that without tripping over their own shoelaces. Sure, a button that goes directly there would be nice, but it's not going to happen. In practice, apps don't seem to be rejected for doing this using the private URL scheme - and a rejection is not the end of the world. Your choice.

What exactly does UBSan say?

What language would you recommend a beginning programmer learn? That depends on a lot of things. I would like to create programs that capture product info and prices from retail websites and then create infographics of product data. Also want to design / build website for my design business and have compatible app for iOS. To be honest I’m not the best person to advise on that sort of work, because it’s a long way from what I do day-to-day. But the same is probably true of most people on this particular forum. The answer is certainly not C, though. It might be Python or something Javascript-like. Do you see this as just the first programming problem of a decades-long career? If you do, it’s probably more useful to understand the fundamentals of computer science generally, rather than specific languages. Good luck.

I am starting with C as per some recommendations I have seen online. Don’t believe everything you read on the internet… "build failed" Somewhere there will be some much more detailed error messages; without more details it won’t be easy for anyone to offer useful advice.