Post

Replies

Boosts

Views

Activity

Reply to How can I download the invoice for my developer payment?
I can't find ANY document that I could hand over to book keeping. This 5-year-old thread is confusing because half the people are asking about the annual developer programme membership fee paid TO Apple and half the people are asking about the monthly payments FROM Apple. Regarding the payment to Apple for the developer programme membership, you can find VAT invoices for these in the Apple Store website. Log in, follow links for “my account”, find the purchase, click “view invoice”, etc. You may also have received the invoice by email. Regarding the payment from Apple for your app sales - if you are expecting Apple to send you an invoice for that, you are confused. (Do you think that you have to pay Apple each time someone installs your app???). It is YOU who should prepare an invoice to send to Apple each month. The easiest way to do that is to wait until they pay you, and then prepare an invoice for the amount that you have actually received. Attempting to prepare an invoice before that is complicated because of currency exchange rates; you would need an accounts system that works with multiple currencies, then import the financial reports, then at some point reconcile the exchange rates used on they day of the payment. Keep it simple, just work in your own currency and prepare an invoice when you know the exact amount. Note that you don’t need to actually send the invoices to Apple, though you can if you want - they have an address in Dublin you can post them to if your accountants insist on doing that.
Dec ’22
Reply to App Store & GPL-2.0 License
You should ask the OpenVPN people for their thoughts. It is mostly OK to use GPL-licensed code in an iOS app store app. You obviously have to publish ALL of your source code and provide an offer to supply that to everyone who installs the app. “Mostly OK” isn’t quite enough, though. Two issues I’m aware of are: The minimum end users terms and conditions for app store apps ( https://www.apple.com/legal/internet-services/itunes/dev/minterms/ ) need to not conflict with the GPL terms. In particular: “The license granted to the End-User for the Licensed Application must be limited to a non-transferable license to use the Licensed Application on any Apple-branded Products that the End-User owns or controls …”. That “non-transferable” bit is clearly problematic. The GPL requires that you supply the source code, and says: “The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable.”. It could be argued that the “installation of the executable” part is not achievable for iOS because regular users cannot install executables onto their devices. (Though actually they can, now, without paying a developer programme membership, with some limitations.) As I said, ask the OpenVPN people what their policy is. If the copyright holders don’t object to what you plan to do, then minor infractions are less of a concern. But I know they do also offer commercial licensing terms. If they feel that iOS apps should be using their commercially-licensed product, you need to be much more cautios (i.e. talk to a lawyer).
Dec ’22
Reply to If the standards are different every time you review, is there such a thing as a standard?
Wait until the copyright expires in 2040ish. Or, ask whoever owns the rights for permission and send the contract to Apple. Or, get an intellectual property lawyer to write an opinion saying you’re not infringing anything and send that to Apple. Fundamentally it sounds like whoever owns the rights to VPET has complained to Apple about copycat apps and now Apple filters them out. There have been a few similar cases. Apple will not attempt to arbitrate, they will just reject everything until there is no mention and no similarity.
Dec ’22