I have found this issue as well and believe it is caused by the new WC 3.0 CRUD classes. However, it does not happen with regular custom fields, only ACF custom fields. So I believe it is an ACF bug.
Welcome
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users
We use cookies to offer you a better browsing experience, analyze site traffic and personalize content. Read about how we use cookies and how you can control them in our Cookie Policy. If you continue to use this site, you consent to our use of cookies.
