Internal method Connection.storage() might use the wrong Connection.StorageUrl.

[simonklee]

Connection.storage() makes a call to Connection.Call() passing Connection.StorageUrl. Connection.Call() might enter a re-authentication state, calling to Connection.Authenticate() which does overwrite the Connection.StorageUrl.
However, Connection.Call() will continue using the initially passed in storageUrl instead of the reading the value of Connection.StorageUrl.

The easiest way to reproduce this issue is to make any API request on a connection without first calling Authenticate().

[ncw]

Yes I agree.

I'll post a fix for you to try shortly

[ncw]

Hopefully the above fixes your problem - let me know either way!

Thanks

[simonklee]

Thanks Nick,

This seems to fix the problem. As a side effect it is no longer necessary to call Connection.Authenticate() before using a connection.

[ncw]

Merged along with a comment about no longer having to call Authenticate