ImportBuddy on Apple Silicon macOS

[MrPeteypoo]

Hi, it's pretty frustrating to try and use ImportBuddy on macOS if you have any Apple Silicon chip. I believe a major difference is that when you run third party software you have to explicitly allow each application by entering your password. Unfortunately macOS seems to consider every DLL in the x64 macOS build a different executable so they all must be explicitly allowed one by one, then when you next start and use ImportBuddy it will prompt you to enter your password for each individual DLL. I must've done so about 20 times, either way it's quite painful and I think the solution would be a correctly signed AARCH64 build for Mac?

Here's an example:

[lfoust]

Peter, Thank you for letting me know about this. I don't have a mac and had no idea this is the experience. Unfortunately, it seems that access to a mac to create a signing certificate is required? I found this article discussing how to sign .net builds for mac: https://codingflamingo.com/blog/how-to-code-sign-and-notarize-net-console-app-for-mac Once you entered your password 20 times did ImportBuddy actually run an work on mac? Thanks, Luke

…

________________________________ From: Peter ***@***.***> Sent: Wednesday, December 18, 2024 4:02 AM To: TheDiscDb/data ***@***.***> Cc: Subscribed ***@***.***> Subject: [TheDiscDb/data] ImportBuddy on Apple Silicon macOS (Issue #35) Hi, it's pretty frustrating to try and use ImportBuddy on macOS if you have any Apple Silicon chip. I believe a major difference is that when you run third party software you have to explicitly allow each application by entering your password. Unfortunately macOS seems to consider every DLL in the x64 macOS build a different executable so they all must be explicitly allowed one by one, then when you next start and use ImportBuddy it will prompt you to enter your password for each individual DLL. I must've done so about 20 times, either way it's quite painful and I think the solution would be a correctly signed AARCH64 build for Mac? Here's an example: image.png (view on web)<https://github.com/user-attachments/assets/d9696055-91c5-4acd-aeab-b59b3e7b4a65> — Reply to this email directly, view it on GitHub<#35> or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAAUK5FLFCYPVPGKB3WI26D2GFP4TBFKMF2HI4TJMJ2XIZLTSOBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJLJONZXKZNENZQW2ZNLORUHEZLBMRPXI6LQMWBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTLDTOVRGUZLDORPXI6LQMWSUS43TOVS2M5DPOBUWG44SQKSHI6LQMWVHEZLQN5ZWS5DPOJ42K5TBNR2WLKJTGI3DKOBRGEYTFAVEOR4XAZNFNFZXG5LFUV3GC3DVMWVDENZUG43DENZRGY3KO5DSNFTWOZLSUZRXEZLBORSQ>. You are receiving this email because you are subscribed to this thread. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[MrPeteypoo]

I didn't make it as far as to importing a title as it turned out Lost is already in the database but when I searched on the website it didn't show up. I was able to input the show ID and such via the command line interface. I'll try it again in the future with a different title and report other bugs if I find them.

In regards to signing yes I believe that resource is correct. Mac is a bit weird because there are some differences in what security rules apply based on whether you have an Intel x86_64 Mac or an Apple Silicon Mac. I'm not sure if this problem is exhibited by both variants or just the M series Apple chips. I have an M2 Mac Mini.