Hi Victor,
I’m happy to hear that the bug will be fixed in a future maintenance release.
I found a workaround for this problem, which also might be interesting to know for others who are dependent on custom fields in combination with updating changes through scheduled imports.
I recreated the custom fields I needed with the Plugin “Advanced Custom Fields” and changed the functions tribe_get_custom_field() into get_field(), so the field value gets retrieved correctly. The fields are preserved on updates.
Best,
Frank