ScreenAreaShare icon indicating copy to clipboard operation
ScreenAreaShare copied to clipboard

Screen recording permissions request loop on MacBook (M1) with Sonoma 14.4.1

Open rzbergme opened this issue 1 year ago • 9 comments

Hi,

I am stuck in a screen recording permissions request loop.

Installed screen-area-share version 1.4.1 (screen-area-share-1.4.1-universal.dmg) on a MacBook (M1) running Sonoma 14.4.1

When I launch it, I get the prompt:

image

I click open settings and toggle screen-area-share to allow and it asks me to restart it (quit & reopen):

image

image

But then when it reopens (or if I launch it manually) it just prompts for missing permissions again.

Even a reboot does not help.

Any idea?

Thanks!

rzbergme avatar May 08 '24 16:05 rzbergme

I don't have a Mac at hand to check this - could you maybe try the previous versions? 1.4.1 is the first one being built automatically, the other ones were uploaded manually by other contributors

mPyKen avatar May 08 '24 23:05 mPyKen

Thank you for your work @mPyKen! I am glad to report that version 1.3.3 worked. screen-area-share-1.4.0-arm64.dmg did not work (Mac claimed the .app file was damaged). But screen-area-share-1.3.3-x64.dmg worked. I was able to enable record screen and audio permissions, and it started working. Let me know if you need help troubleshooting what the issue might be with the later versions.

Thanks!

rzbergme avatar May 08 '24 23:05 rzbergme

Glad it worked! There seems to be something missing in the auto build... I would appreciate if any developer on Mac os could investigate this

mPyKen avatar May 09 '24 03:05 mPyKen

Hmm, 1.3.3 does not work for me on M3 mac.

fdoumet avatar May 22 '24 21:05 fdoumet

1.3.3 is an x86 build, it is not compatible with an M3 mac. Could you try the 1.4.0 or 1.4.1 build instead?

mPyKen avatar May 23 '24 00:05 mPyKen

Building the latest master manually does work on macOS 14.5 on my M3 Mac.

MarcelBochtler avatar Jun 12 '24 09:06 MarcelBochtler

Problem still persists on Mac, M1, macOS 15.3.1 here. Couldn't find a workaround.

dxtr0dsgnz avatar Feb 20 '25 10:02 dxtr0dsgnz

Updated dependencies in the latest version (v1.4.2), hoping it to solve this issue. If not - contributions are welcome:)

mPyKen avatar Feb 26 '25 12:02 mPyKen

Thanks, unfortunately still the same problem in 1.4.2.

dxtr0dsgnz avatar Feb 26 '25 12:02 dxtr0dsgnz