Fix 'Malformed UTF-8 characters, possibly incorrectly encoded' Error #2289
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix 'Malformed UTF-8 characters, possibly incorrectly encoded' Error On Sync Api
1. Why is this change necessary?
Currently when the error message on the Sync Api contains a UUID the error message "Malformed UTF-8 characters, possibly incorrectly encoded" is shown. Which is not very helpfull
2. What does this change do, exactly?
Adds the "JSON_INVALID_UTF8_SUBSTITUTE" option to the Sync API Json Response
3. Describe each step to reproduce the issue or behaviour.
For ex: upsert a product, try to link an non existing media entity to it. "Malformed UTF-8 characters, possibly incorrectly encoded" error will be shown.
4. Please link to the relevant issues (if any).
/
5. Checklist