Re: App can't be opened
Thanks a lot for the insight. Best regards, Gabriel smime.p7s Description: S/MIME cryptographic signature ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: App can't be opened
Hey, > On Sep 15, 2021, at 11:38 AM, Gabriel Zachmann via Cocoa-dev > wrote: > > Thanks so much! I guess that missing symbol explains the crash. > > BTW: is it possible, to make Xcode produce an error message when I am using > symbols that are not available on the deployment target? > (unless they are guarded by @available() ...) Normally, that does happen automatically. However, in this case, it appears that AVAudioSessionInterruptionNotification is missing an availability annotation for macOS. The compiler interprets this as meaning “symbol is always available” and doesn’t warn you. Since the online docs say that AVAudioSessionInterruptionNotification only became publicly available in macOS 11.0, I suspect this is a bug in the AVFAudio headers. (This is a somewhat frequent occurrence as iOS APIs get moved over to macOS—often to support Catalyst—without a thorough audit of the headers.) Matt ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: App can't be opened
Thanks so much! I guess that missing symbol explains the crash. BTW: is it possible, to make Xcode produce an error message when I am using symbols that are not available on the deployment target? (unless they are guarded by @available() ...) Best regards, Gabriel > On 9. Sep 2021, at 20:30, Carl Hoefs wrote: > > On a 10.13 system, your app gives this in the console log: > > opendirectoryd: Authentication failed for with result > ODErrorCredentialsInvalid > opendirectoryd: ODRecordVerifyPassword failed with result > ODErrorCredentialsInvalid > > The (extensive) crash log has this at the top: > > Crashed Thread:0 > > Exception Type:EXC_CRASH (SIGABRT) > Exception Codes: 0x, 0x > Exception Note:EXC_CORPSE_NOTIFY > > Termination Reason:DYLD, [0x4] Symbol missing > > Application Specific Information: > dyld: launch, loading dependent libraries > > Dyld Error Message: > Symbol not found: _AVAudioSessionInterruptionNotification > Referenced from: /Applications/ArtSaverApp.app/Contents/MacOS/ArtSaverApp > Expected in: > /System/Library/Frameworks/AVFoundation.framework/Versions/A/AVFoundation > in /Applications/ArtSaverApp.app/Contents/MacOS/ArtSaverApp > > -Carl > smime.p7s Description: S/MIME cryptographic signature ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: App can't be opened
On a 10.13 system, your app gives this in the console log: opendirectoryd: Authentication failed for with result ODErrorCredentialsInvalid opendirectoryd: ODRecordVerifyPassword failed with result ODErrorCredentialsInvalid The (extensive) crash log has this at the top: Crashed Thread:0 Exception Type:EXC_CRASH (SIGABRT) Exception Codes: 0x, 0x Exception Note:EXC_CORPSE_NOTIFY Termination Reason:DYLD, [0x4] Symbol missing Application Specific Information: dyld: launch, loading dependent libraries Dyld Error Message: Symbol not found: _AVAudioSessionInterruptionNotification Referenced from: /Applications/ArtSaverApp.app/Contents/MacOS/ArtSaverApp Expected in: /System/Library/Frameworks/AVFoundation.framework/Versions/A/AVFoundation in /Applications/ArtSaverApp.app/Contents/MacOS/ArtSaverApp -Carl > On Sep 9, 2021, at 10:54 AM, Jack Brindle via Cocoa-dev > wrote: > > In 10.13 this is not a Notarization problem. It could be a quarantine > problem, though. Have him move the application to any directory other than > the one where he unzipped the app, then launch the app. That should remove > the quarantine and allow him to run the app if that was the problem. The > Applications folder is a good place to move these things. > > Jack > > >> On Sep 9, 2021, at 12:45 PM, Rob Petrovec via Cocoa-dev >> wrote: >> >> The text in an error dialog is typically a washed down version of the actual >> error. See if you can get the user to give you a sysdiagnose log, taken >> just after reproducing the problem, so you can check out the .logarchive to >> see what the actual error was from the system. It should provide more >> insight into what the problem actually is. >> >> btw, if you sent the app as a zip file you should double check the >> permissions on the app, including its bundle contents. Your uid may not be >> the same has the users uid, so the privs could be set to not allow anyone >> but you to open it. Thats why installers are better than sending the raw >> bits. >> >> —Rob >> >> >>> On Sep 9, 2021, at 7:13 AM, Gabriel Zachmann via Cocoa-dev >>> mailto:cocoa-dev@lists.apple.com>> wrote: >>> >>> I have compiled my app for macOS 10.12, because one user runs macOS 10.13. >>> >>> Now he reports that he gets the error message "app can't be opened due to a >>> problem" >>> (the err message is in German, but I guess this is what it would say in >>> English.) >>> >>> The error message does NOT say ".. unidentified developer" >>> and it does NOT say ".. cannot check it for malicious software". >>> >>> I have notarized my app using Xcode's Archive utility. >>> I sent the user the app as a zip file - if you want , you can try it for >>> yourself: >>> >>> https://owncloud.informatik.uni-bremen.de/index.php/s/9i3DCYodkgHZeZw >>> >>> It goes without saying that I can run the app from that very zip file on my >>> Mac. >>> >>> Does anyone have an idea what might be causing this funny error message? >>> >>> Best, G. >>> >>> ___ >>> >>> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) >>> >>> Please do not post admin requests or moderator comments to the list. >>> Contact the moderators at cocoa-dev-admins(at)lists.apple.com >>> >>> Help/Unsubscribe/Update your Subscription: >>> https://lists.apple.com/mailman/options/cocoa-dev/petrock%40mac.com >>> <https://lists.apple.com/mailman/options/cocoa-dev/petrock%40mac.com> >>> >>> This email sent to petr...@mac.com <mailto:petr...@mac.com> >> >> ___ >> >> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com >> <mailto:Cocoa-dev@lists.apple.com>) >> >> Please do not post admin requests or moderator comments to the list. >> Contact the moderators at cocoa-dev-admins(at)lists.apple.com >> <http://lists.apple.com/> >> >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/cocoa-dev/jackbrindle%40me.com >> <https://lists.apple.com/mailman/options/cocoa-dev/jackbrindle%40me.com> >> >> This email sent to jackbrin...@me.com <mailto:jackbrin...@me.com> > ___ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > Please do not
Re: App can't be opened
In 10.13 this is not a Notarization problem. It could be a quarantine problem, though. Have him move the application to any directory other than the one where he unzipped the app, then launch the app. That should remove the quarantine and allow him to run the app if that was the problem. The Applications folder is a good place to move these things. Jack > On Sep 9, 2021, at 12:45 PM, Rob Petrovec via Cocoa-dev > wrote: > > The text in an error dialog is typically a washed down version of the actual > error. See if you can get the user to give you a sysdiagnose log, taken just > after reproducing the problem, so you can check out the .logarchive to see > what the actual error was from the system. It should provide more insight > into what the problem actually is. > > btw, if you sent the app as a zip file you should double check the > permissions on the app, including its bundle contents. Your uid may not be > the same has the users uid, so the privs could be set to not allow anyone but > you to open it. Thats why installers are better than sending the raw bits. > > —Rob > > >> On Sep 9, 2021, at 7:13 AM, Gabriel Zachmann via Cocoa-dev >> mailto:cocoa-dev@lists.apple.com>> wrote: >> >> I have compiled my app for macOS 10.12, because one user runs macOS 10.13. >> >> Now he reports that he gets the error message "app can't be opened due to a >> problem" >> (the err message is in German, but I guess this is what it would say in >> English.) >> >> The error message does NOT say ".. unidentified developer" >> and it does NOT say ".. cannot check it for malicious software". >> >> I have notarized my app using Xcode's Archive utility. >> I sent the user the app as a zip file - if you want , you can try it for >> yourself: >> >> https://owncloud.informatik.uni-bremen.de/index.php/s/9i3DCYodkgHZeZw >> >> It goes without saying that I can run the app from that very zip file on my >> Mac. >> >> Does anyone have an idea what might be causing this funny error message? >> >> Best, G. >> >> ___ >> >> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) >> >> Please do not post admin requests or moderator comments to the list. >> Contact the moderators at cocoa-dev-admins(at)lists.apple.com >> >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/cocoa-dev/petrock%40mac.com >> <https://lists.apple.com/mailman/options/cocoa-dev/petrock%40mac.com> >> >> This email sent to petr...@mac.com <mailto:petr...@mac.com> > > ___ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com > <mailto:Cocoa-dev@lists.apple.com>) > > Please do not post admin requests or moderator comments to the list. > Contact the moderators at cocoa-dev-admins(at)lists.apple.com > <http://lists.apple.com/> > > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/cocoa-dev/jackbrindle%40me.com > <https://lists.apple.com/mailman/options/cocoa-dev/jackbrindle%40me.com> > > This email sent to jackbrin...@me.com <mailto:jackbrin...@me.com> ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: App can't be opened
The text in an error dialog is typically a washed down version of the actual error. See if you can get the user to give you a sysdiagnose log, taken just after reproducing the problem, so you can check out the .logarchive to see what the actual error was from the system. It should provide more insight into what the problem actually is. btw, if you sent the app as a zip file you should double check the permissions on the app, including its bundle contents. Your uid may not be the same has the users uid, so the privs could be set to not allow anyone but you to open it. Thats why installers are better than sending the raw bits. —Rob > On Sep 9, 2021, at 7:13 AM, Gabriel Zachmann via Cocoa-dev > wrote: > > I have compiled my app for macOS 10.12, because one user runs macOS 10.13. > > Now he reports that he gets the error message "app can't be opened due to a > problem" > (the err message is in German, but I guess this is what it would say in > English.) > > The error message does NOT say ".. unidentified developer" > and it does NOT say ".. cannot check it for malicious software". > > I have notarized my app using Xcode's Archive utility. > I sent the user the app as a zip file - if you want , you can try it for > yourself: > >https://owncloud.informatik.uni-bremen.de/index.php/s/9i3DCYodkgHZeZw > > It goes without saying that I can run the app from that very zip file on my > Mac. > > Does anyone have an idea what might be causing this funny error message? > > Best, G. > > ___ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > Please do not post admin requests or moderator comments to the list. > Contact the moderators at cocoa-dev-admins(at)lists.apple.com > > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/cocoa-dev/petrock%40mac.com > > This email sent to petr...@mac.com ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
App can't be opened
I have compiled my app for macOS 10.12, because one user runs macOS 10.13. Now he reports that he gets the error message "app can't be opened due to a problem" (the err message is in German, but I guess this is what it would say in English.) The error message does NOT say ".. unidentified developer" and it does NOT say ".. cannot check it for malicious software". I have notarized my app using Xcode's Archive utility. I sent the user the app as a zip file - if you want , you can try it for yourself: https://owncloud.informatik.uni-bremen.de/index.php/s/9i3DCYodkgHZeZw It goes without saying that I can run the app from that very zip file on my Mac. Does anyone have an idea what might be causing this funny error message? Best, G. smime.p7s Description: S/MIME cryptographic signature ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
