They are supposed to be only the screen with no bezel or similar. That's why they are required to be specific sizes. In practice, lots of apps seem to include other content yet get approved.

No. What do you mean by "associate subscriptions with specific users"? When your app calls StoreKit APIs, it only ever gets information about the user whose device it is running on. You don't need to do anything to "match" users - unless you are providing some sort of outside-the-app payment process.

Would combining GPS with other location technologies (like Wi-Fi or Bluetooth) reduce drifting effectively? The values you get from Core Location have already been merged in this way. I think the answer to your question is basically "no".

If the rejection mentions the app metadata, you need to put a link in the app description in App Store Connect.

There is a whole long section about Canada in section 3 of exhibit B to schedule 2 of the paid apps agreement. I don’t understand it all, but this looks relevent: (c) If You are registered for GST/HST purposes, You, by executing Schedule 2 and Schedule 3, (i) agree to enter into the election pursuant to subsection 177(1.1) of the ETA to have Apple Canada collect, account for and remit GST/HST on sales of Licensed Applications and Custom Applications made to End-Users in Canada on Your behalf and have completed (including entering its valid GST/HST registration number), signed and returned to Apple Canada Form GST506 (accessible on the App Store Connect site); and (ii) acknowledge that Apple will deduct from your remittance the applicable Canadian GST/HST and QST, based on Your address in Canada, on the commission payable by You to Apple. Note the very last bit about “the commission payable by You to Apple”.

I think your accountant is wrong, but I’m far from certain as I am not familiar with Canadian tax accounting. I’d say that Apple’s commission isn’t your business expense. You haven’t paid that sales tax, so you can’t reclaim it. Compare with physical goods. Say you made widgets and sold them to a retailer, who added their markup and sold them on to end users. The end users pay sales tax on the retail price including the retailer’s markup. Would you expect to be able to reclaim that sales tax? I don’t think it makes sense to do that.

What country are you in? My guess is that your accountant is wrong.

No I am not, I'm simply living in the UK currently I guess what I really meant by "UK taxpayer" was something like "Resident in the UK for tax purposes", which probably means "living in the UK for 6 months or more in any year". Or something. I.e. would you expect to declare the income that you get from Apple to HMRC, or to some other country's tax authority? Your circumstances may be sufficiently complex that you need to get professional advice, quite apart from working out how to describe it to Apple. Regarding the W8BEN, could you post a screenshot of what it actually asks you to declare? Mine says this: I certify that (check all that apply) The beneficial owner is a resident of United Kingdom within the meaning of the income tax treaty between United States and that country or region. I.e. resident for tax purposes, not citizen. Is yours different?

Are you a UK taxpayer?

It's only opt-in users. But you can see the % who have opted in, so you can extrapolate to the total number of sessions if you want. (What does "MAU" mean?)

Has anyone faced a similar situation? Yes, if you search the forum you’ll find plenty of similar messages. I don’t recall anyone ever reporting that they were able to save their account from termination. The lesson for all of us is, don’t rely 100% on Apple to pay your bills. Make sure you have a second source of income, and don’t learn only Apple-specific skills.

All my 100+ hours of experimentation and trial and error attempting to create a matching SHA256 has on device have failed I wonder if you are changing the wrong thing. In the tech note you linked to, the required change is inside the “verify certificate chain of trust“ step. See the tip box, “Ensure that your code supports certificates that use SHA-256 and SHA-1 signing algorithms.”. It is not the following section “Compute the SHA-1 Hash”; that is unchanged. (All IIUC).

So I'll most likely just perform the steps in what feels to me like the incorrect order. Here's an anecdote from about 1990: A friend was on a transatlantic flight, and the guy sat next to him had a laptop computer - which was a bit of a novelty at the time, and since this was before at-seat power, he also had a large bag of batteries to swap. (Yes, removable batteries!). My friend was of course watching what the guy was doing. He seemed to be writing 3D graphics code. He would hack around for a bit, then run it, quietly swear, and repeat. Eventually, my friend had to say something. "Excuse me", "Huh, yeah?", "You're multiplying the matricies in the wrong order. Swap A and B on line 481." Anyway. I don't recall the semantics of the Core Graphics transformation functions. There are definitely two ways of thinking about it. My preference with any API of this sort is to form the complete matrix myself and call a single API function to set it. Then I'm in control of what happens and I don't need to worry about whether this particular library does AxB or BxA. Beware that that's not the only way it can go wrong. There is one affine transformation API - I forget which one, maybe it's SVG? - where rotations are about the center of the image, not the origin! Good luck.

I’m afraid you’ve more-or-less reached the end of my knowledge of this stuff. how do I map something like the CTLine to the context? Using this: https://developer.apple.com/documentation/coretext/1511145-ctlinedraw

im in the process of delving more into coregraphics with swiftui Are you? Your code has this: Canvas { context, size in That’s this: https://developer.apple.com/documentation/swiftui/graphicscontext Which is not a Core Graphics context: https://developer.apple.com/documentation/coregraphics/cgcontext Don’t waste your time learning about Core Graphics if you are actually using a SwiftUI Canvas!