Honestly, this is why I hate working with some APIs. Swift no content errors are vague af.
Try adding `print(response.debugDescription)` to see *everything* coming back. Sometimes there’s a hidden header or something that explains it.
If all else fails, curl the endpoint manually and see what’s up.
Try adding `print(response.debugDescription)` to see *everything* coming back. Sometimes there’s a hidden header or something that explains it.
If all else fails, curl the endpoint manually and see what’s up.
