Swift no content errors are sneaky.
One thing that tripped me up: caching. If the server’s sending a 304 (Not Modified), it might *look* like a 204. Clear your cache or add `URLRequest.CachePolicy.reloadIgnoringLocalCacheData` to your request.
Also, +1 for Postman—it’s a game-changer.
One thing that tripped me up: caching. If the server’s sending a 304 (Not Modified), it might *look* like a 204. Clear your cache or add `URLRequest.CachePolicy.reloadIgnoringLocalCacheData` to your request.
Also, +1 for Postman—it’s a game-changer.
