Reverse Lookup Updates

Going Live: Reverse Lookup 3.5.9

Just a quick note to let everyone know that Reverse Lookup / Reverse Lookup PLUS 3.5.9 has been submitted to the Google Play Store and Amazon App Store! This update brings improved search results.

We anticipate it going live within the next 48 hours, and we’ll update here as it’s approved in each storefront. UPDATE: Now LIVE in all stores with full rollout over the next week or so.

After this, we anticipate the next update in about 4-6 weeks.

As always, thank you for your support and have a great weekend!

FacebooktwitterredditlinkedinFacebooktwitterredditlinkedin

Going Live: Reverse Lookup 3.5.8

After what can only be described as a chaotic start to 2020, we’re happy to announce that we’re pretty much back to normal work here, and Reverse Lookup 3.5.8 has been submitted to the Google Play Store for rollout beginning today.

This release features various minor bug fixes and some tweaks that should result in better results when searching for callers.

In addition, expect the same update to follow closely for Reverse Lookup PLUS as well as the Amazon App Store version.

Thank you all for your patience during this uncertain time and please stay safe.

FacebooktwitterredditlinkedinFacebooktwitterredditlinkedin

Reverse Lookup 3.4.5

A few hours after this post goes live, Reverse Lookup 3.4.5 will begin rolling out on the Play Store and Amazon Appstore. The update should make it to all users over the course of the next two weeks. The PLUS version of this update will follow within the next 5-7 days.

In addition to the usual minor bug fixes, this release adds support for spam call detection. This is a feature that we’ve been preparing behind the scenes for a while, and we hope our users find it to be useful. Whenever you search for a call within Reverse Lookup, our systems will now use historical data to determine whether or not the caller has exhibited spam-like activity, and if so, will make a note of that on the search results screen.

This has worked well in testing, and we’ll be closely monitoring the system to make sure it’s catching as many spammers as possible.

As usual, thanks again and please let us know if you have any issues or questions.

FacebooktwitterredditlinkedinFacebooktwitterredditlinkedin

Reverse Lookup 3.3.4 Released

Reverse Lookup and Reverse Lookup PLUS v3.3.4 is now going live in the Google Play Store

This release addresses an issue that caused incoming call notifications to fail for some pre-Oreo users. In addition to this, the app received various background optimizations and a slightly smaller overall file size. This version should be fully rolled out by early next week.

The PLUS version of the app receives these same optimizations as well as the newer runtime permissions model that the free version received a couple weeks ago. Like the free version, the PLUS version now requires a device running Android 4.0 or higher. This version is rolling out to 100% of users today.

We would also like to alert users to a known issue we recently became aware of: Android Oreo devices are currently not receiving notifications of incoming calls from the app. We are working to resolve the issue and will release a fix as soon as possible. We apologize for any inconvenience.

As always thank you again and please let us know if you have any questions.

FacebooktwitterredditlinkedinFacebooktwitterredditlinkedin

Reverse Lookup 3.3.2 – Important bugfix

Hey all – just a quick note.. after releasing version 3.3.1 over the weekend, we noticed a bug that was causing crashes at launch for a lot of users.

We’ve just pushed out version 3.3.2 on the Google Play Store which should solve this issue, so please be sure to grab the latest version if you’re having trouble.

Thank you and as always, please reach out if you have any comments or questions.

FacebooktwitterredditlinkedinFacebooktwitterredditlinkedin

Reverse Lookup v3.3.x Going Live

Hi! Today we’re beginning to launch Reverse Lookup 3.3 on the Google Play Store. All users should start receiving this update today. Although the update is fairly substantial, most of the changes are behind the scenes and most existing users won’t see a difference in their day to day use.

So what did change?

New permissions request model We’re now building the app against the latest Android APIs, something we had previously planned to do as we moved through the second half of the year. What this brings for our users is the realtime permissions request model that was implemented when Android 6.0 launched a few years back. Existing users won’t see a change – you’ve already accepted the needed permissions when you downloaded the app prior to today. New users on devices using Android 6.0 and up will now be asked to grant permissions as they are needed for the first time. The permission requested at app launch is used to build the main screen from your device’s call log. If you don’t grant this permission, you’ll only be able to search for calls by entering phone numbers by hand. The other permission you may be prompted to grant is for writing contacts, which is used when you use the app to block a number.

Permissions cleanup – Prior to this release, we needed to request the permission for writing to external storage as a requirement of the Google Maps API which is used on the location tab in search results. Google Maps no longer requires this permission, so we’ve removed the request from the app.

As always, we’ll be monitoring the launch and quickly releasing fixes for any issues that arise, so you may receive the app with a different minor version number.

Legacy Android Support dropped – Some of these changes have required us to drop support for devices running versions of Android under 4.0, which was released over 6 years ago as of this writing. According to our data, less than 500 users were still on these versions, and while the app version they have will continue to work for now, they will no longer receive updates or support.

As always, thank you for using the app and please reach out if you have any issues or questions.

FacebooktwitterredditlinkedinFacebooktwitterredditlinkedin