--- title: Issue 762 – iOS Dev Weekly | daily.dev description: iOS Dev Weekly issue 762 covers several Swift and iOS development topics: typed throws in Swift 6 for clearer error handling, type-safe JSON/JSONB support in... canonical: https://daily.dev/posts/issue-762-ios-dev-weekly-7xnerye10 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Issue 762 – iOS Dev Weekly | daily.dev og:description: iOS Dev Weekly issue 762 covers several Swift and iOS development topics: typed throws in Swift 6 for clearer error handling, type-safe JSON/JSONB support in... og:url: https://daily.dev/posts/issue-762-ios-dev-weekly-7xnerye10 og:image: https://api.daily.dev/og/posts/7xnErYe10.png og:image:alt: Issue 762 – iOS Dev Weekly og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Issue 762 – iOS Dev Weekly **[iOS Dev Weekly](https://daily.dev/sources/iosdevweekly)** · 4 min read · 0 upvotes · 0 comments ## Summary iOS Dev Weekly issue 762 covers several Swift and iOS development topics: typed throws in Swift 6 for clearer error handling, type-safe JSON/JSONB support in the StructuredQueries library for SQLite, building testable SwiftData applications with practical refactoring techniques, and a breakdown of SwiftUI's new @ContentBuilder API for non-View types. The newsletter also touches on the Apple vs. OpenAI trade secrets dispute and a SwiftCon conference discount for readers. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How do typed throws work in Swift 6 and why should I use them? Typed throws in Swift 6 let you declare the specific error type a function can throw, making error handling clearer for both API authors and callers. Instead of catching any error, callers know exactly what error types to expect, reducing boilerplate and improving type safety. This feature was long-requested and finally arrived in Swift 6, enabling more expressive and self-documenting error-handling APIs. _Swift developers adopting Swift 6 error patterns track changes like these on daily.dev._ ### How do I build testable SwiftData applications without tight coupling to the persistence layer? Building testable SwiftData apps requires deliberate separation of the persistence layer from the rest of the app. Key practices include avoiding direct SwiftData dependencies in view models and business logic, applying refactoring techniques to isolate data access, and using abstractions that can be swapped in tests. Concrete code examples illustrate what patterns to follow and which anti-patterns to avoid. _iOS engineers keeping SwiftData architectures maintainable find relevant patterns on daily.dev._ ## Similar posts on daily.dev - [Sunday Incident -- Fatbobman's Swift Weekly \#115](https://daily.dev/posts/sunday-incident----fatbobman-s-swift-weekly-115-kflsudzvi) · Fatbobman · 0 upvotes · 0 comments - [Stability > New Features -- Fatbobman's Swift Weekly \#138](https://daily.dev/posts/stability-new-features----fatbobman-s-swift-weekly-138-e3zsz6sd3) · Fatbobman · 0 upvotes · 0 comments - [A Wall Away, Worlds Apart -- Fatbobman's Swift Weekly \#129](https://daily.dev/posts/a-wall-away-worlds-apart----fatbobman-s-swift-weekly-129-lbpukh1cf) · Fatbobman · 0 upvotes · 0 comments --- Tags: [#ios](https://daily.dev/tags/ios), [#swift](https://daily.dev/tags/swift), [#swiftui](https://daily.dev/tags/swiftui) [View this post on daily.dev](https://daily.dev/posts/issue-762-ios-dev-weekly-7xnerye10) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Issue 762 – iOS Dev Weekly","url":"https://daily.dev/posts/issue-762-ios-dev-weekly-7xnerye10","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/issue-762-ios-dev-weekly-7xnerye10"},"datePublished":"2026-08-07T13:19:38.412Z","dateModified":"2026-08-07T13:20:01.514Z","description":"iOS Dev Weekly issue 762 covers several Swift and iOS development topics: typed throws in Swift 6 for clearer error handling, type-safe JSON/JSONB support in...","image":"https://media.daily.dev/image/upload/s--HRgLpUt6--/f_auto/v1722860399/public/Placeholder%2003","thumbnailUrl":"https://media.daily.dev/image/upload/s--HRgLpUt6--/f_auto/v1722860399/public/Placeholder%2003","isAccessibleForFree":true,"articleSection":"iOS Dev Weekly","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"iOS Dev Weekly","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/56213f98c2ed4e2d8662fd109ae3b7ef","url":"https://daily.dev/sources/iosdevweekly"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/issue-762-ios-dev-weekly-7xnerye10","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ios,swift,swiftui","timeRequired":"PT4M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"iOS Dev Weekly","item":"https://daily.dev/sources/iosdevweekly"},{"@type":"ListItem","position":3,"name":"Issue 762 – iOS Dev Weekly"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/issue-762-ios-dev-weekly-7xnerye10#faq","mainEntity":[{"@type":"Question","name":"How do typed throws work in Swift 6 and why should I use them?","acceptedAnswer":{"@type":"Answer","text":"Typed throws in Swift 6 let you declare the specific error type a function can throw, making error handling clearer for both API authors and callers. Instead of catching any error, callers know exactly what error types to expect, reducing boilerplate and improving type safety. This feature was long-requested and finally arrived in Swift 6, enabling more expressive and self-documenting error-handling APIs. Swift developers adopting Swift 6 error patterns track changes like these on daily.dev."}},{"@type":"Question","name":"How do I build testable SwiftData applications without tight coupling to the persistence layer?","acceptedAnswer":{"@type":"Answer","text":"Building testable SwiftData apps requires deliberate separation of the persistence layer from the rest of the app. Key practices include avoiding direct SwiftData dependencies in view models and business logic, applying refactoring techniques to isolate data access, and using abstractions that can be swapped in tests. Concrete code examples illustrate what patterns to follow and which anti-patterns to avoid. iOS engineers keeping SwiftData architectures maintainable find relevant patterns on daily.dev."}}]} ```