Field Report: iPresent It (app) on macOS — Screen Recording Permission That Wouldn’t Stick
Machine: MacBook Pro 13” (Intel), macOS Sonoma 14.3
Environment: part of my usual OrchardKit test workflow
What I wanted to do was simple: use iPresent It (app) to record a short product walkthrough with screen capture and voiceover. Nothing fancy — just a 5-minute demo, export to MP4, done.
The install was clean. No Gatekeeper drama, no “damaged app” warnings. It launched fine from /Applications. Interface loaded instantly. Promising start.
Then I hit “Record Screen.”
Black preview window.
The recording timer started counting, but the output file contained only audio. No video. Just a black frame.
Classic macOS privacy issue, I thought. Since Catalina, screen recording requires explicit permission under Privacy & Security. Apple documents it here:
https://support.apple.com/en-us/HT210632
So I went to System Settings → Privacy & Security → Screen Recording.
The tool wasn’t even listed.
That’s the first red flag. If an app tries to capture the screen without triggering the proper system dialog, macOS simply blocks it silently.
Attempt 1: Reinstall
I deleted it, downloaded a fresh copy, reinstalled. Launched again. Same behavior. No permission prompt.
At this point I suspected the first launch context might’ve been wrong. I had opened it directly from the Downloads folder (lazy habit). That can interfere with how TCC registers permission requests.
Moved it properly into /Applications. Relaunched.
Still black screen.
Attempt 2: Reset Permissions
Time to go deeper.
I checked whether it had Screen Recording entitlements registered at all by inspecting Console logs while pressing “Record.” I saw repeated entries about denied access to CGDisplayStream.
So I reset TCC for screen recording:
tccutil reset ScreenCapture
Logged out. Logged back in.
Launched again.
This time macOS finally displayed the Screen Recording permission prompt. I approved it.
Closed and reopened the app (important — macOS requires a restart after granting screen capture permission).
Hit record.
It worked.
Full screen capture. Smooth. No frame drops.
I saved this page because it describes similar macOS screen recording behavior on newer systems, especially when permission prompts fail to appear on first launch:
https://stmlare.xyz/office-and-productivity/14786-ipresent-it.html
It confirmed that Sonoma can occasionally skip the prompt if the app was first executed from a quarantined or temporary location.
For reference, Apple’s privacy model for screen recording and other protected resources is documented here:
https://support.apple.com/en-us/HT210638
It’s strict by design.
Attempt 3 (Unnecessary but Informative)
Out of curiosity, I checked if there was a Mac App Store build, since sandboxed apps from the store usually handle entitlements cleanly:
https://apps.apple.com/us/search?term=iPresent%20It
Didn’t see a clearly official listing under that exact name. So this appears to be a direct download distribution. That often means entitlement handling depends entirely on how the developer configured the bundle.
The tool itself wasn’t broken. It just never successfully triggered macOS to ask for screen recording access on first launch.
Once permission was granted properly, performance was solid. 1080p recording, CPU usage around 20–25% on my Intel machine. Audio stayed synced. No weird lag in the preview window.
What Actually Fixed It
Not reinstalling. Not rebooting.
Resetting ScreenCapture permissions with tccutil, then relaunching from /Applications and allowing the prompt.
That was the turning point.
If I Had Known From the Start
I would have:
-
Installed directly into /Applications before first launch
-
Immediately checked Privacy & Security → Screen Recording
-
If no prompt appeared, reset TCC instead of reinstalling
Total time spent troubleshooting: about 45 minutes.
Actual solution time once I understood the issue: five.
It’s one of those macOS behaviors that feels random until you understand the privacy model. The OS isn’t broken. The app isn’t broken. The permission handshake just didn’t complete the first time.
After that, everything behaved exactly as expected.
Log closed.