Question
I'm testing a Tizen .NET app (targeting Tizen 4.0) on a real Samsung TV. The app builds and packages successfully, and the installation via sdb install appears to complete without errors (showing 100% installation progress). However, the app doesn't appear in the Smart Hub or apps screen.
Additional details:
- Device capabilities show
profile_name:tvandplatform_version:4.0 sdb shellis blocked on this device- Installation was attempted via both
sdb installandtizen.bat
When using tizen.bat to install, the app appears but crashes immediately (while it works fine on emulator). I also can't access logs due to sdb dlog and sdb shell being locked.
Key questions:
- How can I find and launch the installed app?
- Is there a way to unlock
sdb shellon this TV device?
Answer
Problem Understanding
The issue involves two main problems:
- Apps installed via
sdb installdon't appear in the TV interface (though they are actually installed) - Debugging is difficult due to restricted shell access on production TVs
Solution Methods
-
Finding and Launching Installed Apps
- Use these commands to list and launch apps:
# List installed apps sdb shell 0 applist # Launch specific app sdb shell 0 execute APP_ID
- Use these commands to list and launch apps:
-
Alternative Installation Method
- Use
dotnet tizen installinstead ofsdb installfor persistent installation that appears in the Apps section - Note: Installation may show "FAILED" but wait 5 minutes for completion
- Use
-
Debugging Without Shell Access
- Implement try/catch blocks in C# and redirect exceptions to a TCP socket
- Use netcat on your development machine to receive debug messages
Additional Tips
-
On Tizen 4.0 TVs, test apps don't appear in the apps panel by policy
-
Shell access requires partnership status with Samsung
-
App crashes on TV (but not emulator) may be caused by:
- Security policy violations
- PInvoke/DllImport issues
- DLL version conflicts (especially with System assemblies)
-
For dependency conflicts:
- Avoid overriding System DLLs
- Use older package versions if newer ones cause conflicts
- Example working dependency set:
dotnet add package Newtonsoft.Json --version 12.0.3 dotnet add package NAudio --version 1.9.0 dotnet add package HtmlAgilityPack --version 1.11.23
