I just noticed that I no longer get this error on 4.19 preview 4. Looks like it is fixed.
Thank you for your support.