# Sign in/out ... Google API

**URL:** <https://community.thunkable.com/t/sign-in-out-google-api/15256>\
**Category:** Feedback\
**Tags:** design, ux\
**Created:** [January 24, 2018, 5:34pm UTC](https://community.thunkable.com/t/sign-in-out-google-api/15256 "2018-01-24T17:34:08Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![adamgb](https://avatars.discourse-cdn.com/v4/letter/a/c67d28/32.png) [@adamgb](https://community.thunkable.com/u/adamgb)\
**Post date:** [January 24, 2018, 5:34pm UTC](https://community.thunkable.com/t/sign-in-out-google-api/15256/1 "2018-01-24T17:34:08Z")

</div>

The sign-in process seems fundamentally broken. At least, if using Chrome & multiple accounts.

For example:

1. Open thunkable
2. Click "sign in"  
expected behaviour: system should ask me which account to log in to  
actual behaviour: it selects an account from my multiple log-ins in Chrome, and logs me into that account

Another example:

1. Click “account” on thunkable (top right corner)  
expected behaviour: it shows me which account is logged-in  
actual behaviour: if offers to log me out (without telling me which account it will log out of)

Another:

1. Click “account” on thunkable (top right corner)
2. Click "log out"  
expected behaviour: it logs me out of [thunkable.com](http://thunkable.com)  
actual behaviour: it logs me out of all Google account in Chrome (this is VERY annoying behaviour!)

The whole sign-in process seems broken, and needs user research.  
I can’t tell whether the fault is with the Google API, or Thunkable’s implementation of it (although, I use many other sites that piggy-back Google for authentication, and I’ve never had this experience before).

---

<div class="post-metadata">

**Author:** ![adamgb](https://avatars.discourse-cdn.com/v4/letter/a/c67d28/32.png) [@adamgb](https://community.thunkable.com/u/adamgb)\
**Post date:** [January 25, 2018, 2:35pm UTC](https://community.thunkable.com/t/sign-in-out-google-api/15256/2 "2018-01-25T14:35:37Z")

</div>

As a followup…

App Inventor doesn’t work this way - it obeys the usual Google Login API rules, and doesn’t do the strange behaviour with not specifying which account is being used (and not logging me out of ALL accounts without warning!)

(logging me out of all accounts is a huge problem … and means I’m unlikely to use Thunkable in future - it caused me a lot of issues yesterday, and I lost some work from my corporate account because of it).

---

<div class="post-metadata">

**Author:** ![Red\_Panda](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/red_panda/32/19387_2.png) [@Red\_Panda](https://community.thunkable.com/u/Red_Panda)\
**Post date:** [January 25, 2018, 4:39pm UTC](https://community.thunkable.com/t/sign-in-out-google-api/15256/3 "2018-01-25T16:39:52Z")

</div>

I agree on 3, but the rest always uses the main account and not the one’s you added

---

<div class="post-metadata">

**Author:** ![adamgb](https://avatars.discourse-cdn.com/v4/letter/a/c67d28/32.png) [@adamgb](https://community.thunkable.com/u/adamgb)\
**Post date:** [January 25, 2018, 4:47pm UTC](https://community.thunkable.com/t/sign-in-out-google-api/15256/4 "2018-01-25T16:47:18Z")

</div>

@Red_Panda…

That’s definitely not the way it works for me - it just seems to randomly select an account.

And none of this works how other systems handle the same process (including MIT App Inventor).

Thunkable seems to have implemented their integration to the G-Login API differently to the ‘standard’ (as best I can tell - as the behaviour seems unpredictable).

---

<div class="post-metadata">

**Author:** ![ioannis](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/ioannis/32/146956_2.png) [@ioannis](https://community.thunkable.com/u/ioannis)\
**Post date:** [November 8, 2024, 12:04pm UTC](https://community.thunkable.com/t/sign-in-out-google-api/15256/5 "2024-11-08T12:04:37Z")

</div>


