[flutter_vlc_player] PlatformException: Unable to establish connection on channel during VlcPlayerController.initialize()

[nandhakumarbmdev]

[15/06/26, 10:03:26 AM] Nandhakumar B M: rController.initialize()
[15/06/26, 10:03:50 AM] Nandhakumar B M: ## Bug Report

Description

When ⁠ VlcPlayerController.initialize() ⁠ is called, the app crashes with a
⁠ PlatformException(channel-error) ⁠. The Flutter side is unable to establish
a connection with the Android native VLC code.

Error Log

PlatformException(channel-error, Unable to establish connection on channel., null, null)
#0 VlcPlayerApi.create (package:flutter_vlc_player_platform_interface/src/messages/messages.dart:658:7)
#1 VlcPlayerController.initialize (package:flutter_vlc_player/src/vlc_player_controller.dart:191:5)
#2 VlcPlayerController.onPlatformViewCreated (package:flutter_vlc_player/src/vlc_player_controller.dart:969:7)

[MrTONYCHAN]

That error happens before VLC opens the media. The generated Pigeon client sent a message, but no Android handler was registered on that Flutter engine. So the first thing to debug is plugin registration/lifecycle rather than the stream URL.

I would check these in order:

1. Do a real native rebuild, not hot reload:

flutter clean
flutter pub get
flutter run

Also uninstall the existing app once before reinstalling. Adding or changing a native plugin cannot be validated by hot reload.

2. Verify that flutter_vlc_player and its platform-interface package resolve to compatible versions:

flutter pub deps | grep -A3 flutter_vlc_player

Avoid pinning flutter_vlc_player_platform_interface directly unless the main package explicitly requires it; a generated-channel mismatch can produce this symptom.

3. Check your Android embedding. If you override configureFlutterEngine in MainActivity, call super.configureFlutterEngine(flutterEngine). If you create/cache a Flutter engine yourself, make sure plugins are registered on that same engine. A platform view created on one engine cannot use a plugin registered only on another.

4. Make sure initialize() runs on the main Flutter isolate after the widget/platform view is attached. Plugins are not automatically registered in arbitrary background isolates.

5. Compare debug and release builds. If debug works but release fails, inspect R8/minification and native packaging. If both fail, capture Android logs from app startup—not only the Dart exception—because an Android-side plugin initialization exception usually appears earlier:

adb logcat | grep -i -E "flutter|vlc|libvlc|pigeon|exception"

A minimal test should contain only one VlcPlayerController, one VlcPlayer, and no custom Flutter engine. If that works, add back the custom activity/engine and app lifecycle code until registration breaks.

One other point: flutter_vlc_player is not a FlutterFire/Firebase plugin, so this discussion is in an unrelated repository. If the checks above do not isolate it, report the resolved package versions, Flutter version, Android API/ABI, MainActivity, and the native logcat lines to the flutter_vlc_player maintainers; they can confirm the exact generated-channel version pair.