Closed SwiftPush closed 1 year ago
Hi @SwiftPush, thank you so much for your contribution,
I just reviewed and you're right, adding the omitempty tag resolves the problem. But, the library version you're referencing is a little bit outdated, the error handling on the HTTP report is already fixed on the latest version.
I would recommend you update the forked repo, resolve the conflicts, and try it again.
Happy holidays!!
Thank you both and happy new year ! I'm facing the same issue on my side so happy to get your fix on the latest version 1.4.4. Were you able to identify the change on atlassian side , I was not on my side unfortunately. I don't see any changelog on API around the 19th of Dec, start day when the behavior changed.
I'm also wondering when we could have a new release including this fix, as it's currently preventing us creating/updating our confluence pages and I did not found any simple workaround for now ? thanks
@SwiftPush @1OOsei apologies for the delayed response, the latest version fix this error.
Closing this PR.....
Thanks you for supporting this project!!
I observed that Confluence appears to have recently made a change to their "Create Content" API (
POST /wiki/rest/api/content
). They used to accept these fields asnull
, but will now return an exception if you do so.Example
This is a minimal example showing a request that fails and a request that suceeds. The only difference being including a
null
fieldIncluding the
view
field asnull
This request fails
Omitting the any
null
fieldsThis request succeeds