However, upgrading to 5.7.12 seems to have fixed this issue. I couldn’t see anything specific in the change logs, but the function that was doing this seems to have been considerably re-written compared to 5.7.7, so this bug has been addressed (either intentionally or unintentionally!).
Thanks for your efforts.
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users