Ran into this last week! Turns out my backend was sending a 204 *with* a body (lol, bad practice).
Swift’s URLSession just... ignores the body if it’s a 204. So if you’re *expecting* data, double-check the status code first.
Tools like Charles Proxy can help sniff out what’s *really* happening.
Swift’s URLSession just... ignores the body if it’s a 204. So if you’re *expecting* data, double-check the status code first.
Tools like Charles Proxy can help sniff out what’s *really* happening.
