Hi Ross,
I can reproduce the error. Thanks for reporting.

Yes. There will be a release pushed.

A work-around is to create a custom field using the Infusionsoft Radio field type instead of their YES/NO field type.

As with any multi-value field, ensure the GF field values match the Infusionsoft field values.

For example, a GF Radio field with two values “Yes” and “No” will correctly map to an Infusionsoft Radio field with those two values.

I believe the problem is that Infusionsoft expects integer values for their YES/NO field type; the current values are sent as the strings “1” and “0” instead of the integers 1 and 0. The string values are always interpreted as integer 0 when assigning to their YES/NO field type.