Agreed, it would be preferably for any patches or bug fixes to follow the Semantic Versioning principle.
Meaning, once a bug has been fixed or a patch applied, a new version would be released instead of simply updating files and keeping the same version.
I’m experiencing a similar behavior and can confirm this bug was introduced in ACF 5.6.0.
This may also be related to Front End image fields failing validation.
I’m experiencing a similar behavior and can confirm this bug was introduced in ACF 5.6.0.
In my testing, the Front End image field uploads the asset to the Media Library, but the ACF Form shows a validation error, so it’s both misleading and broken.
On macOS 10.12.x using Chrome 60.x this shows as the following:
url=C%3A%5Cfakepath%5C15851_341517840345_529745345_9520381_3073091_n.jpg&size=43073&type=image%2Fjpeg&width=399&height=577
See the attached screenshot for more information.
Fantastic. Keep up the great work!