IssueTracker

Basic information

• Google Play services version: 22.43.12 (180306-483592595)
• SDK version: play-services-auth:20.3.0
• Android OS level: Android TV 10 (error still occurred after updating to 12)
• Device/emulator(Android level): 29
• What device are you using: Chromecast with Google TV
• App Package Name: jp.hapicom.cloudsignagepro, com.lonelycatgames.Xplore, com.mobisystems.fileman
• What are the steps to reproduce the problem? (Please provide the minimal reproducible test case.)
  1. Install our Android TV app on Chromecast with Google TV.
  2. Launch the app and perform Google sign-in with adding a Google Drive read only permission.
  3. Wait for two or more weeks (may need token expire to reproduce?).
  4. Launch the app and perform Google sign-in. If the error does not occur, wait for more weeks.
• What was the expected result: Google sign-in completed.
• What was the actual result: Google sign-in failed with error message "Sorry, this app is not supported. Please try again later."
• Relevant logcat output: logcat output before the error is as below, but there was no output when the error occurred.

2022-11-10 22:44:22.419 6566-6566/jp.hapicom.cloudsignagepro I/TvMainActivity: Requesting sign-in
2022-11-10 22:44:22.459 6566-6604/jp.hapicom.cloudsignagepro V/FA: Recording user engagement, ms: 16778
2022-11-10 22:44:22.493 6566-6594/jp.hapicom.cloudsignagepro V/FA: onActivityCreated
2022-11-10 22:44:22.498 6566-6604/jp.hapicom.cloudsignagepro V/FA: Connecting to remote service
2022-11-10 22:44:22.521 6566-6604/jp.hapicom.cloudsignagepro V/FA: Connection attempt already in progress
2022-11-10 22:44:22.521 6566-6604/jp.hapicom.cloudsignagepro V/FA: Activity paused, time: 113239705
2022-11-10 22:44:22.535 6566-6604/jp.hapicom.cloudsignagepro V/FA: Activity resumed, time: 113239783
2022-11-10 22:44:22.588 6566-6604/jp.hapicom.cloudsignagepro V/FA: Connection attempt already in progress
2022-11-10 22:44:22.589 6566-6604/jp.hapicom.cloudsignagepro V/FA: Connection attempt already in progress
2022-11-10 22:44:22.593 6566-6604/jp.hapicom.cloudsignagepro V/FA: Screen exposed for less than 1000 ms. Event not sent. time: 56
2022-11-10 22:44:22.593 6566-6604/jp.hapicom.cloudsignagepro V/FA: Connection attempt already in progress
2022-11-10 22:44:22.593 6566-6604/jp.hapicom.cloudsignagepro V/FA: Activity paused, time: 113239839
2022-11-10 22:44:22.630 6566-6604/jp.hapicom.cloudsignagepro D/FA: Connected to remote service
2022-11-10 22:44:22.638 6566-6604/jp.hapicom.cloudsignagepro V/FA: Processing queued up service tasks: 5
2022-11-10 22:44:23.890 6566-6566/jp.hapicom.cloudsignagepro I/TvMainActivity: app background
2022-11-10 22:44:23.911 6566-6600/jp.hapicom.cloudsignagepro D/OpenGLRenderer: endAllActiveAnimators on 0xe86c1400 (InsetDrawable) with handle 0xe97eb7c0
2022-11-10 22:44:24.635 6566-6604/jp.hapicom.cloudsignagepro D/FA: Application going to the background
2022-11-10 22:44:26.819 6566-6566/jp.hapicom.cloudsignagepro I/TvMainActivity: app foreground
2022-11-10 22:44:26.993 6566-6663/jp.hapicom.cloudsignagepro I/OpenGLRenderer: Davey! duration=4502ms; Flags=1, FrameTimelineVsyncId=8971730, IntendedVsync=113239728512368, Vsync=113239795245700, InputEventId=0, HandleInputStart=113239798130578, AnimationStart=113239798137328, PerformTraversalsStart=113239798733828, DrawStart=113239822777787, FrameDeadline=113239861979032, FrameInterval=113239798103662, FrameStartTime=16683333, SyncQueued=113239825170703, SyncStart=113239825336203, IssueDrawCommandsStart=113239825445412, SwapBuffers=113239826732412, FrameCompleted=113244230754956, DequeueBufferDuration=28625, QueueBufferDuration=1183625, GpuCompleted=113244230754956, SwapBuffersCompleted=113239830883328, DisplayPresentTime=0, 
2022-11-10 22:44:29.749 6566-6604/jp.hapicom.cloudsignagepro V/FA: Inactivity, disconnecting from the service

• Link to captured Android bug report: Google drive folder
• Link to captured video that demonstrates the issue: Google drive folder

Details

We have an Android app using Google Drive API and the app can also be installed in Android TV.

While this app works perfect on Android TV devices, it sometimes faces a Google sign-in error on Google TV devices.

We first just omitted Chromecast as our supported device, but now feel this error is fatal because it seems Google TV is situated as the next mainstream of the Android TV system.

The captured video shows that sign-in errors occur on multiple Android TV apps that use Google Drive API.

What we found so far are as follows.

• The error occurs on Google TV devices. We and our app users found that it occurred on Chromecast with Google TV, Sony A90J series, and TCL devices with Google TV. Also, many Chromecast users facing the same error can be found on Reddit.

• The error can occur a few weeks after the first Google sign-in was performed on the app. This may be related to some token expiration. This makes reproduction of the error more time consuming.

• Once the error occurs, the app cannot perform Google sign-in anymore unless the factory reset of the device is conducted.

• The error can occur on any apps using Google Drive API. As shown in the captured video, it occurred on Cloud Signage, X-plore File Manager, and File Commander.

• The error occurs both on release and debug builds. After the error occurred with our app installed from Play Store, we uninstalled it and installed its debug version from Android Studio, and the error still occurred.

• The error occurs inside the com.google.android.gms library. We found that the error occurred after the GoogleSignInClient.SignInIntent was launched and before the ActivityResult was returned.

GoogleSignInOptions gso =
        new GoogleSignInOptions.Builder(GoogleSignInOptions.DEFAULT_SIGN_IN)
                .requestIdToken(WEB_CLIENT_ID)
                .requestEmail()
                .requestScopes(new Scope(DriveScopes.DRIVE_READONLY))
                .build();
googleSignInClient = GoogleSignIn.getClient(this, gso);
if (googleSignInAccount == null) {
    signInLauncher.launch(googleSignInClient.getSignInIntent()); // the error occurred after here
}

• We could not focus on the Close button in the error dialog, i.e., needed to press the back button of the Chromecast remote controller.

We would like Google developers to know and fix this fatal error as soon as possible since many users are at a loss.

Also, please tell us whether there is a room to further inspect the error with Android Studio.

(We first created an issue here but pointed out that it is specific to Android TV rather than Drive API, so created another issue here.)

Thanks.