Alex, In the ticket Volker filled look at the full stack trace:
https://bugreports.qt.io/secure/attachment/114014/crashreport.txt <https://bugreports.qt.io/secure/attachment/114014/crashreport.txt> Crashed Thread: 5 Dispatch queue: com.apple.root.default-qos Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Termination Reason: Namespace TCC, Code 0x0 Thread 5 Crashed:: Dispatch queue: com.apple.root.default-qos 0 libsystem_kernel.dylib 0x00007fff6f5c1ad6 __abort_with_payload + 10 1 libsystem_kernel.dylib 0x00007fff6f5c33df abort_with_payload_wrapper_internal + 80 2 libsystem_kernel.dylib 0x00007fff6f5c3411 abort_with_payload + 9 3 com.apple.TCC 0x00007fff65c6959f __CRASHING_DUE_TO_PRIVACY_VIOLATION__ + 163 4 com.apple.TCC 0x00007fff65c67531 __TCCAccessRequest_block_invoke.114 + 500 5 com.apple.TCC 0x00007fff65c67a58 __tccd_send_message_block_invoke + 231 6 libxpc.dylib 0x00007fff6f6a61ff _xpc_connection_reply_callout + 36 7 libxpc.dylib 0x00007fff6f6a6187 _xpc_connection_call_reply_async + 69 8 libdispatch.dylib 0x00007fff6f4076c2 _dispatch_client_callout3 + 8 9 libdispatch.dylib 0x00007fff6f41e15d _dispatch_mach_msg_async_reply_invoke + 369 10 libdispatch.dylib 0x00007fff6f4165f9 _dispatch_kevent_worker_thread + 1316 11 libsystem_pthread.dylib 0x00007fff6f661a85 _pthread_wqthread + 362 12 libsystem_pthread.dylib 0x00007fff6f660b77 start_wqthread + 15 This is what happens when the OS terminates the app due to lack of code signing entitlements: Termination Reason: Namespace TCC, Code 0x0 I’ve been here before, just trying to help. Good luck! Best, Nuno > On 10 Oct 2021, at 13:33, Alexander Carôt <alexander_ca...@gmx.net> wrote: > > >>I consider it quite cheap compared with a EV code signing certificate for > >>Windows which is usually >= 250 EUR a year. > > Looks like we misunderstand: > > I don't mind having users to click on an additional button one single time > but I mind having an app crashing without any further info and basically > making it useless. > > On Windows so far audio and video work well without any code signing / > notarization so there is no need for me to pay any money for it anyways. > > Regarding OSX let's see what Volker and friends will figure in how far the > non-existing dialogue is a bug or actually a feature Apple consciously wants. > In the latter case I'd be seriously disappointed because it would basically > assume developers to pay the fee in order to make their app work at all. > > Best > > Alex > > > -- > http://www.carot.de > Email : alexan...@carot.de > Tel.: +49 (0)177 5719797 > > > Gesendet: Sonntag, 10. Oktober 2021 um 14:19 Uhr > Von: "Nuno Santos" <nuno.san...@imaginando.pt> > An: "Alexander Carôt" <alexander_ca...@gmx.net> > Cc: volker.hilshei...@qt.io, interest@qt-project.org > Betreff: Re: [Interest] OSX security – allow dialogue > Alex, > > You need to code sign with entitlements to get rid of this problems on Mac OS > >= 10.14.6 > > From my point of view is already a good reason to pay 99 EUR a year. > > I consider it quite cheap compared with a EV code signing certificate for > Windows which is usually >= 250 EUR a year. > > Regards, > > Nuno > > On 10 Oct 2021, at 12:53, Alexander Carôt <alexander_ca...@gmx.net > <mailto:alexander_ca...@gmx.net>> wrote: > > When the cam is not authorized by the user it will crash upon initialization > because it has no entry in the security settings. > > Running the app via terminal works out because the terminal always has these > permissions. > > With audio it’s more tricky: When the mic is not authorized by the user the > sound input will still launch (and not crash) but it will not capture any > audio data.
_______________________________________________ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
