Answers to frequently asked questions about Player SDK for Flutter, including questions about licenses, compilation and packaging, and playback.
License-related issues
Resolve invalid or expired license issues in License FAQ.
Common issues across platforms
For platform-independent issues, check Cross-platform player FAQs.
Experienced developers can also troubleshoot playback errors independently.
Compilation issues
What do I do if packaging and compilation by using Player SDK for Flutter fail on an Android device?
In the Gradle Scripts directory, create a proguard-rules.pro file and add the following rules to disable flutter_aliplayer-related obfuscation:
-keep class com.alivc.**{*;}
-keep class com.aliyun.**{*;}
-keep class com.cicada.**{*;}
-dontwarn com.alivc.**
-dontwarn com.aliyun.**
-dontwarn com.cicada.**In the build.gradle(:app) file, enable code obfuscation for the release build type and reference the proguard-rules.pro file:
buildTypes {
release {
minifyEnabled true
proguardFiles getDefaultProguardFile('proguard-android.txt'), '../proguard-rules.pro'
}
}Playback issues
What do I do if an Android device cannot play RTS streams when Player SDK for Flutter uses a single player as the SDK kernel?
Load the RTS library and configure RTS properties on the playback page:
import 'package:flutter_aliplayer/flutter_aliplayer_factory.dart';
// This method applies only to Android devices.
FlutterAliPlayerFactory.loadRtsLibrary(true);What do I do if playback fails without any error when Player SDK for Flutter uses VidAuth for playback?
This issue is usually caused by an incorrect call order for the playback configuration. First, call FlutterAliplayer.createVidPlayerConfigGenerator() to generate the playback configuration, and then set this configuration on the player. If you skip this step or use the wrong call order, playback fails without an explicit error because the player lacks a valid playback configuration. For more information about the correct call order, see the official documentation and demo project.