<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Google on Build in Public</title><link>https://build.ralphmayr.com/tags/google/</link><description>Recent content in Google on Build in Public</description><generator>Hugo</generator><language>en-us</language><copyright>©️ Ralph Mayr 2026</copyright><lastBuildDate>Sun, 03 Aug 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://build.ralphmayr.com/tags/google/index.xml" rel="self" type="application/rss+xml"/><item><title>‘Cloud Idenity’ is a secret well kept by Google</title><link>https://build.ralphmayr.com/posts/34-cloud-idenity-is-a-secret-well-kept-by-google/</link><pubDate>Sun, 03 Aug 2025 00:00:00 +0000</pubDate><guid>https://build.ralphmayr.com/posts/34-cloud-idenity-is-a-secret-well-kept-by-google/</guid><description>&lt;p&gt;Permissions on Google Cloud resources are assigned to principals. Principals, in principle 😏, are Google accounts. My personal @gmail.com address, for example, is the principal that &amp;quot;owns&amp;quot; most of my Google Cloud stuff. So far, so good.&lt;/p&gt;
&lt;p&gt;However, in some cases, I was required to delegate ownership of a resource to a principal with an @poketto.me email address &amp;mdash; a domain for which I don&amp;rsquo;t have a Google Workspace account. Consequently, these addresses aren&amp;rsquo;t recognized as regular Google Accounts. (See exhibit A)&lt;/p&gt;</description></item><item><title>The process to get an app into Google Play is… byzantine</title><link>https://build.ralphmayr.com/posts/14-the-process-to-get-an-app-into-google-play-is-byzantine/</link><pubDate>Mon, 14 Jul 2025 00:00:00 +0000</pubDate><guid>https://build.ralphmayr.com/posts/14-the-process-to-get-an-app-into-google-play-is-byzantine/</guid><description>&lt;p&gt;🏗️First, of course, you actually got to build your app. Then you register at the &lt;strong&gt;Google Play Console&lt;/strong&gt; (and fork over $25). Then you provide your name, contact details, etc. and then the fun starts: You need official ID (drivers license, passport), proof of residence (&amp;ldquo;Meldezettel&amp;rdquo; in Austria), proof that you own an Android device, install the Google Play Console App on that device, and verify your contact phone number.&lt;/p&gt;</description></item><item><title>"Token used too early" — the weirdest Google Sign-In error.</title><link>https://build.ralphmayr.com/posts/13-token-used-too-early-the-weirdest-google-sign-in-error/</link><pubDate>Sun, 13 Jul 2025 00:00:00 +0000</pubDate><guid>https://build.ralphmayr.com/posts/13-token-used-too-early-the-weirdest-google-sign-in-error/</guid><description>&lt;p&gt;I&amp;rsquo;ve had my ups and downs with &amp;ldquo;Sign in with Google&amp;rdquo;:&lt;/p&gt;
&lt;p&gt;⬆️It&amp;rsquo;s simple and works well on the web&lt;/p&gt;
&lt;p&gt;⬇️It&amp;rsquo;s a complete hassle inside a hosted WebView in a native mobile app&lt;/p&gt;
&lt;p&gt;But here&amp;rsquo;s something really funny: I local clock is &lt;em&gt;ahead&lt;/em&gt; of Google's &amp;mdash; sometimes by as little as a few milliseconds &amp;ndash; the sign in call will fail with &amp;ldquo;Token used too early.&amp;rdquo; 🤯&lt;/p&gt;
&lt;p&gt;✅ Solution: resync your system clock (in my case, my MacBook with Apple's time server).&lt;/p&gt;</description></item></channel></rss>