WhatsApp has been facing some problem lately, and the same happened last week. The Facebook-owned messaging app went down for many users in the past week.
WhatsApp has been facing some problem lately, and the same happened last week. The Facebook-owned messaging app went down for many users in the past week. Several users took to Twitter and reported an issue with WhatsApp that did not allow them to access their chats. As per the users, WhatsApp’s screen welcomed them with an ‘obsolete error’ bug and also did not give any information as to how to fix it. The Facebook-owned company has addressed the issue and said that it is working on a fix. However, until then many users have already found a workaround to get WhatsApp working on their devices. The complaints of messaging-app not working started pouring in last week.
According to the screenshots posted by the social media fanatics, the app screen read,“This version of WhatsApp became obsolete on 13 Jan 2018. Please go to the Google Play Store to download the latest version.” The users further got displeased when they found there was no option to re-download the app from Google Play Store. Moreover, some users also said that even after uninstalling and reinstalling the app failed to fix the bug.
Here are the steps to fix the ‘obsolete error’:
Step 1: Go to your phone Settings > Security > Allow installation of app from unknown sources’ and enable it
Step 2: Now, download the latest version of WhatsApp from whatsapp.com/android
Step 3: Install and run it. WhatsApp will be updated without any loss of data from the previous version.
In a statement, WhatsApp acknowledged the issue saying: “On background, this is an issue that’s being fixed. It was a problem with how our app is distributed, which is not under our control.”
Meanwhile, WhatsApp had recently suffered a global outage for about an hour on New Year’s eve before the problem was fixed.
Some reports claim the issue can be resolved by installing the latest (v2.18.8) WhatsApp APK from the WhatsApp site, however, we were not able to replicate either the bug or the resolution.