cancel
Showing results for 
Search instead for 
Did you mean: 

Seeking bug with Google Assistant

bluebaron
Community Member

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.  

1 Recommended Answer

armen_dpe
Solutions Expert
Solutions Expert

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:

  1. Visit the Google Issue Tracker:

  2. Sign in with Your Google Account:

    • Sign in with your Google account or create one if you don't have an account.
  3. Create a New Issue:

    • Click on the "+ Create Issue" button to create a new issue.
  4. Provide Detailed Information:

    • Fill in the required details, including a clear and descriptive title for the issue.
    • In the description, provide a detailed explanation of the problem as above.
  5. Include Reproduction Steps:

    • Include clear steps for reproducing the issue, so the development team can understand and replicate the problem.
  6. Attach Supporting Information:

    • If applicable, attach any relevant logs, screenshots, or recordings that can help illustrate the problem.
  7. Categorize and Submit:

    • Categorize the issue appropriately (e.g Media, Google Assistant).
    • Click the "Submit Issue" button to submit your bug report.
  8. Provide the bugID here so we can track the issue further.

View Recommended Answer in original post

1 REPLY 1

armen_dpe
Solutions Expert
Solutions Expert

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:

  1. Visit the Google Issue Tracker:

  2. Sign in with Your Google Account:

    • Sign in with your Google account or create one if you don't have an account.
  3. Create a New Issue:

    • Click on the "+ Create Issue" button to create a new issue.
  4. Provide Detailed Information:

    • Fill in the required details, including a clear and descriptive title for the issue.
    • In the description, provide a detailed explanation of the problem as above.
  5. Include Reproduction Steps:

    • Include clear steps for reproducing the issue, so the development team can understand and replicate the problem.
  6. Attach Supporting Information:

    • If applicable, attach any relevant logs, screenshots, or recordings that can help illustrate the problem.
  7. Categorize and Submit:

    • Categorize the issue appropriately (e.g Media, Google Assistant).
    • Click the "Submit Issue" button to submit your bug report.
  8. Provide the bugID here so we can track the issue further.