yes 
I confirmed that this is a problem in SeeShell Desktop Automation. It works fine in the SeeShell Browser. So this is a bug, and we will fix it with the next update early September.
Meanwhile you can use the API to achieve the same (read CSV via API).