Fix: Aborting Waystone account creation causes client-side success state
Response in makeWaystoneAccount:
{ id: 'B5640231-03F0-4E07-8D04-371DD193EBB3',
response:
{ error: true,
errorMessage: 'Remote call failed.',
errorDetails: { [Error: socket hang up] code: 'ECONNRESET' } } }
Success: Waystone account created.
Check the .response.error
object on the response and standardise on that (makeWaystoneAccount
currently returns the deviceID in a naked object — on the root)