Client Profile Bug on new Android TV app

Server Version#: 1.43.4.10903
Player Version#: 2026.17.0
Error: [Req#42d3/Transcode] ClientProfileExtra: missing or invalid type parameter
Preceding Log Output: [Req#5857/Transcode] TranscodeUniversalRequest: adapting profile with augmentation data: add-transcode-target(type=videoProfile&context=all&protocol=hls&container=mkv&videoCodec=h264,hevc,vp8,vp9&audioCodec=aac,pcm,mp3,ac3,dca,eac3,truehd&subtitleCodec=ass,ssa,pgs,srt,smi,dvd_subtitle,mov_text,eia_608,eia_708,vobsub,vtt,webvtt,text,ttxt,tx3g)+add-limitation(scope=videoTranscodeTarget&scopeName=hevc&scopeType=videoCodec&context=all&protocol=hls&type=upperBound&name=video.width&value=4096)+add-limitation(scope=videoTranscodeTarget&scopeName=hevc&scopeType=videoCodec&context=all&protocol=hls&type=upperBound&name=video.height&value=2304)+add-limitation(scope=videoTranscodeTarget&scopeName=h264&scopeType=videoCodec&context=all&protocol=hls&type=upperBound&name=video.width&value=4096)+add-limitation(scope=videoTranscodeTarget&scopeName=h264&scopeType=videoCodec&context=all&protocol=hls&type=upperBound&name=video.height&value=2304)+add-limitation(scope=videoTranscodeTarget&scopeName=hevc&scopeType=videoCodec&context=all&protocol=hls&type=upperBound&name=video.bitDepth&value=10)+add-transcode-target-codec(scope=videoTranscodeTarget&scopeName=mp3&scopeType=audioCodec&context=all&protocol=http)+add-transcode-target-codec(scope=videoTranscodeTarget&scopeName=ac3&scopeType=audioCodec&context=all&protocol=http)+add-transcode-target-codec(scope=videoTranscodeTarget&scopeName=eac3&scopeType=audioCodec&context=all&protocol=http)+add-transcode-target-codec(scope=videoTranscodeTarget&scopeName=dca&scopeType=audioCodec&context=all&protocol=http)+add-transcode-target-codec(scope=videoTranscodeTarget&scopeName=opus&scopeType=audioCodec&context=all&protocol=http)

Good Example Log: [Req#862c/Transcode] TranscodeUniversalRequest: adapting profile with augmentation data: add-limitation(scope=videoCodec&scopeName=h264&type=upperBound&name=video.level&value=52)+add-limitation(scope=videoCodec&scopeName=*&type=upperBound&name=video.width&value=3840&replace=true)+add-limitation(scope=videoCodec&scopeName=*&type=upperBound&name=video.height&value=2160&replace=true)+add-transcode-target(type=videoProfile&context=streaming&protocol=hls&container=mkv&videoCodec=h264,hevc,mpeg2video&audioCodec=aac,ac3,dca,dca,dca,eac3,mp3,wmav1,wmav2,wmalossless,wmapro,wmavoice&subtitleCodec=ass,pgs,subrip,dvd_subtitle,mov_text,vtt,dvb_subtitle&replace=true)+add-transcode-target-settings(type=videoProfile&context=streaming&protocol=hls&CopyMatroskaAttachments=true)+add-transcode-target-audio-codec(type=videoProfile&context=streaming&protocol=hls&audioCodec=mp3)+add-transcode-target-audio-codec(type=videoProfile&context=streaming&protocol=hls&audioCodec=ac3)+add-transcode-target-audio-codec(type=videoProfile&context=streaming&protocol=hls&audioCodec=eac3)+add-transcode-target-audio-codec(type=videoProfile&context=streaming&protocol=hls&audioCodec=dca)+add-limitation(scope=videoCodec&scopeName=*&type=NotMatch&name=video.anamorphic&value=999&replace=true)+add-transcode-target(type=subtitleProfile&context=streaming&protocol=http&container=mkv&subtitleCodec=srt)+append-transcode-target-codec(type=videoProfile&context=streaming&protocol=hls&videoCodec=mpeg2video)+append-transcode-target-codec(type=videoProfile&context=streaming&protocol=hls&videoCodec=hevc)+add-limitation(scope=videoCodec&scopeName=hevc&type=Match&name=video.profile&list=main|main 10)+add-limitation(scope=videoTranscodeTarget&scopeName=hevc&scopeType=videoCodec&context=streaming&protocol=hls&type=match&name=video.colorTrc&list=smpte2084|bt709|bt470m|smpte240m|smpte170m|bt470bg|bt2020-10&isRequired=false)
Symptoms: My Android TV used to transcode AAC 5.1 to AC3 5.1 to preserve surround sound. On this build, it tried to direct play it instead, resulting in stereo output. Downgrading to the latest non-beta resolved the issue. I compared it to a “good” preceding message (granted using AI), and it seems to point to issues with the add-transcode-target-codec mechanism

The profile won’t tell you much. Look at the transcode decision. That will indicate if something needs to be transcoded.

The issue with the error is that it doesn’t transcode since the provided client profile isn’t accepted. So I don’t think it ever gets to that step.

Confirming the same issue on my server. Getting this exact error on my Google TV device — works fine at forced 480p, but any higher quality (which requires transcoding) fails with “An error occurred while attempting to play this video. Please check your connection and try again.”

Server log shows the same rejected directives:

ERROR - [Req#1f0/Transcode] ClientProfileExtra: missing or invalid type parameter
WARN - [Req#1f0/Transcode] ClientProfileExtra: ignoring directive: add-transcode-target-codec(scope=videoTranscodeTarget&scopeName=mp3&scopeType=audioCodec&context=all&protocol=http)
ERROR - [Req#1f0/Transcode] ClientProfileExtra: missing or invalid type parameter
WARN - [Req#1f0/Transcode] ClientProfileExtra: ignoring directive: add-transcode-target-codec(scope=videoTranscodeTarget&scopeName=ac3&scopeType=audioCodec&context=all&protocol=http)
ERROR - [Req#1f0/Transcode] ClientProfileExtra: missing or invalid type parameter
WARN - [Req#1f0/Transcode] ClientProfileExtra: ignoring directive: add-transcode-target-codec(scope=videoTranscodeTarget&scopeName=eac3&scopeType=audioCodec&context=all&protocol=http)
ERROR - [Req#1f0/Transcode] ClientProfileExtra: missing or invalid type parameter
WARN - [Req#1f0/Transcode] ClientProfileExtra: ignoring directive: add-transcode-target-codec(scope=videoTranscodeTarget&scopeName=dca&scopeType=audioCodec&context=all&protocol=http)
ERROR - [Req#1f0/Transcode] ClientProfileExtra: missing or invalid type parameter
WARN - [Req#1f0/Transcode] ClientProfileExtra: ignoring directive: add-transcode-target-codec(scope=videoTranscodeTarget&scopeName=opus&scopeType=audioCodec&context=all&protocol=http)
WARN - [Req#1f0/Transcode] TranscodeUniversalRequest: at least one profile extra directive could not be read

Same pattern as the original report — all the add-transcode-target-codec directives for audio (mp3/ac3/eac3/dca/opus) get rejected for a missing/invalid type parameter, and then the transcode session fails once it actually needs to use one of those targets. Forcing a fixed lower quality (480p) sidesteps it, so it does look like it’s specific to how the app is building the profile-extra string, not a server-side config issue.

Yeah I did some more research and saw some other people having the same issue. It seems like the new beta for Android TV in particular is causing issues with transcoding. Not sure if it’s a new client profile that the public pms hasn’t been updated to accept yet or if it’s an actual bug in the beta. I’m tempted to test the beta pms with the beta app to rule out the former…

Same issue here on Fire TV after the September 18, 2026 update.

I’m seeing the exact same “client profile” bug on my Plex app on Fire TV since the update released on September 18, 2026. The behavior matches what’s described in the original post: [briefly describe what you see, e.g. “the app shows the wrong client profile / resets my profile / fails to load profiles”].

Device: Fire TV Stick
Plex app version: 2026.18.0 (971050448)
Server version: 1.43.4.10903

Happy to provide logs or more details if it helps with debugging.

[Req#2455/Transcode] ClientProfileExtra: missing or invalid type parameter