Ugh, same issue here! Swift no content errors are the worst.
I found that sometimes the API just... doesn’t send anything back even when it *should*. Try logging the raw response headers—you might see a 204 hiding in there.
Also, Postman is a lifesaver for debugging this stuff. You can see exactly what’s coming back (or not).
I found that sometimes the API just... doesn’t send anything back even when it *should*. Try logging the raw response headers—you might see a 204 hiding in there.
Also, Postman is a lifesaver for debugging this stuff. You can see exactly what’s coming back (or not).
