Photo: Bogdan Popa/autoevolution/Google
Google has issued an emergency update for Google Maps specifically to correct a widespread error causing the app to crash on Android Auto.
The new version is specifically aimed at beta users and is now rolling through the Google Play Store. You must look for version 11.132.0101 to correct the crash, but if you've enabled automatic updates in the Store, the new build should already be installed on your device.
If the new version doesn't appear, you can update to the late beta by downloading the stand-alone APK installer.
The Google Maps bug has become widespread in the last 24 hours, mainly as more users received the broken beta. However, I've seen users reporting similar behavior in the stable channel, albeit it's unclear if the crashes are related.
The bug caused Google Maps to crash on launch on Android Auto every time users tapped its icon. Repeated attempts to fire up Goole Maps ended in the same way.
Users said running Google Maps on the mobile device was still possible, so the only broken feature was the Android Auto support.
If you downgraded to an earlier build, it's now safe to re-enable automatic updates and get the latest version to correct the problem. Users who temporarily left the beta program or installed another navigation app can return to the newest Google Maps testing version, as everything should work correctly after the update.
The glitch perfectly highlights the risks of being a beta tester. Software companies launch beta programs specifically to provide users with pre-release versions of their applications, allowing them to test them before the public rollout in exchange for feedback. These releases are typically less polished than stable updates and come with bugs and stability problems that must be reported to the parent companies.
Dev teams use the feedback they receive to improve the experience with an app before giving the go-ahead to the stable update, eventually offering improved stability and a reduced likelihood of issues in the non-beta channel.
Beta builds shouldn't be used as daily drivers. Many users do it anyway, and the Google Maps bug that appeared this week proves how big the impact of bug can be when users rely on a testing release as much as on a stable update. Google Maps beta builds could come with bugs that break down navigation or lead to other issues, so using its features every day on your main device is a risky decision.
Google responded fast in this case, which is good news for the Google Maps community considering how many people run the app's beta builds, so fingers crossed that similar major bugs will be avoided in the future. If you can't see the new version on the Play Store, look for the Google Maps APK installers on this page.
If the new version doesn't appear, you can update to the late beta by downloading the stand-alone APK installer.
The Google Maps bug has become widespread in the last 24 hours, mainly as more users received the broken beta. However, I've seen users reporting similar behavior in the stable channel, albeit it's unclear if the crashes are related.
The bug caused Google Maps to crash on launch on Android Auto every time users tapped its icon. Repeated attempts to fire up Goole Maps ended in the same way.
Users said running Google Maps on the mobile device was still possible, so the only broken feature was the Android Auto support.
If you downgraded to an earlier build, it's now safe to re-enable automatic updates and get the latest version to correct the problem. Users who temporarily left the beta program or installed another navigation app can return to the newest Google Maps testing version, as everything should work correctly after the update.
The glitch perfectly highlights the risks of being a beta tester. Software companies launch beta programs specifically to provide users with pre-release versions of their applications, allowing them to test them before the public rollout in exchange for feedback. These releases are typically less polished than stable updates and come with bugs and stability problems that must be reported to the parent companies.
Dev teams use the feedback they receive to improve the experience with an app before giving the go-ahead to the stable update, eventually offering improved stability and a reduced likelihood of issues in the non-beta channel.
Beta builds shouldn't be used as daily drivers. Many users do it anyway, and the Google Maps bug that appeared this week proves how big the impact of bug can be when users rely on a testing release as much as on a stable update. Google Maps beta builds could come with bugs that break down navigation or lead to other issues, so using its features every day on your main device is a risky decision.
Google responded fast in this case, which is good news for the Google Maps community considering how many people run the app's beta builds, so fingers crossed that similar major bugs will be avoided in the future. If you can't see the new version on the Play Store, look for the Google Maps APK installers on this page.
Google News