I'm still seeing the problem. Did you guys have to bounce your instances or something to get things back on track?
On Thursday, June 11, 2015 at 1:19:11 PM UTC-7, Nhat Nguyen wrote: > > Confirmed, everything seems to be back to normal. > > четвъртък, 11 юни 2015 г., 22:31:01 UTC+3, Arun Nedun написа: >> >> The issue now appears to be fixed for me..! Can someone else confirm this >> as well? Will do more checking now... >> >> On Thursday, June 11, 2015 at 8:34:30 AM UTC-4, Erik Zivkovic wrote: >>> >>> I am using code from >>> http://android-developers.blogspot.se/2013/01/verifying-back-end-calls-from-android.html >>> >>> and have been using it for a long time to authenticate users for my >>> service, but since about one hour ago I am getting "Security issue: >>> Signature length not correct: got 256 but was expecting 128", it is being >>> thrown from GoogleIdTokenVerifier.verify >>> >>> There seems to be a similar issue for OAuth: >>> http://stackoverflow.com/questions/30780407/google-oauth2-jwt-token-verification-exception >>> >>> Someone else experiencing the same issue? >>> >>> BR Erik >>> >> -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/6636cd26-4764-4055-a78e-2159b87ce4d8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
