iOS IAP Apple hosted content download state bug?

lol - that censored word was simply a common non-offensive word meaning "not nice" ;-)

Update: I'm also seeing download state of "finished" with progress of zero. Not sure if that's intentional either, but again, very confusing on the app side. This is on 13.7 btw, but I suspect it's more of a server-side issue anyway :-/

I've also noticed that if you cancel a download, you then get a download notification that correctly reports the state as cancelled but also reports the progress as 1.0 - I would not have expected that. You then can't use that same transaction to re-start a download, so the only way I can see to unblock that error state is to restore purchases.

This seems to be specific to iOS 14.1 as best I can tell. I'm able to cancel and re-start downloads on iOS 13.7 just fine - no need to restore purchases and you can (re-)use the same transaction. Whether that's the "correct" thing to do or not, I'm happy to be educated on that point.

I see this behaviour in the sandbox and production environments.

Update: now some of my users are seeing spurious download status of failed. The localised description of the error is "An unknown error occurred".

The inability to re-start a download also seems to apply to iOS 14.2.

The downloads saga continues... I seem to be having an issue with pause / resume too.

I can't seem to be able to resume() a paused download, but I can start() it. No error is reported - simply nothing seems to happen. However... I can start() it, but when I start() a paused download, the status during (what appears to be a successful download, i.e. progress > 0) is waiting, not active (aka: downloading). I would not have expected that, but I am slowly learning to expect the unexpected with hosted content downloads... This is on iOS 13.7.

In case anyone's interested in this at all aside from me...

pause and resume seems to work OK on iOS 14.2, but trying to restart a cancelled download does not - I guess that's by design, although you can actually do that on iOS 13.7.

Apologies for my error in a previous post - I was trying to resume() a paused download, not start() it. And...

This seems to be working OK on 13.7 too, so either I got this wrong, or something has changed in the last week on the backend. Anyhoo... this all seems to be working predictably / as expected and pausing / resuming downloads makes more sense in the context of my app - i.e. you always want to download the content eventually.

Marking this as resolved.

Update... I think this is broken again.

Basically I'm seeing conflicting download states and progress, e.g. downloads in "waiting" state but the download progress is updating and the content is actually downloading.

It's making it really hard on the app side to handle this logic and I'm getting customer complaints again that "downloads aren't working".

I'm wondering whether to totally ignore the download state property for now?