media-player-sdk-x-ios

What problem does it solve?

Integrating VisioForge Media Player SDK X into a native .NET for iOS app can be error-prone due to iOS-specific setup like MTtouch interpreter settings, mandatory SDK boot, VideoView placement, Info.plist requirements, and common runtime failures.

Core Features & Use Cases

• Native .NET for iOS integration (net10.0-ios): Set up the iOS-specific VideoView, reference the pinned wrapper and iOS redist NuGets, and wire the sample playback flow into your app.
• Correct engine lifecycle and startup order: Call VisioForgeX.InitSDK() exactly once per process, ensure it runs after the window is key-and-visible, and dispose/stop the player properly.
• Stream-ready playback with practical pitfalls: Use UniversalSourceSettings for URL probing, handle HTTP/ATS issues for network streams, support file picking via UIDocumentPickerViewController, and address common iOS failures like AOT/JIT ExecutionEngineException and black preview stalls.
• License registration for purchased builds: Load a .vflicense resource and call SetLicenseCertificateAsync on every MediaPlayerCoreX instance before OpenAsync and PlayAsync.

Quick Start

Follow the bundled iOS template by adding the provided AppDelegate.cs, CustomViewController.cs, and Info.plist privacy key into a new net10.0-ios project, enable MtouchInterpreter=all on both Debug and Release, call VisioForgeX.InitSDK() after Window.MakeKeyAndVisible(), then start playback by probing the selected URL with UniversalSourceSettings.CreateAsync() and calling OpenAsync followed by PlayAsync.