"Invalid UserId" when trying to add a new connection

[jdiercks]

No matter what I enter for Name and/or User-ID on the New Conversation dialog, I always get "Invalid UserId" as the response.

    Feb 18 11:44:03.804 DEBG send message, conv: f01b1bdf-844f-49a4-aefe-9d4f63be70e2, id: de71a2c0-8f8a-4e8c-948d-dd03d9826db0
    Feb 18 11:44:03.823 DEBG prepare message future, conv: f01b1bdf-844f-49a4-aefe-9d4f63be70e2, id: de71a2c0-8f8a-4e8c-948d-dd03d9826db0
      Feb 18 11:44:03.823 DEBG store message, conv: f01b1bdf-844f-49a4-aefe-9d4f63be70e2, id: de71a2c0-8f8a-4e8c-948d-dd03d9826db0
        Feb 18 11:44:03.823 DEBG insert message, conv: f01b1bdf-844f-49a4-aefe-9d4f63be70e2, id: de71a2c0-8f8a-4e8c-948d-dd03d9826db0, status: 0
      Feb 18 11:44:03.826 DEBG preparing message, conv: f01b1bdf-844f-49a4-aefe-9d4f63be70e2, id: de71a2c0-8f8a-4e8c-948d-dd03d9826db0
        Feb 18 11:44:03.826 DEBG select, conv: f01b1bdf-844f-49a4-aefe-9d4f63be70e2
        Feb 18 11:44:03.826 DEBG select member ids, conv: f01b1bdf-844f-49a4-aefe-9d4f63be70e2
        Feb 18 11:44:03.827 DEBG select clients, user: 8a2045f7-816a-48af-9998-97e7129f7a66
      Feb 18 11:44:03.827 DEBG enqueue, conv: f01b1bdf-844f-49a4-aefe-9d4f63be70e2, msg: de71a2c0-8f8a-4e8c-948d-dd03d9826db0
        Feb 18 11:44:03.827 DEBG add message to outbox, id: de71a2c0-8f8a-4e8c-948d-dd03d9826db0, conv: f01b1bdf-844f-49a4-aefe-9d4f63be70e2
    Feb 18 11:44:03.922 DEBG send future, conv: f01b1bdf-844f-49a4-aefe-9d4f63be70e2, id: de71a2c0-8f8a-4e8c-948d-dd03d9826db0
      Feb 18 11:44:03.922 DEBG sending message, conv: f01b1bdf-844f-49a4-aefe-9d4f63be70e2, id: de71a2c0-8f8a-4e8c-948d-dd03d9826db0
      context: Client
        Feb 18 11:44:03.922 INFO sending message
        Feb 18 11:44:03.922 DEBG reconnect, host: prod-nginz-https.wire.com
        Feb 18 11:44:04.523 INFO sending message
        context: Rpc
          Feb 18 11:44:04.523 DEBG send json, method: POST, url: https://prod-nginz-https.wire.com/conversations/f01b1bdf-844f-49a4-aefe-9d4f63be70e2/otr/messages
          Feb 18 11:44:04.945 DEBG header received, status: 412
      Feb 18 11:44:07.946 DEBG client mismatch, clients: ClientMismatch { time: 2017-02-18T19:44:04.847Z, redundant: User2Clients { value: {} }, missing: User2Clients { value: {Id { id: Uuid("8a2045f7-816a-48af-9998-97e7129f7a66"), _t: PhantomData }: {ClientId("c5b0bab9ea769e31")}} }, deleted: User2Clients { value: {} } }
        Feb 18 11:44:07.946 DEBG looking up prekeys
          Feb 18 11:44:07.946 DEBG send json, method: POST, url: https://prod-nginz-https.wire.com/users/prekeys
          Feb 18 11:44:08.376 DEBG header received, status: 200
      context: Database
        Feb 18 11:44:08.376 DEBG select, user: 8a2045f7-816a-48af-9998-97e7129f7a66, client: c5b0bab9ea769e31
      Feb 18 11:44:08.376 DEBG new cbox session from prekey, user: 8a2045f7-816a-48af-9998-97e7129f7a66, client: c5b0bab9ea769e31
      context: Client
        Feb 18 11:44:08.378 INFO sending message
        context: Rpc
          Feb 18 11:44:08.378 DEBG send json, method: POST, url: https://prod-nginz-https.wire.com/conversations/f01b1bdf-844f-49a4-aefe-9d4f63be70e2/otr/messages
          Feb 18 11:44:08.800 DEBG header received, status: 201
      context: Database
        Feb 18 11:44:08.800 DEBG updating message status, id: de71a2c0-8f8a-4e8c-948d-dd03d9826db0, status: Sent
        Feb 18 11:44:08.803 DEBG updating message time, id: de71a2c0-8f8a-4e8c-948d-dd03d9826db0, time: 1487447048
        Feb 18 11:44:08.806 DEBG updating conversation time, value: 1487447048
      Feb 18 11:44:08.808 DEBG dequeue, conv: f01b1bdf-844f-49a4-aefe-9d4f63be70e2, msg: de71a2c0-8f8a-4e8c-948d-dd03d9826db0
        Feb 18 11:44:08.808 DEBG remove from outbox, id: de71a2c0-8f8a-4e8c-948d-dd03d9826db0, conv: f01b1bdf-844f-49a4-aefe-9d4f63be70e2

[twittner]

Creating new conversations is in development. Every user is internally identified by a UUID which is what the "User-ID" field expects. Unless you happen to know the UUID of the user you want to start a conversation with it is best to ignore this functionality for now and wait until a better mechanism for user selection is implemented.