#swiftpm — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #swiftpm, aggregated by home.social.
-
Xcode Cloud's caching of Swift Package Manager dependencies is incredibly aggressive. If you target a branch rather than a specific version or commit hash, it will happily pull a stale build from three days ago without checking for upstream changes, even if you clean the build folder locally. The only reliable fix is manually clearing the build cache in the App Store Connect portal. Saved me an hour of questioning my sanity today.
-
Xcode Cloud's caching of Swift Package Manager dependencies is incredibly aggressive. If you target a branch rather than a specific version or commit hash, it will happily pull a stale build from three days ago without checking for upstream changes, even if you clean the build folder locally. The only reliable fix is manually clearing the build cache in the App Store Connect portal. Saved me an hour of questioning my sanity today.
-
Xcode Cloud's caching of Swift Package Manager dependencies is incredibly aggressive. If you target a branch rather than a specific version or commit hash, it will happily pull a stale build from three days ago without checking for upstream changes, even if you clean the build folder locally. The only reliable fix is manually clearing the build cache in the App Store Connect portal. Saved me an hour of questioning my sanity today.
-
Xcode Cloud's caching of Swift Package Manager dependencies is incredibly aggressive. If you target a branch rather than a specific version or commit hash, it will happily pull a stale build from three days ago without checking for upstream changes, even if you clean the build folder locally. The only reliable fix is manually clearing the build cache in the App Store Connect portal. Saved me an hour of questioning my sanity today.
-
Xcode Cloud's caching of Swift Package Manager dependencies is incredibly aggressive. If you target a branch rather than a specific version or commit hash, it will happily pull a stale build from three days ago without checking for upstream changes, even if you clean the build folder locally. The only reliable fix is manually clearing the build cache in the App Store Connect portal. Saved me an hour of questioning my sanity today.
-
[Перевод] Flutter 3.44 — Что нового во Flutter?
Google I/O 2026. Flutter 3.44 уже здесь, и это грандиозное событие! Этот релиз знаменует собой важную веху в истории Flutter: Hybrid Composition++ для Android, Swift Package Manager в качестве нового менеджера пакетов по умолчанию для iOS/macOS и улучшенную поддержку Vulkan для Impeller. Мы представляем предварительную версию поддержки многооконного режима для настольных компьютеров, и Canonical станет нашим новым ведущим разработчиком, а также начинаем масштабную архитектурную эволюцию, отделяя Material и Cupertino от основного фреймворка. Мы переосмысливаем UX для агентного взаимодействия с пользователями с помощью GenUl и переосмысливаем опыт разработчиков с помощью Agentic Hot Reload и Dart & Flutter Agent Skills. Flutter расширяет возможности приложений следующего поколения — повсюду, от мультимедийной системы Toyota RAV4 2026 года до грядущего SDK для webOS от LG. Мы очень рады поделиться с вами всеми новостями и обновлениями; добро пожаловать в Flutter 3.44!
https://habr.com/ru/articles/1037518/
#dart #flutter #344 #LiteRTLM #flutter_gemma #A2UI_protocol #SwiftPM #Canonical #Toyota_Embedded #LG_WebOS
-
Xcode 26.4 introduces package traits from SwiftPM 6.1, letting package authors expose configurable options to consumers. Enable optional dependencies and conditional compilation — a powerful solution for transitive dependency management.
🔗: https://www.massicotte.org/blog/package-traits-in-xcode/ by Matt Massicotte (@mattiem)
-
Пишем декларативный Package.swift: DSL для модульной архитектуры iOS проекта
Swift Package Manager отлично подходит для модульной архитектуры, но по мере роста проекта Package.swift быстро превращается в длинный список строковых зависимостей. В статье показываю, как превратить Package.swift в типобезопасный DSL на Swift: - убрать строковые зависимости - автоматически генерировать feature-модули - зафиксировать архитектурные правила на уровне компиляции
https://habr.com/ru/articles/1010564/
#swift #swiftpm #dsl #swift_package_manager #ios #ios_development #modularity
-
Пишем декларативный Package.swift: DSL для модульной архитектуры iOS проекта
Swift Package Manager отлично подходит для модульной архитектуры, но по мере роста проекта Package.swift быстро превращается в длинный список строковых зависимостей. В статье показываю, как превратить Package.swift в типобезопасный DSL на Swift: - убрать строковые зависимости - автоматически генерировать feature-модули - зафиксировать архитектурные правила на уровне компиляции
https://habr.com/ru/articles/1010564/
#swift #swiftpm #dsl #swift_package_manager #ios #ios_development #modularity
-
Пишем декларативный Package.swift: DSL для модульной архитектуры iOS проекта
Swift Package Manager отлично подходит для модульной архитектуры, но по мере роста проекта Package.swift быстро превращается в длинный список строковых зависимостей. В статье показываю, как превратить Package.swift в типобезопасный DSL на Swift: - убрать строковые зависимости - автоматически генерировать feature-модули - зафиксировать архитектурные правила на уровне компиляции
https://habr.com/ru/articles/1010564/
#swift #swiftpm #dsl #swift_package_manager #ios #ios_development #modularity
-
Пишем декларативный Package.swift: DSL для модульной архитектуры iOS проекта
Swift Package Manager отлично подходит для модульной архитектуры, но по мере роста проекта Package.swift быстро превращается в длинный список строковых зависимостей. В статье показываю, как превратить Package.swift в типобезопасный DSL на Swift: - убрать строковые зависимости - автоматически генерировать feature-модули - зафиксировать архитектурные правила на уровне компиляции
https://habr.com/ru/articles/1010564/
#swift #swiftpm #dsl #swift_package_manager #ios #ios_development #modularity
-
"Added the ability to enable package traits on dependencies from the Package Dependencies view. (141748785)"
There are a ton of goodies in the release notes, but this one earns a well-deserved #Finally
-
"Added the ability to enable package traits on dependencies from the Package Dependencies view. (141748785)"
There are a ton of goodies in the release notes, but this one earns a well-deserved #Finally
-
"Added the ability to enable package traits on dependencies from the Package Dependencies view. (141748785)"
There are a ton of goodies in the release notes, but this one earns a well-deserved #Finally
-
"Added the ability to enable package traits on dependencies from the Package Dependencies view. (141748785)"
There are a ton of goodies in the release notes, but this one earns a well-deserved #Finally
-
So I’m in the market for a #TypeForm style service with a good #Swift and #SwiftUI integration. I’d love to use TypeForm and the #swiftpm package that gives it a nice native integration to be able to collect in-app feedback from my users but their free tier is really limited and their paid tiers start at too high of a price to be worth it.. (I expect more than 10 submissions a month but not enough to justify to pay [that much] for it).
Yes I know I could just open an email client but so like the coneceptnof having the whole support / suggest / bug report flow in the app and only send replies per mail if needed.
-
So I’m in the market for a #TypeForm style service with a good #Swift and #SwiftUI integration. I’d love to use TypeForm and the #swiftpm package that gives it a nice native integration to be able to collect in-app feedback from my users but their free tier is really limited and their paid tiers start at too high of a price to be worth it.. (I expect more than 10 submissions a month but not enough to justify to pay [that much] for it).
Yes I know I could just open an email client but so like the coneceptnof having the whole support / suggest / bug report flow in the app and only send replies per mail if needed.
-
So I’m in the market for a #TypeForm style service with a good #Swift and #SwiftUI integration. I’d love to use TypeForm and the #swiftpm package that gives it a nice native integration to be able to collect in-app feedback from my users but their free tier is really limited and their paid tiers start at too high of a price to be worth it.. (I expect more than 10 submissions a month but not enough to justify to pay [that much] for it).
Yes I know I could just open an email client but so like the coneceptnof having the whole support / suggest / bug report flow in the app and only send replies per mail if needed.
-
So I’m in the market for a #TypeForm style service with a good #Swift and #SwiftUI integration. I’d love to use TypeForm and the #swiftpm package that gives it a nice native integration to be able to collect in-app feedback from my users but their free tier is really limited and their paid tiers start at too high of a price to be worth it.. (I expect more than 10 submissions a month but not enough to justify to pay [that much] for it).
Yes I know I could just open an email client but so like the coneceptnof having the whole support / suggest / bug report flow in the app and only send replies per mail if needed.
-
So I’m in the market for a #TypeForm style service with a good #Swift and #SwiftUI integration. I’d love to use TypeForm and the #swiftpm package that gives it a nice native integration to be able to collect in-app feedback from my users but their free tier is really limited and their paid tiers start at too high of a price to be worth it.. (I expect more than 10 submissions a month but not enough to justify to pay [that much] for it).
Yes I know I could just open an email client but so like the coneceptnof having the whole support / suggest / bug report flow in the app and only send replies per mail if needed.
-
Swift Package: SwiftExtras https://wesleydegroot.nl/blog/swift-package-swiftextras #SwiftPM #SwiftExtras
-
Swift Package: SwiftCronParser https://wesleydegroot.nl/blog/swift-package-swiftcronparser #SwiftPM# SwiftCronParser
-
Swift Package: NetworkMonitor https://wesleydegroot.nl/blog/swift-package-networkmonitor #SwiftPM# NetworkMonitor
-
Swift Package: PreventScreenshot https://wesleydegroot.nl/blog/swift-package-preventscreenshot #SwiftPM# PreventScreenshot
-
Swift Package: XCUITestHelper https://wesleydegroot.nl/blog/swift-package-xcuitesthelper #SwiftPM# XCUITestHelper
-
Swift Package: SecureStorage https://wesleydegroot.nl/blog/swift-package-securestorage #SwiftPM# SecureStorage
-
Swift Package: iCloudStorage https://wesleydegroot.nl/blog/swift-package-icloudstorage #SwiftPM# iCloudStorage
-
Swift Package: FilePicker https://wesleydegroot.nl/blog/swift-package-filepicker #SwiftPM# FilePicker
-
🚀 New write-up: Extreme Packaging — my approach to modular Swift architecture
I’ve been experimenting with project structures where *every responsibility is its own Swift Package*.
The result: cleaner boundaries, faster builds, and reusable code between iOS & macOS apps.Full article 👉 https://aleahim.com/ExtremePackaging
#Swift #iOSDev #macOS #SwiftPM #CleanArchitecture #OpenSource #SwiftLang
-
Swift Package: ImagePicker https://wesleydegroot.nl/blog/swift-package-imagepicker #SwiftPM# ImagePicker
-
SwiftPM's file-disk footprint can hinder caching optimizations. Our mirror of the Swift Package Index directory solves this, making downloads and caching faster, saving you time on every run.
-
I wonder why #SwiftPM build plugins have not gained broader usage (at least that's my impression)? Do they slow build times, are they too clunky to develop, something else?
-
This .editorconfig file should be added to every single #SwiftPM repo out there! 👇
https://gist.github.com/Jeehut/e5b7559da355a1f243d9c012fe63edc4It ensures that everyone editing the package in Xcode will get the same indentation settings avoiding mismatches with their global settings. 🥳
Add it now! 💯 #iOSDev #OpenSource #SwiftLang #XcodeTips
-
ticked off at whoever decided SwiftPM wasn't gonna support multiple packages per Git repo (ignoring local package references)
c'mon, you can't tell me anyone enjoys duplicating CI config, etc. across multiple repos, and SPM packages are a nice way to structure code otherwise.
-
This .editorconfig file should be added to every single #SwiftPM repo out there! 👇
https://gist.github.com/Jeehut/e5b7559da355a1f243d9c012fe63edc4It ensures that in Xcode 16+ everyone editing the package will get the same indentation settings avoiding mismatches with their global settings. 🥳
Add it now! 💯 #iOSDev #OpenSource
-
#SwiftPM with resources in production and test target work in Xcode.
`swift test` on the CLI fails to load NSColor from Asset catalog, though. The catalog is part of the library.
Is that some CLI thing?
Is Bundle.module pointing at the wrong one?
-
One of the most underrated aspects of #SwiftPM is the bundle structure by convention and not by referencing individual source code files as it happens in #Xcode project bundles. 🙏
I am thankful for that on every merge conflict I have to resolve.
Would every source code file still be referenced as in an Xcode project file, it would totally wreck it during rebases all the time. 😀
-
I occasionally hear the misconception amongst iOS devs that SwiftPM will resolve/clone every dependency in the graph, including test dependencies added by dependent packages. This is not true since SE-0226.
Since Swift 5.2, SwiftPM will compute the graph needed only by the specific products you add from a package. Because test dependencies will never be added to those production targets, they should never be included in resolved graph.
-
I’m trying to make a #swift package that vends at least two libraries.
The package builds each library fine, and I had no problem importing the first library into my app, but when I try to import the second library, it tells me “Cannot find ‘Foo’ in package. Did you mean ‘Foo’”
I’ve been fighting this for a few days. Any advice or pointers to projects I can learn from? #SwiftPM
-
If you asked how @SwiftStudio going. Well... it been better. Apple #Swift just recently decided to shutdown #SwiftPM API I use (to make things CLI cannot provide). I find it unexpected (to me, not to apple) move after many years. https://github.com/apple/swift-package-manager/issues/7440
I'm disappointed with a move in that direction and find that decision harmful for the third-party dev tooling ecosystem trying to adopt SwiftPM. IMHO.
-
I'm thinking about moving some models to a Swift Package.
I wanted to do that some time ago but couldn't find a way to exclude development assets from a package when building in Release (Archive). I currently have files in my "Preview Content" folder that are used for Previews with Core Data.
Is that still the same?
-
Swift Developers! Have you heard of the package-registry added in Swift 5.7 already? I think this is going to be great once broadly adopted. Definitely worth taking a look into 😉
#Swift #SwiftPM #SwiftPackageRegistry
https://lukaspistrol.com/blog/what-is-swift-package-registry?ref=Mastodon
-
Swift Developers! Have you heard of the package-registry added in Swift 5.7 already? I think this is going to be great once broadly adopted. Definitely worth taking a look into 😉
#Swift #SwiftPM #SwiftPackageRegistry
https://lukaspistrol.com/blog/what-is-swift-package-registry?ref=Mastodon
