#google oauth

iOS 26.5.1

Challe Activity app for iOS (version 1.3.30)

06/23/2026

Description:

The Google OAuth sign-in screen for the Challe Activity app for iOS displays an app name of: project-837812025812.

This is not an accurate representation of what the user is granting permission to. 

Steps to Reproduce:

Download the Challe Activity for iOS

From Challe “Let’s you in” screen, select “Continue with Google”

From the “Challe App” Wants to Use “google.com” prompt select “Continue” 

From the Google OAuth screen note the project name of project-837812025812

Result: The app name listed on the Google OAuth screen for the Challe Activity app for iOS displays as “project-837812025812” - this is misleading to the end user 

Expected: The Challe Activity app for iOS should display the correct name of the app on the Google OAuth consent screen

Choose the Google option...

Select the "Continue" option...

 iOS 18.3.1

WOM: Restaurant Discovery app for iOS (version 2.4.0)

03/03/2025

Description:

The WOM: Restaurant Discovery app for iOS has a problem. The WOM: Restaurant Discovery app has a Google OAuth screen. 

Unfortunately, on this Google OAuth consent screen, the app name is incorrect. Instead of displaying an app name appropriate to the app, an app name of: "wom.auth.us-east-1.amazoncognito.com" appears.

Here's a screenshot of how it currently appears:

Steps to Reproduce:

1. Download and launch the WOM: Restaurant Discovery app for iOS

2. Select the app icon in the upper right of the screen

3. Select "Sign Up"

4. From the "Sign Up" pop-up menu, select "Google"

5. On the Google Sign in screen, note the app name of: "wom.auth.us-east-1.amazoncognito.com"

Result: The Google OAuth consent screen displayed by the WOM: Restaurant Discovery app displays an app name of: "wom.auth.us-east-1.amazoncognito.com"Expected: An app name of "wom.auth.us-east-1.amazoncognito.com" isn't user friendly and doesn't provide relevant information to the end user

After launching the iOS app, select "Sign Up"

Select the "Google" option...

OS 18.3

Bozt: Restaurants & Local Food app for iOS (version 4.2.4)

02/01/2025

Description:

The Bozt: Restaurants & Local Food app for iOS has a problem with the OAuth consent screen.

The "Privacy Policy" and "Terms of Service" links on this OAuth consent screen that is displayed by the Bozt app are bad - they lead the user on a dead link. 

Steps to Reproduce:

1. Download and launch the Bozt: Restaurants & Local Food app 

2. From the Sign-in screen, select "Sign in with Google"

3. Select "Continue" to the pop-up prompt

4. From the Google OAuth screen, select either "privacy policy" or "terms of service"

Result: The "privacy policy" and "terms of service" links on Bozt's Google OAuth consent screen take the user to a dead link

Expected: The "privacy policy" and "terms of service" links on Bozt's Google OAuth consent screen should take the user to valid privacy policies and terms of service for the app. 

Download and launch the app...

Choose the "Sign in with Google" option...

Select the "Continue" option to advance to the OAuth consent screen...

Select either the "privacy policy" or "terms of service" links on this OAuth consent screen...

 iOS 18.2.1

OneDayOnly app for iOS (version 4.3.0)

01/22/2025

Description:

The Google OAuth sign-in screen for the OneDayOnly - Online Shopping app for iOS displays an app name of:

This obviously isn't an accurate representation of what the user is logging into. 

Steps to Reproduce:

1. Download the OneDayOnly app for iOS

2. Select the "Account" option 

3. Select the "Log in" option 

4. Select "Log in with Google"

5. From the Google pop-up prompt select "Continue"

6. Note the name "project-4272050226" on the Google consent screen

Result: The app name listed on the Google OAuth consent screen for the OneDayOnly iOS app displays as "project-4272050226" - this is misleading to the end user 

Expected: The OneDayOnly iOS app should display the correct name of the app on the Google OAuth consent screen 

Download the OneDayOnly app for iOS and launch it...

Select the "Account" menu option...

Select the "Log in" option...

Select "Continue" ...

iOS 18.0.1

Pepper - Recipes with Friends app for iOS (version 2.10.1)

11/06/2024

Description: 

The Google OAuth Sign In screen for the Pepper - Recipes with Friends app displays an app name of: "pepperauthprod.auth.us-east-1.amazoncognito.com."

This is not an accurate representation of what the user is signing into. 

Steps to Reproduce:

1. Download the Pepper - Recipes with Friends app for iOS (version 2.10.1)

2. Launch the app - select "Sign Up"

3. From the "JOIN US." screen, select the "Sign up with Google" option 

4. From the Google Sign in screen, note the app name of: "pepperauthprod.auth.us-east-1.amazoncognito.com"

Result: The app name listed on the Google OAuth screen presented by the Pepper - Recipes with Friends iOS app is: "pepperauthprod.auth.us-east-1.amazoncognito.com" - this is an AWS URL and not an accurate representation of what the app's name is. There is no privacy policy or TOS link either 

Expected: The Google OAuth screen presented by the Pepper - Recipes with Friends app should present the name of the app correctly 

Download the Peppers - Recipes with Friends app for iOS

Launch the app and select the "Sign Up" option...

Select the "Sign up with Google" option...

iOS 18.0.1

myPittCounty app for iOS

10/28/2024

Description:

Here's a common problem with Google Oauth consent screens. On the Google Oauth screen presented by the myPittCounty app, the correct app name is not listed. Take a look at how it appears:

This goes against Google's own rules. 

Steps to Reproduce:

1. Download the myPittCounty app for iOS

2. Navigate to the log in page

3. Select the Google logo

4. From the "myPittCounty" Wants to Use "google.com" to Sign in" prompt, select "Continue"

5. From the consent screen, note the app's name isn't listed (instead it says "project-191509807296")

Result: When accessed via the myPittCounty iOS app, the Google Oauth consent screen does not display the name of the app. The app is represented as: "project-191509807296"

Expected: When accessed via the myPittCounty iOS the Google Oauth consent screen should display the correct name of the app 

Download the app for the Apple App Store. Then launch the app...

Select the Google login option...

Select "Continue"...

Implementing OAuth 2.0 in Django: Secure Your Application with Third-Party Authentication

Introduction:OAuth 2.0 is an industry-standard protocol for authorization that allows applications to access user data without exposing their credentials. Implementing OAuth 2.0 in Django is crucial for developers looking to integrate third-party authentication services like Google, Facebook, or GitHub into their web applications. This guide will walk you through the process of setting up OAuth…

iOS 17.6.1

Olive Young Global app for iOS (version 1.3.6)

Date: 08/15/2024

Description:

Here's an unusual problem with a Google OAuth consent screen that I have not encountered before: an app called Olive Young Global has a consent screen which the user is impossible to back out of.

Take a look:

Absolutely no way to back out of this consent screen to the app. The app needs to be forced-quit or deleted. This is a terrible end-user experience. 

Steps to Reproduce:

1. Download and launch the Olive Young Global app (version 1.3.6) for iOS

2. Select the "My" option 

3. From the Sign In page, select "Sign up with Google"

4. No way to back out of Google sign-in page

Result: There is no way for the user to back out of the Google OAuth consent screen presented by the Olive Young Global app - user is stranded on a consent screen. Exiting and re-starting the app does not return the user to the app 

Expected: There should always be a way (a visual cue) for the end user to exit out of a Google OAuth consent screen and back into an iOS app

There's the "Sign up with Google" option...