obsproject / obsproject/obs-studio
Profile import fails on macOS in 32.2.2: profile name parsed as empty, files copied to profiles root ("File exists" error)
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 76.4k
- Forks
- 10.2k
- Avg merge
- 4d 23h
- Merged PRs (30d)
- 12
Description
Operating System Info
macOS 26
Other OS
No response
OBS Studio Version
32.2.2
OBS Studio Version (Other)
No response
OBS Studio Log URL
https://obsproject.com/logs/D9qeYx8O2TcQ1H8Y
OBS Studio Crash Log URL
No response
Expected Behavior
Importing a profile via Profile → Import should read the profile name from [General] Name= in basic.ini, create a subfolder in basic/profiles/, and copy the profile files into it.
Current Behavior
The profile name is parsed as an empty string, so OBS does not create a subfolder and copies the profile files directly into the root of basic/profiles/. On a second import attempt it fails with:
warning: Failed to copy import file 'basic.ini' for profile '':
filesystem error: in copy_file: File exists ["/Users/[user]/Library/Application Support/obs-studio/basic/profiles/basic.in
Steps to Reproduce
- In OBS 32.2.2 on macOS, create a new profile (e.g. "Testprofile").
- Export it via Profile → Export to any folder (e.g. ~/Downloads/).
- Delete "Testprofile" via Profile → Remove.
- Import that same folder via Profile → Import.
- Observe that no subfolder is created in basic/profiles/ — the profile files are copied into the profiles root instead, and the imported profile does not appear in the Profile menu.
- Repeat the import: OBS logs the "File exists" warning above with an empty profile name.
Anything else we should know?
Manually copying the exported folder into basic/profiles// works fine — the profile loads normally, so the exported data itself is not corrupted. Only the import routine is affected.
The issue appeared for me in 32.2.2; import worked in earlier versions.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with Profile → Import using an exported folder containing basic.ini, then inspect the import path that reads its [General] Name= value. Done means the imported profile appears under the original name in basic/profiles//, and a repeated import no longer copies into the profiles root or reports an empty-name File exists error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, macos
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100