I'm still seeing various confusing download states in the transaction when trying to download content. I'm mostly seeing issues on iOS 14.2. A quite common error seems to be the download being reported as finished and there is a referenced cache folder in Library/Caches/StoreKit. However, this folder appears to be empty and there is no "Contents" sub-folder as expected. What seems to happen is that the download transitions from waiting (progress zero) to finished (progress 1.0) straight after the download has been started. This error condition persists until a power-cycle of the device which seems to clear the error, allowing the download to proceed successfuly. Also, can someone confirm the naming convention of these cache files changed significantly in iOS 14? In 13.7 for example, the download location and naming convention appear to be different. I'm also still seeing occasional instances where the state is waiting, but the download progress goes from zero to 1.0 and the content is actually downloaded. In this latter error scenario, it means I have to have a workaround to essentially ignore this documentation: Use the downloadState property to determine whether the download has completed. Don’t use the progress or timeRemaining property of the download object to check its status; these properties are for updating your UI.

Hi, I've noticed that after cancelling an IAP content download, and attempting to re-download, while the transaction download seems to kick-off OK, and progress is reported as being > 0, the download state is still set to cancelled. I would have assumed that when (re)downloading, the state would / should change to being active ("Download is actively downloading" according to the state enum docs). Is this a legit bug or a "feature" ? It entails a nasty workaround on the app-side for sure as you have to assume now that an active download is where you have a progress of > 0 instead of looking at the download state property. Yuk.