omnight / phonehook

12 stars 8 forks source link

Not able to connect to truecaller #19

Closed adithyakhamithkar closed 7 years ago

adithyakhamithkar commented 8 years ago

Hey,

I am getting a message saying not able to connect to truecaller

[D] dbus::processNumber:248 - request raise/activate
[D] dbus_adapter::set_lookupState:45 - setting state =  "activate:lookup"
[D] dbus::processNumber:254 - connecting lookup_thread(0x48933ce0)
[D] expression for onCommand:233 - stateChange activate:lookup
[D] stateChange:193 - GOT LOOKUP STATE!!! activate:lookup
[D] lookup_worker::threadStarted:83 - bot query "
            SELECT bot.id, bot.name, bot.xml, bot.country FROM bot
            LEFT JOIN block ON block.bot_id = bot.id
            WHERE 1=1
     AND enabled = 1
        ORDER BY COALESCE(block.bot_id,9999),bot.id
    "
[D] lookup_worker::threadStarted:91 - got bot! "TrueCaller"
[D] lookup_worker::threadStarted:158 - xml result
[D] lookup_worker::threadStarted:159 - "<result>
 <field>
  <title>Name</title>
  <value>Could not connect</value>
  <stitle>name</stitle>
 </field>
 <field>
  <title>Address</title>
  <value>India</value>
  <stitle>address</stitle>
 </field>
</result>
"
[D] dbus_adapter::sendQml:57 - sending qml...
[D] lookup_worker::threadStarted:91 - got bot! "EveryCaller"
[D] lookup_worker::threadStarted:158 - xml result
[D] lookup_worker::threadStarted:159 - "<Root/>
"
[D] dbus_adapter::sendQml:57 - sending qml...
[D] dbus_adapter::set_lookupState:45 - setting state =  "finished"
[D] lookup_worker::threadStarted:261 - lookup finished?
[D] expression for onCommand:233 - result [
    {
        "source": "TrueCaller",
        "stitle": "name",
        "tagname": "field",
        "title": "Name",
        "value": "Could not connect"
    },
    {
        "source": "TrueCaller",
        "stitle": "address",
        "tagname": "field",
        "title": "Address",
        "value": "India"
    }
]

[D] expression for onCommand:233 - result [
]

[D] expression for onCommand:233 - hideIn 60000
[D] expression for onCommand:233 - stateChange finished
[D] stateChange:193 - GOT LOOKUP STATE!!! finished
[D] lookup_thread::worker_finish:31 - thread finished?
[D] lookup_thread::~lookup_thread:36 - lookup_thread is destroy

Is this because of new api that they are using to verify spammers?

omnight commented 8 years ago

I have seen it happen, but usually it works like it should. I have some monitoring now that verifys all of the sources daily, and so far I have only seen this happen once.

adithyakhamithkar commented 8 years ago

It keeps happening quite frequently for me, I am not able to verify any 😞

omnight commented 8 years ago

Does it also happen if you do a manual search directly on their site?

adithyakhamithkar commented 8 years ago

When i do a manual search directly from their site I am prompted for a captcha does that effect the app?

omnight commented 8 years ago

Yes, that is most likely the cause. I think there is some (daily?) usage limit before that happens, but not sure what the limit is.

adithyakhamithkar commented 8 years ago

Every time I search it prompts me to enter the capcha, Is there any work around for this?

omnight commented 8 years ago

You could try logging in with another account and see if you are still getting captchas. I don't know how many lookups you do daily, but maybe it only appears for users with high lookup counts.

The captcha might be due to some other reason, so I'm really just speculating.

adithyakhamithkar commented 8 years ago

I will try that and get back to you.

adithyakhamithkar commented 8 years ago

It works from a different ID, Let us try and contact the customer support to find out the limits.