Although it seems to have actually linked successfully after going through the Splitwise auth flow despite this error.
Thanks for the report - I'll take a look at see what's going on. (There's some postMessage funny business there that tries to make the oauth experience nice that might be the culprit...)