12-26-2023 09:57 PM
There is a bug with Google Assistant. I have filed countless feedback requests. I have contacted Spotify and TuneIn to try to get them to deal with this. I cannot get anyone who understands the problem.
The problem is, I believe, with the seek commands that Google Assistant is sending to applications.
If you say, "Okay, Google, skip back one minute," Assistant sends the app a seek(60) command when it should send a seek(currentPlayTime-60) command. See the difference? And this causes all sorts of havoc. It started the day that the latest major version of Google Home came out and it's a really aggravating one.
If you're in a podcast, it'll skip to 1:00. You might have been at 47:32. You'll have to scan through the episode to figure out where you were. Even worse, if you do it in TuneIn, it will seek to a location no longer in memory and the audio will be silent, but play will continue, just playing 0s.
Answered! Go to the Recommended Answer.
01-04-2024 01:00 PM
I'm sorry to hear about the issue you're experiencing with Google Assistant's seek commands. To address this problem and ensure that it reaches the appropriate teams for investigation, I recommend opening a bug report on the Google Public Issue Tracker. Here are the steps:
Visit the Google Issue Tracker:
Sign in with Your Google Account:
Create a New Issue:
Provide Detailed Information:
Include Reproduction Steps:
Attach Supporting Information:
Categorize and Submit:
01-04-2024 01:00 PM
I'm sorry to hear about the issue you're experiencing with Google Assistant's seek commands. To address this problem and ensure that it reaches the appropriate teams for investigation, I recommend opening a bug report on the Google Public Issue Tracker. Here are the steps:
Visit the Google Issue Tracker:
Sign in with Your Google Account:
Create a New Issue:
Provide Detailed Information:
Include Reproduction Steps:
Attach Supporting Information:
Categorize and Submit: