I’ve got Jira Mobile Connect set up in my iPhone app but it’s acting weird. When I hit send in the feedback view, I get a message saying it’s received. But nothing shows up in Jira. It’s been like this for over a week now.
I turned on debug mode and saw this error:
[JMCTransportOperation connection:didFailWithError:] Request failed:
request body stream exhausted.
The URL it’s trying to hit is for creating an issue, but it’s getting a response code of 0.
Has anyone run into this before? I’m scratching my head here. The feedback items are just sitting there ‘in transit’ and I can’t figure out why they’re not making it to Jira. Any ideas on how to fix this?
I’ve dealt with this exact issue before, and it can be super frustrating. Have you checked if there are any firewall or proxy settings interfering with the connection? Sometimes corporate networks can block certain outgoing requests.
Another thing to look at is the size of the feedback data you’re sending. If it’s too large, it might be hitting a limit somewhere along the way. Try sending a really small, simple feedback item and see if that goes through.
Also, make sure your Jira instance is set up correctly to receive these requests. Sometimes permissions or workflow settings can silently reject incoming issues without giving a clear error.
If none of that works, you might want to consider using Charles Proxy or a similar tool to inspect the outgoing requests in detail. That can often reveal subtle issues that aren’t obvious from the error messages alone.
Hope this helps you get to the bottom of it!
hey, had similar probs before. check ur app’s network settings and jira api endpoints. they change sometimes and break stuff. also, look at network logs for ssl/tls issues. if nothing works, hit up atlassian support. they might know whats up with recent changes or issues affecting ur setup. good luck!
I’ve encountered a similar issue with Jira Mobile Connect before. The error you’re seeing suggests a problem with the data transmission. Have you checked your app’s network permissions? Sometimes iOS privacy settings can interfere with background data transfers.
Another potential culprit could be Jira’s API endpoints. They occasionally change, which can break integrations. It might be worth verifying that your app is using the most current API endpoint for issue creation.
If those don’t help, I’d recommend diving into your app’s network logs. Look for any SSL/TLS handshake failures or timeout errors. These can sometimes manifest as the ‘body stream exhausted’ error you’re seeing.
Lastly, consider reaching out to Atlassian support. They might have insights into recent changes or known issues that could be affecting your integration.