reqAccountUpdates throwing error message and / or warnings. Warning is "In eWrapper$updatePortfolio(curMsg, msg, timestamp, file, ... :
NAs introduced by coercion"
Expected behavior
No warnings / errors - clean runs for years
Minimal, reproducible example
reqAccountUpdates(tws,acct="u***")
For some reason, Account[[2]][[1]]$portfolioValue$position (for example, or any index) is NA, and the values in the other six fields (marketPrice, marketValue, averageCost,unrealizedPNL, realizedPNL, accountName) are all "shifted down" by one, so for example, the "Position" field shows NA, but the next field ("marketPrice") shows the Position. The same goes for the third field ("marketValue"), which actually shows the number that should be next to "marketPrice" above it.
Apologies in advance if this is not the correct format. This is the first GitHub issue I've submitted, but I've been using this excellent package for years and rely on it heavily so wanted to see if there was a new release possibly on the TWS side, or even the iBrokers package side, that might be causing this sudden behavior.
If this is an inappropriate forum to bring up this issue, please let me know and I will remove / repost / re-ask elsewhere.
Description
reqAccountUpdates throwing error message and / or warnings. Warning is "In eWrapper$updatePortfolio(curMsg, msg, timestamp, file, ... : NAs introduced by coercion"
Expected behavior
No warnings / errors - clean runs for years
Minimal, reproducible example
reqAccountUpdates(tws,acct="u***")
For some reason, Account[[2]][[1]]$portfolioValue$position (for example, or any index) is NA, and the values in the other six fields (marketPrice, marketValue, averageCost,unrealizedPNL, realizedPNL, accountName) are all "shifted down" by one, so for example, the "Position" field shows NA, but the next field ("marketPrice") shows the Position. The same goes for the third field ("marketValue"), which actually shows the number that should be next to "marketPrice" above it.
Session Info
Apologies in advance if this is not the correct format. This is the first GitHub issue I've submitted, but I've been using this excellent package for years and rely on it heavily so wanted to see if there was a new release possibly on the TWS side, or even the iBrokers package side, that might be causing this sudden behavior.
If this is an inappropriate forum to bring up this issue, please let me know and I will remove / repost / re-ask elsewhere.