Thanks for checking!

Hi Kevin, Thank you for this interesting post. A decade ago I was struggling with an app that tried to use large memory-mapped read-only data files. By default, we prevented that issue by artificially limiting address space and terminating the app when it hits that limit. That is, you can use the architecture above but doing so won't actually give you access to significantly more memory than you would otherwise have access to, removing most of the benefit this architecture would have provided. So now I know that my inability to map large (multi-gigabyte) files for reading was blocked because you didn't want people to map large files for read/write as a kind of swap. I don't think anyone said that at the time. It's much too late now, but I do wonder if you could have used some other method than simply restricting the virtual memory size, that would have permitted read-only mappings.

Also, with any functionality that allows arbitrary users to send money to other users, you need to be very careful about money laundering regulations and similar.

You need to answer the more fundamental question of whether in-app-purchase is allowed for this at all. If in-app-purchase is allowed, Apple takes 30% (or 15%) of the total value of the transaction, as well as any applicable taxes. If in-app-purchase is not allowed, you need to provide your own payment processing and Apple take nothing. As to whether in-app-purchase is allowed, the primary question is whether the purchased content is delivered in the app. You talk about "shows" and "lectures", but I take it that these are actually streamed videos; are these presented in your app? I'm not totally familiar with the current rules in this case; I think there are some relatively new exceptions for one-to-one consultations.

why the test code print("line 64") is being printed after the test code print("line 84") Because the session.dataTask call on line 52 returns immediately and runs the code from line 78 onwards. The call to dataTask.resume on line 80 also returns immediately, having caused the download to start asynchronously. The code in lines 53 to 76 runs only when the download has completed. I would like the program to wait until the results array has been parsed before continuing the code (otherwise it does not have content to present). Waiting in a method like this one would cause the UI to freeze until the download has finished, which is very undesirable. You need to start your networking elsewhere. When the download completes, store the items and tell the view to update. Have the numberOfRowsInSection method just return the current number of items, which will initially be zero. Possibly also present some sort of "wait" indication (spinner, etc) in this case.

backing by a top VC Did their due-diligence process include understanding Apple's ban on new dating apps?

Seems like my problem is that I can't get the following to work: include/import the auto-generated Swift header in either my C++ header or my C++ source file (which is a *.mm file) What exactly happens when you try?

Yes, this basically works. One oddity is that the C++ wrapper doesn’t seem to provide a default constructor, so you have to use a factory method. If you can’t make it work, post a concrete example and I’ll compare with what I do.

What exactly do you imagine the ”four random people on the internet” who read this forum are going to do? We’re not law enforcement. No I’m not going to click on your random googledrive link.

In the circumstance, you probably can't make a message appear. More likely, you could probably make the current version continue to function by supporting both versions on your back end. To avoid this happening next time, make sure that what is now your new version does include a mechanism that allows it to show such a message when it is replaced.

So most of those % should have been %%, right?

Is it possible for users to initiate a transaction half a year ago and only successfully pay it now? Yes, for a while, though 6 months does seem a bit much.

how have you ascertained this? I’ve been around since before Feedback Assistant existed. If Apple had included a feature that caused it to forward bug reports in the “Third Party Apps” category to the app developers, I’m pretty confident I would have heard about it. I guess I could be wrong. Hopefully one of the two other actual app developers on here will post soon. What have you submitted in that report? ”Some users believe that bug reports filed in Feedback Assistant’s ‘Third-Party Apps’ category are forwarded to the app developers; please change Feedback Assistant to make it clear that those reports are sent only to Apple.”

FB16934300

I would assume that trying to use Apple's Feedback Assistant to report an issue with a non-Apple app would result in an immediate message saying "Feedback Assistant is for reporting issues with Apple products and services. For issues with third-party apps, please contact the developer of the app directly." If Feedback Assistant does waste your time collecting bug reports for third-party apps, do be aware that - unless I've been missing something really fundamental for many years - those reports do not reach the actual app developers. If they do anything at all, it will be to decrease the developer's reputation score in some secret Apple database .