Showing posts with label google. Show all posts
Showing posts with label google. Show all posts

Saturday, July 2, 2016

GoogleAuthException: INVALID_AUDIENCE

I've been having some problems getting an Android app to properly authenticate with my app engine backend. For like weeks, spending the evenings looking through every single google result and trying out different combinations of peoples experience. Today, I finally figured out what my mistake was and I have to write this down.

The problem lies on this page and in this statement.
You need to specify your Android app's package name and SHA1 fingerprint.
  1. In the Package name field, enter your Android app's package name.

This is WRONG! It is in fact the applicationId in the build.gradle file that should be used. The package name in the manifest and the applicationId is most of the time the same, but in my it was not. And I never got the app to properly authenticate. But now it does and I'm happy again!

Tuesday, June 30, 2009

Why web developers shouldn't do systems

I stumbled into the google code blog the other day and there was a post about performance improvement for mobile html5.

There was a section about database performance which was just ridiculous. I won't go too deep into this, but I reacted strongly to the suggestion to "Use Triggers whenever possible". With some experience in application maintenance I can recommend this if you will do the maintenance on this application until its end of life. The reason is simple, putting application logic in the database is hard to debug and cannot be versioned in any simple way. So please, don't do this. Microsoft used to recommend similar things (stored procedures instead of OR mapping) and I think they're trying really hard to forget that now.