Scan to google docs doesn wotk - HP6500A

[wwahmed]

Add one more victim to this defect. I recently bought HP Officejet 8600a Plus - specifically for being able to scan to cloud functionality (without needing a computer in between). I bought this HP printer specifically for this feature as I already had a working multi function brohter printer. Oh well, hopefully HP and Google will fix it soon...

[guygg]

Just went through the online chat, which confirmed it was something Google changed that they need to fix. The agent was unable to specify, even generally (weeks, months, etc), when it might be fixed.

I'm in the sad position of having bought this otherwise outstanding unit as a Christmas gift for my father for the primary use reason of being able to scan directly to Google Docs (start archiving the decades of boxes of paperwork he's accumulated). Since that was the primary reason for even getting the thing, I'm faced with the decision of having to return it just because of the upload problem. Which sucks, because it's awesome that it does duplex scanning as well.

[peterpanpeter]

I got a 6500A Plus AIO. It's so annoying to get an error message. I have spent hours trying solutions on the Google settings side of things with no success. It's one of the main features and it's broken, even with the latest update. HP fix this, please!!!

[johnbrown_esq]

There was a previous post somewhere among these threads from an HP representative (at least that was what was portrayed) that said they would have this fixed in December. What a bunch of crap. No one at HP is probably doing anything. Big corporate companies not fighting or responding to its customers.

[peterpanpeter]

My new 6500a (e710n) has this problem too. so disappointing.

[linebery]

Any word yet on when the fix will be available?

[cianc]

Add another unsatisfied customer to the list. This app is one of the main reaons i just bought my HP printer.

Also, a promise of a fix is not an actual fix, can we get this issue unmarked as fixed please? i can't see where to click to make this happen.

[jensjakobanders]

Thread is changed to marked "Unsolved"

[Dave_K]

Hey everyone,

I know you are all still struggling with this and I really apologize for the wait on a fix. We have determined that the issue is due to the switch from http-https on Google's end and we are working on a fix. I know you're not going to want to hear this and I hate to be the one to say it but unfortunately I don't know how long the fix is going to take to implement. As soon as I find out anything more I will let you know.

[johnbrown_esq]

Who in the world marked this as resolved when it hasn't been resolved? Also, to Dave_K, uh, we already know what the problem is -- this was pointed out months ago. Tell us something we don't already know.