tinman83 / zscreen

Automatically exported from code.google.com/p/zscreen
0 stars 0 forks source link

UploadScreenshot is not working - api key is inactive or banned #802

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Windows 7 x64, ZScreen-4.9.0.3046-dev-setup.exe

2012-04-21 13:09:23.368 - Creating job: CaptureRectRegion
2012-04-21 13:09:23.371 - Clipboard, Upload using uploadscreenshot.com
2012-04-21 13:09:23.379 - Retrieved Window Title at StartWork
2012-04-21 13:09:24.538 - Setting Image 380x230 to WorkerTask
2012-04-21 13:09:24.538 - Performing PNG Save using ZLib level 9 compression 
without interlace
2012-04-21 13:09:25.683 - Performed Actions using Image Annotator.
2012-04-21 13:09:25.683 - PrepareData prepared data from image
2012-04-21 13:09:25.683 - Performing PNG Save using ZLib level 9 compression 
without interlace
2012-04-21 13:09:25.708 - Initialized uploadscreenshot.com
2012-04-21 13:09:28.342 - The apiKey that you provided does not exist or has 
been banned. Please contact us for more information.
2012-04-21 13:09:28.342 - The apiKey that you provided does not exist or has 
been banned. Please contact us for more information.
2012-04-21 13:09:28.342 - The apiKey that you provided does not exist or has 
been banned. Please contact us for more information.
2012-04-21 13:09:28.371 - Job completed: CaptureRectRegion
2012-04-21 13:09:28.371 - Task duration: 2590 ms

Original issue reported on code.google.com by x.meg...@gmail.com on 21 Apr 2012 at 10:11

GoogleCodeExporter commented 9 years ago
http://img1.uploadscreenshot.com/images/orig/4/11100280066-orig.png

You are getting very strange results x.meglio!

Original comment by mcored on 21 Apr 2012 at 1:36

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Closing issues just because you cannot reproduce them is not a good development 
tactic. You lose the efforts of others who report the problem. More you close 
just because you cannot reproduce - more I lose interest to report any 
potential bugs (which you must be interested in as product developer - it is 
like free testing for you).

Original comment by x.meg...@gmail.com on 21 Apr 2012 at 2:45

GoogleCodeExporter commented 9 years ago
It is working in ZUploader too: 
http://img1.uploadscreenshot.com/images/orig/4/11106564519-orig.png

Original comment by flexy...@gmail.com on 21 Apr 2012 at 8:04

GoogleCodeExporter commented 9 years ago
Ok, but I'm talking about ZScreen, not ZUploader.
Anyhow, there is concrete debug messages which say it is not working for some 
reason:

> The apiKey that you provided does not exist or has been banned. Please 
contact us for more information.

Original comment by x.meg...@gmail.com on 21 Apr 2012 at 8:30

GoogleCodeExporter commented 9 years ago
ZUploader and ZScreen using same upload library and api keys in same library.
So when we are using same api keys how it is not giving error to us and giving 
to you i don't understand. Maybe you using old version? Because it is banned 
long time ago when one people uploaded illegal image to there with ZScreen... 
So we got new api key after that.

Original comment by flexy...@gmail.com on 21 Apr 2012 at 8:38

GoogleCodeExporter commented 9 years ago
Maybe it is "configuration storage" problem?
Where can I check what api keys my zscreen is using?
is it in some configuration file or hardcoded into application?

Original comment by x.meg...@gmail.com on 21 Apr 2012 at 9:09

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
x.meglio we are not closing the issue, if we close the issue then it gets the 
"Done" or "Invalid" tag. The issue is labelled as CannotReproduce so we know 
they are strange issues that users are getting which we still need to 
ultimately reproduce somehow. CannotReproduce tag helps us think outside of the 
box. 

Your issue reports are always appreciated. Sorry for the confusion with the 
CannotReproduce tag. 

Original comment by mcored on 22 Apr 2012 at 12:33

GoogleCodeExporter commented 9 years ago
This issue was closed by revision r3051.

Original comment by mcored on 22 Apr 2012 at 2:21