Closed GoogleCodeExporter closed 9 years ago
Thank you for your input. Actually this is the 2nd report of the same issue,
but unfortunately we can not reproduce this error in our environment. In the
coming release, we refined the auth process a little bit, and hope it works on
your device.
Original comment by charle...@gmail.com
on 2 Oct 2011 at 1:22
Ok cool, this is on a Samsung Tab, 32mb 10.1,
Original comment by tdwindus...@gmail.com
on 2 Oct 2011 at 9:22
the 1st report of this issue was also on a Samsung tab 10.1, is this a
coincidence? let's see...
Original comment by charle...@gmail.com
on 3 Oct 2011 at 1:27
in version 1.2, the auth process is refined a little, and I also can reproduce
this, it seems mostly to be caused by the request token is correctly returned.
the auth process still needs to be improved. For now, will you please try more
times if auth fails? it will be ok.
leave this issue open to improve the auth process in the coming update.
Original comment by charle...@gmail.com
on 11 Oct 2011 at 3:46
If it's any help, I also get this issue on a Galaxy tab 10.1
Original comment by nburr...@gmail.com
on 11 Oct 2011 at 7:04
We have identified the possible root cause of this problem, and will roll out a
new version as soon as we finish testing the fix.
Original comment by yuyang...@gmail.com
on 12 Oct 2011 at 11:28
Issue fixed, please install the latest v1.2.1 and let musknow if it works for
you.
Original comment by yuyang...@gmail.com
on 13 Oct 2011 at 1:25
Tested, not fixed - I now get a dialogue box saying it is authorizing, then it
returns me to the option box, without allowing me to auth my account. So its
doing more but still not fixed - unless I need to do something else?
Thanks, Tim
Original comment by t...@lumacoustics.co.uk
on 13 Oct 2011 at 4:59
Tim
Sorry to hear that it's still not working on your device. We updated the
implementation of auth api and tested on 1.2.1 on our devices ( Xoom Wifi,
Toshiba Thrive ), seems this issue was gone, so please give us more time to
look into this.
For now, will you please try to tap the 'auth' button more times? since before
1.2.1 when this issue happens on our device, it will succeed after trying more
times.
Again, sorry for this.
Original comment by charle...@gmail.com
on 14 Oct 2011 at 1:54
reopen this issue.
Original comment by charle...@gmail.com
on 14 Oct 2011 at 1:54
Hi There:
Could you try out the v1.2.2 version from http://code.google.com/p/flickr-viewer-for-honeycomb/downloads/detail?name=flickr.viewer.oauth.apk, which we built with more detailed error messages for authorization flow please?
For installation, you can install the Barcode Scanner from Market: https://market.android.com/details?id=com.google.zxing.client.android, and scan the barcode in the download link provided earlier. This would automatically download the apk, and then install the program after that.
Please let us know if it works or not. If still not, let us know the error message and give us your device name, language, OS version, etc.
Original comment by yuyang...@gmail.com
on 15 Oct 2011 at 5:44
Hi,
This build worked perfectly and authorized against Flickr first time.
Thanks,
Neil
Original comment by nburr...@gmail.com
on 15 Oct 2011 at 8:34
I am marking this issue as fixed and will publish v1.2.2 version to the Market
officially. Thanks for your patience!
Original comment by yuyang...@gmail.com
on 15 Oct 2011 at 8:39
Sorry guys, still not fixed on my 10.1 I now get an error when pressing the
auth button "error:Received authentication challenge is null"
Original comment by tdwindus...@gmail.com
on 15 Oct 2011 at 11:52
Hi tdwindus...@gmail.com:
It sounds like an issue we just resolved for a user with oauth today. It should because your device's time setting is not correct, like time region not set. You can find similar issues on http://groups.google.com/group/android-developers/browse_thread/thread/9896ec659e6ba11d?pli=1
Original comment by yuyang...@gmail.com
on 15 Oct 2011 at 12:03
Same problem here on galaxy tab 10.1... Checked everything qbout time
Original comment by thierry....@gmail.com
on 12 Nov 2011 at 8:27
same issue here on Galaxy tab under Honeycomb 3.2. I get a message saying
"error:Received authentication challenge is null"
Original comment by bnos...@gmail.com
on 18 Dec 2011 at 7:54
Original issue reported on code.google.com by
tdwindus...@gmail.com
on 1 Oct 2011 at 5:15