[v12.1.1] Automatic initialization (autoInit) failure causes onReady not to be called

[Jongchan-park]

Hello,

I’ve discovered a bug in version 12.1.1 where the YouTubePlayerView’s automatic initialization (XML app:enableAutomaticInitialization="true" or calling initialize(...)) never triggers the onReady callback.

Steps to Reproduce

1. Add to your Gradle dependencies:

   implementation 'com.pierfrancescosoffritti.androidyoutubeplayer:core:12.1.1'

<com.pierfrancescosoffritti.androidyoutubeplayer.core.player.views.YouTubePlayerView
    android:id="@+id/youtube_player_view"
    android:layout_width="match_parent"
    android:layout_height="wrap_content"
    app:enableAutomaticInitialization="true" />

YouTubePlayerView youTubePlayerView = findViewById(R.id.youtube_player_view);
getLifecycle().addObserver(youTubePlayerView);
youTubePlayerView.addYouTubePlayerListener(new AbstractYouTubePlayerListener() {
    @Override
    public void onReady(@NonNull YouTubePlayer player) {
        // This log never appears in v12.1.1
        player.loadVideo("dQw4w9WgXcQ", 0f);
    }
});

Expected Behavior
The onReady() callback should fire when automatic initialization is enabled or when initialize(...) is called.

Actual Behavior
In 12.1.1, onReady() is never called.

Downgrading to 12.1.0 fixes the issue immediately.

Notes
Manually calling initialize(...) also does not invoke onReady.

Please restore automatic initialization functionality in the next patch release.

Thank you!

[PierfrancescoSoffritti]

Hi thanks for reporting this, let's use #1223 as the main issue for this. Any help with debugging to find the root cause is much appreciated.