Question
System Environment:
- OS: Ubuntu 18.04
- Tizen Studio Version: 3.0
Problem Description: When creating a new profile in Certificate Manager and author certificate, the passwords are not being stored persistently. After closing and reopening Certificate Manager:
- Passwords appear reset with unknown values (shown as dots in password fields)
- Attempting to re-enter passwords doesn't resolve the issue
- .pwd files listed in tizen-studio-data/profiles/profile.xml are missing
- Applications fail to run on both emulator and physical devices with error: java.io.IOException: Invalid password
- No error messages appear in terminal output
Answer
Problem Understanding
This appears to be a known issue specific to Tizen Studio 3.0 where:
- Certificate Manager fails to properly store passwords
- Required .pwd files are not being generated
- The issue occurs across different operating systems (Ubuntu and Windows)
Solution Methods
-
Downgrade to Tizen Studio 2.5
- Perform a clean uninstall of Tizen Studio 3.0
- Delete all existing profiles
- Install Tizen Studio 2.5
- Configure package sources to use 2.5 branch and disable upgrades
- Note: This will limit development to pre-5.0 platforms
-
Try Samsung Certificate Extension (for SmartTV development)
- Open Package Manager in Tizen Studio
- Navigate to "Extension SDK" tab
- Install "Samsung Certificate Extension"
- This has resolved password storage issues for some SmartTV developers
-
Wait for Tizen Studio 3.1 Update
- Samsung has acknowledged this as a bug related to author certificate expiration
- A patch is being prepared and will be included in Tizen Studio 3.1
- Check for updates in Package Manager
-
Manual Workaround (Advanced Users)
- Create .pwd files manually in tizen-studio-data/profiles/
- Format should match existing profile.xml entries
- Store passwords in plaintext (not recommended for security)
Additional Tips
- Always create certificates with non-root privileges
- Ensure your system meets all prerequisites for Tizen Studio
- If the issue persists after trying these solutions, consider:
- Reporting the bug on Samsung's official bug tracker
- Providing detailed reproduction steps
- Including your system configuration details
