Sometimes you may not hear the alarm clock. But if it repeats itself, then somewhere there is a problem: and in the case we are talking about today it lies in the code of the Google Clock app, and not in too deep sleep or distractions of the users.
Many owners of Pixel smartphones, in fact, have begun to report on Reddit the presence of a bug that precisely causes the inactivity of the alarm clocks which, despite being correctly set, prefer to remain silent when it comes to ringing, and not crack the surface tension of our sleep. The trouble, then, is explaining it to the boss once we get to work.
LATEST UPDATES: BUG FIXED BY GOOGLEIn sharing their misadventures, the community of "latecomers by mistake" seems to have traced a possible cause to the integration between the alarm clock and the use of Spotify playlists as ringtones. It also seems that the problem is more ready to manifest itself when the "Do not disturb" mode is activated on the smartphone, and there are also reports related to a malfunction of the timer.
The onset of these problems could be dated to the March update that brought the 6.4 version of the app. At the moment, waiting for Google to (wake up and) fix things, the best thing to do is to rely on an alternative alarm clock if you normally use the solution developed by Mountain View, which is pre-installed on many devices and it is no coincidence that it is one of the apps that has exceeded one billion downloads on the Play Store.