Geschrieben February 6, 2026 at 04:586. Feb 2026 Mir ist die Meldung unten im Brickv auf dem macMini aufgefallen. Weiß nicht, seit wann das da steht. Beim MacBook taucht sie nicht aus. Ich bin mir nicht bewusst dass ich etwas umkonfiguriert habe. Eine Idee? Ich finde nichts an Berechtigungen für Brickv ... Werde mal neu installierenmacMini M1, macOS 26.2, neuester Brickv 2.4.26, gerade noch mal installiert.Cheers, Uwe
Geschrieben February 6, 2026 at 08:276. Feb 2026 Same here with Brickv 2.4.24. Weird, because version files seem to be fine here and here. Maybe a code signing thing with Apple?Update: it seems the developer certificate expired.
Geschrieben February 6, 2026 at 09:556. Feb 2026 Completely removed Brickv 2.4.24 using Tinkertool → Rebooted → Installed Brickv 2.4.26 → Still the same problem. bearbeitet February 6, 2026 at 09:576. Feb 2026 von Superp Resized images
Geschrieben February 6, 2026 at 10:236. Feb 2026 There are two different issues. We moved our servers to a new infrastructure and by doing that changed the root ca. Because of that brickv doesn't like to download from tinkerforge.com anymore. Additionally we need to renew the developer cert for the next brickv release, but that is a different issue.
Geschrieben February 8, 2026 at 07:218. Feb 2026 Autor Hmm, I'm pretty sure I run the same version of Brickv on the same version of macOS in my office. There everything runs as expected.
Geschrieben February 13, 2026 at 12:3513. Feb 2026 This morning I pushed an update that enables the Tinkerforge Ruby bindings to check firmware versions. To my surprise it immediately found a Bricklet with outdated firmware.For now it expects you to download latest_versions.txt yourself and put it in either ~/.config/tinkerforge/downloads or /etc/tinkerforge/downloadsThis is still somewhat experimental, your kilometrage may vary, etc. Feel free to port this code to your favourite programming language. bearbeitet February 13, 2026 at 20:0813. Feb 2026 von Superp Restored disappearing screenshot
Geschrieben February 13, 2026 at 14:4113. Feb 2026 Autor Am 6.2.2026 um 11:23 schrieb borg: Because of that brickv doesn't like to download from tinkerforge.com anymore. Please forgive my ignorance. Wouldn't that affect every running brickv running in the world out there? But on my Laptop I do not see this message. Am 6.2.2026 um 11:23 schrieb borg: Additionally we need to renew the developer cert for the next brickv release, but that is a different issue.I hate this traffic sign. Any idea when that release will come?
Geschrieben February 16, 2026 at 14:4316. Feb 2026 I cannot reproduce the download issue here, with two different MacBooks with macOS 15.5 and 26.1.It's not a general issue with our server, but with Python not being able to verify the HTTPS certifcate of our server. We are using Let's Encrypt now. I'm a little puzzled why it should not work. I suspect a problem local to the affected computer.Could you try running this terminal command on the affected computer and post it's output here:curl -v https://download.tinkerforge.comSame with Python please:python3 -c "from urllib.request import urlopen; print(urlopen('https://download.tinkerforge.com').read()[:100])"Yes, the code signing certificate used to sign that version of brickv is expired by now. But that's not a real issue, because the signature is timestamped and at the time brickv was signed the certificate was valid. This version of brickv is still properly signed. There is no issue to be fixed. There will not be a new brickv release just because of that. Apple decided to show this in a too dramatic way, making it look like an issue. This also has nothing to do with the download issue.
Geschrieben February 17, 2026 at 09:1517. Feb 2026 What I wanted to see is not in the curl log file because you only redirected stdout to the log file.Please run this command: curl -v https://download.tinkerforge.com &> curl.txtBut both logs already show that the download is working.
Geschrieben February 17, 2026 at 22:2517. Feb 2026 On 2/16/2026 at 3:43 PM, photron said: Apple decided to show this in a too dramatic way, making it look like an issue.Hold your horses. That is not what happened. I ran into the above problem with Brickv and tried finding the cause. I did some digging and found your developer cert expired a few months ago. That's it: I did some digging.The expired developer certificate worries me a bit whether it is causing this trouble or not, but that is a different conversation.The URL "https://download.tinkerforge.com/latest_versions.txt" works fine with Safari, Curl, Wget, Python3, Ruby, and also Shortcuts. URL https://download.tinkerforge.com/ works too.Brickv reports an error.
Geschrieben February 18, 2026 at 08:2318. Feb 2026 This is stderr for curl -v https://download.tinkerforge.com/latest_versions.txt 2> curl_stderr.txt : curl_stderr.txt
Geschrieben February 18, 2026 at 13:0418. Feb 2026 As I cannot reproduce the problem here I need help. Could anyone that is affected by the download problem run this brickv Github branch from source in a terminal? It prints the exception backtrace to the terminal. I would like to see this backtrace.GitHubGitHub - Tinkerforge/brickv at macos-download-problemSmall Qt GUI to control and test all Bricks and Bricklets from Tinkerforge - GitHub - Tinkerforge/brickv at macos-download-problem
Geschrieben February 18, 2026 at 14:2218. Feb 2026 I am willing to try, and have checked out that branch. However, I have no experience with the Python toolchain and so far have not succeeded in getting this running. I'll try again later.
Geschrieben February 18, 2026 at 15:1018. Feb 2026 Autor python seem to be slightly different on both machines. I am not a python person. I probably messed up python on the Mac mini while it is ok for Brickv on the MacBook Pro. There is Python 2.7.18 (python --version, /opt/homebrew/bin/python2) and Python 3.14.3 (python3 --version, /opt/homebrew/bin/python3) on both machines. Probably python installations are slightly different on both machines … But, honestly, I do not know what happens under the hood. I, too, do not succeed to get the Brickv branch running.
Geschrieben February 19, 2026 at 10:0919. Feb 2026 @photron I have tried getting this version of brickv running. No success. I basically do not know what I'm doing trying to "fix" errors with Python.Alternate approach: I have captured brickv's network traffic in a .pcap file, when it 1) Does a clean start 2) Fetches update data 3) Quits.The pcap file is in your email. Maybe it is helpful.
Geschrieben February 19, 2026 at 11:3419. Feb 2026 On 2/19/2026 at 11:09 AM, Superp said:The pcap file is in your email. Maybe it is helpful.Thank you. I can see that connection fails with a certificate error. That's what I expected to be the problem.
Geschrieben February 19, 2026 at 11:4419. Feb 2026 Please try this test version of brickv. Either this one just works now, or it reports an error, that should help me to figure out what's wrong. brickv_macos_2_4_26_snapshot_cf4dbaa.dmg
Geschrieben February 19, 2026 at 12:4419. Feb 2026 It reports an error. Click "OK" and it immediately returns, 3 times in total. The dialog below immediately appears 3-fold, stacked on top of each other: bearbeitet February 19, 2026 at 13:4719. Feb 2026 von Superp Correct/clarify
Geschrieben February 19, 2026 at 17:4019. Feb 2026 Autor Same the messages here on the Mac mini w/ this version. And this version too runs flawlessly on the MacBook Pro (same OS) like the regular one.Why is this behavior so different? bearbeitet February 20, 2026 at 14:2920. Feb 2026 von duaw
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.