How to build using a Personal (free) Developer Account

[jmb]

I'm asking here as this isn't really an issue with Cork, but when I follow the instructions to build locally with my Developer ID (free account), I get the following error at the distribute stage: "Personal teams cannot create distribution signing certificates or provisioning profiles."

I selected "Development" as the Provisining Certificate from the MacOS section under Signing and then get: "Distribution requires enrollment in the Apple Developer Program. Visit https://developer.apple.com/account to enroll."

Is my Apple ID configured incorrectly? Any ideas? Thanks!
I wonder if you can't do this with a free account anymore... 😞

[buresdv]

I made a mistake in the instructions. I updated them with more detail, so you should try again.

I thought that personal teams could create distribution packages, but I guess not. You have to choose "Development" in the first step of the export process (point 6). As I said, try going over it again with the new instructions.

[jmb]

Thank you for the update... I followed the instructions and now get this error...

(Team ID redacted)

However, I also tried the Copy App option which appears to work, but I can't run the app anyway as my 2016 MacBook Pro is too old to run MacOS 13! Doh! 🤦🏻

[jmb]

It runs but seems to never load anything - just the spinners and after clicking the refresh button top right it just is stuck on the Pulling updates... pop up.

No worries, I can stick with the command line! 😉

[buresdv]

If you wanna try debugging it, you can pull the branch lower-deployment-target, run it with the play button from Xcode and send me the terminal output. I've had another report by someone who has Brew in a different path than expected, so it might be the problem you're facing. I just need the output to know 😊

[jmb]

Awesome, I think this is the problem.

Here's is the output:

2023-03-10 13:17:28.297498+0000 Cork[72957:40826905] [SwiftUI] No symbol named 'spigot' found in system symbol set
Error Domain=NSCocoaErrorDomain Code=4 "The file “brew” doesn’t exist." UserInfo={NSFilePath=/opt/homebrew/bin/brew}
Error Domain=NSCocoaErrorDomain Code=4 "The file “brew” doesn’t exist." UserInfo={NSFilePath=/opt/homebrew/bin/brew}

[buresdv]

Yeah, it's definitely a problem with the path to the brew command. I'll fix it ASAP, so keep an eye on this issue: #39

[jmb]

Yup, a find and replace to/usr/local/bin/brew works for me running it from Xcode.

[sandydunlop]

Hi, This is what happened for me as well. I discovered the path the app uses for the brew command didn’t match the path on my system. My path is /usr/local/bin/brew whereas the app was expecting /opt/homebrew/bin/brew Is this possibly the case for you? This issue was created for it: #39 Add more possible Brew paths · Issue #39 · buresdv/Cork github.com

…

On 10 Mar 2023, at 12:57, Jonathan Batchelor ***@***.***> wrote: It runs but seems to never load anything - just the spinners and after clicking the refresh button top right it just is stuck on the Pulling updates... pop up. No worries, I can stick with the command line! 😉 — Reply to this email directly, view it on GitHub <#33 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFN3QJ24SVVZZZOE4UG5YQDW3MQKPANCNFSM6AAAAAAVU6MNJY>. You are receiving this because you are subscribed to this thread.

[jmb]

Yes, I use /usr/local/bin/brew

[buresdv]

I will try to implement a fix ASAP, so please keep your eyes on that issue so you know the progress 😊

[buresdv]

Could you guys direct all the comments to issue #39? So I don't have to keep updating it in two places

[sandydunlop]

As a temporary workaround: Create the /opt/homebrew/bin directory and make a symlink in it to /usr/local/bin/brew

…

On 10 Mar 2023, at 13:05, Jonathan Batchelor ***@***.***> wrote: Yes, I use /usr/local/bin/brew — Reply to this email directly, view it on GitHub <#33 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFN3QJ4TEJQAVFWS7T2VMHDW3MRINANCNFSM6AAAAAAVU6MNJY>. You are receiving this because you commented.