@zorensen,
I'm sorry for the delay getting back with you. For some reason I wasn't seeing notifications on the responses to this ticket.
Our 1.1.6.3 update is going to be released very soon (hopefully within a week or two at the most) and it should resolve this issue based on the testing we've been doing. We've made quite a few adjustments that should handle data regardless of how WC feeds it (which seems to change quite often with their updates) so this shouldn't happen anymore.
Please keep your eye out for that update here soon. I'm going to go ahead and close this thread, but let me know if you have any other questions or concerns.