API Error (NOT_FOUND) and JSON Error (Invalid Unicode Character)

  • Resolved jonnopon

    (@jonnopon)


    8 years, 9 months ago

    Hi,

    after installing this plugin on a client’s site and configuring it with the proper API credentials, we’re immediately getting issues publishing anything to Apple News.

    The two errors we’re getting are:
    The following JSON errors were detected: Invalid unicode character sequences were found that could cause display issues on Apple News

    and

    There has been an error with the API: NOT_FOUND (KeyPath articleId)

    Due to these we’re unable to post anything to Apple News. Any help would be greatly appreciated – thanks.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Bradford Campeau-Laurion

    (@potatomaster)

    8 years, 9 months ago

    The plugin should tell you what sequences it finds to be invalid. Have you truncated those from your post here? If they’re using emoji in a post, we’re aware of that issue and will resolve it in a future version: https://github.com/alleyinteractive/apple-news/issues/404

    With regards to the NOT_FOUND error, please read this thread and see if it is of assistance: https://github.com/alleyinteractive/apple-news/issues/238

    Thanks.

    Thread Starter jonnopon

    (@jonnopon)

    8 years, 9 months ago

    Apologies, I didn’t actually see that the problem sequence shows up in the error message, because it’s being caused by the Unicode “zero width non breaking space” (& #65279; / U+FEFF). I’ve inspected a post which causes the error via WordPress visual + text views, as well as by downloading the post as JSON and by looking at its content as stored in the database – the character in question is definitely not in the post’s content.

    On the API error, thanks for the link. I double-checked with my client and it turns out his channel isn’t approved yet (I thought it was) – would this be the cause of a “articleid” related error like the one I’m getting? (the linked refers to a channelid issue).

    Many thanks.

    • This reply was modified 8 years, 9 months ago by jonnopon.
    Plugin Author Bradford Campeau-Laurion

    (@potatomaster)

    8 years, 9 months ago

    For the unicode issue, it’s likely a plugin that you’re using that’s inserting that code. I’d double check what plugins could potentially be modifying the post content.

    On the API error, yes, that’s exactly the issue. The endpoint for publishing to the API technically doesn’t “exist” until the channel is approved.

    Thanks.

    Thread Starter jonnopon

    (@jonnopon)

    8 years, 9 months ago

    Thanks for the quick and concise responses – appreciated. Just to note, as far as I’ve been able to discern the JSON error won’t actually prevent publishing when the channel becomes live – it’s just a warning? (given that I haven’t set the plugin to stop publishing on JSON warnings)

    Plugin Author Bradford Campeau-Laurion

    (@potatomaster)

    8 years, 9 months ago

    In that case, yes, it would still publish.

    Thread Starter jonnopon

    (@jonnopon)

    8 years, 9 months ago

    Excellent – thanks very much!

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘API Error (NOT_FOUND) and JSON Error (Invalid Unicode Character)’ is closed to new replies.