I set up this #Swift package to control #Docker Desktop to automatically deploy #Nextcloud containers on #macOS. This will become very handy in automated tests and client development.
| Location | Germany |
| Blog | https://i2h3.de |
Iva Horn
- 87 Followers
- 68 Following
- 261 Posts
Engineering digital sovereignty at @nextcloud. 🌥️ Writes mostly about #iOS, #macOS, #Swift, #Nextcloud and #Apple. 🍏 Likes to overshare about things you could not care less about. 😇
@stepan As I have learned: all the time, the problem was to find an implementation different platform clients can deal with due to lack of standardization. Hence the web front-end was lacking it to avoid the expectation it will work with all other clients that had their own ideas about how to handle repeating tasks.
"The key to making this work is telling Claude Code that a genius game designer who only speaks in cryptic riddles is giving it instructions, add strong guardrails, and build plenty of tools for automated feedback."
🤣
bondolo@goetz Well… Qt does which is the foundation of this project since its inception.
In a native macOS app which uses WKWebView (shipped with macOS) it basically adds no notable overhead. Been there, done that. Integrating that into a Qt app on the other hand is overly complicated and fragile. I did a bit of research into that direction. Actually, QtWebView does that at expense of API features (which we need) due to the platform portability requirement.
@helge If you would like to know what Nextcloud global scale is: https://nextcloud.com/blog/nextcloud-global-scale-how-it-works/
In a nutshell: For that we need to inject custom headers into HTTP requests and also set up custom URL scheme handler interception which is not possible with simple Qt Web View API but requires the whole Qt Web Engine.
The standard login process does not work because it assumes that the initial login server is the one which will provide the final app password which is not the case with global scale.
Finally I figured out why #Xcode could not resolve breakpoints in the #Nextcloud desktop client extensions. 😮💨 That was tricky to trace down.
In a nutshell: Make sure your dSYMs are in a directory indexed by Spotlight and not some dot-directory or other excluded location. 🤪
Xcode Breakpoints in the Nextcloud Desktop Client
When attaching Xcode to the FileProviderExt process of the Nextcloud desktop client, the debugger connected just fine — but every single breakpoint was displayed hollow and in dashes which means Xcode cannot associate the position with a line of code on disk. Tracking down the root cause turned into quite the adventure.