SecureTransport error: (null) when pulling with GitUp

[ZhuCanle]

Description

When using GitUp to pull from remote with HTTPS, I encounter a SecureTransport error: (null) popup.
And the pull works correctly when executed via git pull command.

This issue dose not occur consistently, it is intermittent.

Steps to Reproduce

1. Open GitUp and select the repository.
2. Shortcut command + p, then click Pull Branch button.
3. Observe the popup: SecureTransport error: (null).

Expected Behavior

Successfully perform pull operations.

Environment

• GitUp version: 1.4.1 (1050)
• macOS version: Sequoia 15.5
• Git version: 2.39.5

[lucasderraugh]

Does 1.4.3 resolve the issue? If not latest stable does the continuous channel beta build work (1.5.0)?

[ZhuCanle]

Does 1.4.3 resolve the issue? If not latest stable does the continuous channel beta build work (1.5.0)?

I’ve followed your suggestion and downloaded 1.4.3 version.
I noticed the appcast changed that mentioned in the release note. Earlier, when I was using the Check for Updates feature, it kept saying I was already on the latest version.
Since this issue is intermittent and doesn’t happen every time, I’ll need to test it for a while. I’ll follow up here and let you know.

[lucasderraugh]

Yes, we migrated off using Amazon S3 to host GitUp updates but there wasn't a good way to force old clients to change hosting locations.