ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Mobile & games · #xcode
When developing modular architectures in Xcode, managing the visibility of types across different targets is critical for maintaining a clean API. Swift provides internal as the default access level, which restricts visibility to the defining module, and public for external access. A design challenge arises when a type must be visible to an external module,
Context I am designing date handling for an iOS app (Xcode 15+, Swift, targeting iOS 15 and later) that stores event times on a server and displays them to users who travel across regional time zones. The hard constraint is that stored values must round-trip deterministically, while the UI must always reflect the user's current device time zone. The trade-of
An Objective-C project that breaks right after an Xcode upgrade is often recovered by clearing DerivedData and rebuilding. The open question is what happens when that rebuild links object files from two toolchains — stale objects from the old configuration, or a prebuilt static library compiled against an earlier SDK. The Objective-C non-fragile ABI and the
Native Build Error Surfacing The flutter build command orchestrates native build systems, specifically Gradle for Android and xcodebuild for iOS. By default, the Flutter CLI filters the output from these toolchains to provide a streamlined experience, often resulting in a generic "Build failed" message when a native-level error occurs, such as a dependency r
Choosing between Clean Build Folder and full DerivedData removal is a recurring decision when incremental builds appear to retain outdated artifacts. Xcode stores build products, indexes and module caches under DerivedData. Clean Build Folder is documented as targeting the project's build products for the active scheme, while deleting DerivedData removes cac
After a failed Xcode upgrade, the application may stay at the previous version while the system still references a partially upgraded bundle, causing the developer directory reported by xcode-select to be missing. A clean reinstall of Xcode can restore the correct bundle, but it is unclear whether the first‑launch tasks that install optional components such
swift
gradle