Skip to content
This repository has been archived by the owner on Sep 20, 2024. It is now read-only.

facebook "No matching user found" #312

Closed
Areks opened this issue Jul 7, 2016 · 8 comments
Closed

facebook "No matching user found" #312

Areks opened this issue Jul 7, 2016 · 8 comments

Comments

@Areks
Copy link

Areks commented Jul 7, 2016

Hello guys, i got this error when i sending message to chat on facebook. I think it's my fail not the botkit, i tried to google this, but i really can't understand where is problem.

debug: API ERROR { message: '(#100) No matching user found',
type: 'OAuthException',
code: 100,
fbtrace_id: 'AGn41P1D1C9' }
@Ayeps
Copy link

Ayeps commented Jul 8, 2016

I'm facing the same problem

info: Got an unexpected message from Facebook: { sender: { id: '####' },

@krismuniz
Copy link
Contributor

These are two different problems.

The first one (@Areks): You are either trying to send a message to a user that is not match your criteria (it could be a phone number if you are doing customer matching or a page-scoped user fb_id).

The second one (@Ayeps): Botkit is receiving a new type of events that it does not currently support. As of today (Jul 14, 2016), botkit does not support message read receipts or message echoes. That's why you got that output.

Hope this helps :)

@crosofg
Copy link

crosofg commented Jul 19, 2016

@krismuniz Which criteria do you mean? Can you please explain in detail. All of a sudden I am getting the same error as mentioned by @Areks .

@RustyDev
Copy link

I'm facing this too with the example fb app:

debug: GOT A MESSAGE HOOK
debug: RECEIVED MESSAGE
debug: CUSTOM FIND CONVO 1415822938445957 1415822938445957
debug: I HEARD [ 'hello', 'hi' ]
debug: API ERROR { message: '(#100) No matching user found',
  type: 'OAuthException',
  code: 100,
  fbtrace_id: 'Cevxr7GLrSc' }

@agamrafaeli
Copy link
Contributor

Read receipts and echoes were both merged in #403

@peterswimm
Copy link
Contributor

Let us know if #403 fixes the above issues!

@agamrafaeli
Copy link
Contributor

@peterswimm I followed @krismuniz explanation and it made sense. #403 indeed solves the problem described by @Ayeps.

The problem that @Areks is describing could indeed be cause by a wrongful input of a user id.

@peterswimm
Copy link
Contributor

closing as resolved

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

7 participants