Hello @GM-Mike,
Apologies for the delay for this fix. 1.2.6 should address it.
If you encounter any specific issues related to this, please let me know by replying to this thread.
Thanks for your patience!