@eskimo much as I expect you are right that sub-classing URLCache could result in a path of pain, implementing one's own cache could result in an equal path of pain. Some considerations:
URLCache uses an SQL DB under the hood - this is useful because it means that transactions can be used to roll back if both data and metadata fail to be written atomically, which the implementer of said custom cache implementation would also need to do. Additionally, the implementer would need to take care of eviction when the disk becomes full or when there's high memory pressure...If developers could focus on solving problems in their own domain instead of the domain that Apple ought to solve for us (providing an RFC-9111 compliant cache), we'd be more productive...it would be great if you could raise this with the relevant teams...🙏
Aodh
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
From
Sweden
Post
Replies
Boosts
Views
Activity
@elmodos can you share some sample code for how you managed this? I get an exception with layoutAttributesForItem called thousands of time if the frame height is altered al all...
I fixed the issue by logging into App Store Connect and agreeing to the new terms and conditions in the Agreements, Tax, and Banking section for Paid Apps (when these change, it seems you need to agree before you can re-upload any IAP packages - the error doesn't reflect this though).