Uncategorized

Known bug in Reverse Lookup 2.0.8

Posted by

Hey everyone,

We are aware of a bug in Reverse Lookup 2.0.8 where blocked contacts will sometimes continue to ring through. We are investigating the issue and intend to have a fix for it soon.

in the meantime, as a workaround, you can reboot your phone to enable the blocks. You don’t need any special timing, just do it when it is convenient for you and any of the contacts you’ve blocked will go into effect.

Sorry for any inconvenience. We’ll update as soon as we have a fix posted on the Play store.

a bogota columbia called my cell treis to call it back have the number on my caller id how do i find out who it was to call back

Posted by

I’m not sure what you’re asking..

First, Reverse lookup only handles US calls as noted in it’s app description. Second, if you have the number.. just call it back?

I’m sorry if this doesn’t answer your question.. i think we have a bit of a language barrier

I want to be able to pick numbers out of my contacts to put right to voicemail. Does this do that?

Posted by

That doesn’t really fall under an intended use, but you could always use manual entry to lookup any number you want, even if it’s in your contacts. Then from the results screen just hit block.

However, depending on which manufacturer skin your phone has, you might be able to block numbers just by editing the contact and checking the “send to voicemail” option on.

Reverse Lookup 2.0!

Posted by

Good morning! Check the Android market for the latest update to Reverse Lookup.. it features an entirely new UI that is much cleaner and more native looking than the 1.x iterations.

Some searches have also been streamlined for speed and a few minor bugs have been squashed.

Hang tight crew!

Posted by

Hey all..

We realize today’s update went kind of roughly for many of you. We want you to know we have our eyes on the issues and we’ve already submitted an update that should solve most of them. That should become live within minutes of this post.

After that, we’ll be watching our stack traces very closely over the next few days to identify any other unforseen problems.

As always, thanks for using Reverse Lookup and we apologize for the issues.