Michael Sotnikov

This is the only solution to implement subscription tracking since there is no automatic subscription tracking provided by firebase

Looks like there're server-side reporting already which is used to report app_store_* events. They are not exported to BigQuery and do not have any standard properties (user_id, device, ...) comparing...

``` Non-fatal Exception: java.lang.IllegalArgumentException at android.media.MediaCodec.native_setSurface(MediaCodec.java) at android.media.MediaCodec.setOutputSurface + 1979(MediaCodec.java:1979) at com.google.android.exoplayer2.video.MediaCodecVideoRenderer.setOutputSurfaceV23 + 1158(MediaCodecVideoRenderer.java:1158) at com.google.android.exoplayer2.video.MediaCodecVideoRenderer.setSurface + 563(MediaCodecVideoRenderer.java:563) at com.google.android.exoplayer2.video.MediaCodecVideoRenderer.handleMessage + 529(MediaCodecVideoRenderer.java:529) at com.google.android.exoplayer2.ExoPlayerImplInternal.deliverMessage + 976(ExoPlayerImplInternal.java:976) at com.google.android.exoplayer2.ExoPlayerImplInternal.sendMessageToTarget + 947(ExoPlayerImplInternal.java:947)...

Yeah. This issue just needs special handling on the app's side to be sure that user experience does not degrade (do not show any UI notifications about an error).

ditching `@firebase/testing` and using `firebase-admin` with `process.env.FIRESTORE_EMULATOR_HOST` solves the problem. Problemmatic: ```typescript import * as firebase from '@firebase/testing'; const firebaseApp = firebase.initializeAdminApp({ projectId: TEST_PROJECT_ID }); ``` Works well: ```typescript import...

According to comments on firebase/firebase-js-sdk#2633 `@firebase/testing` is client-side sdk. And it's incorrect to use it for backend (`firebase-admin`) unit tests. Using `firebase-admin` (`admin.initializeApp`) + `process.env.FIRESTORE_EMULATOR_HOST` is the right approach to...

> it seems that your test also involve preconditions (e.g. asserting that the document doesn't exist yet) nope. test itself does not asserts if document exists. functionality under test take...

Nope. I was going to disable overlay if there is no subtitles or other stuff displayed in overlay.

I want to confirm it. Technically it's displayed but it's located under surface - so it's "invisible" I've created [branch with ready-to-use repro](/stari4ek/androidtv-sample-inputs/tree/issues/overlay) It includes [changes](https://github.com/googlesamples/androidtv-sample-inputs/compare/master...stari4ek:issues/overlay): * compile project under...

I've created issue in Android bug tracking: https://issuetracker.google.com/issues/139429602