Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
bolha.us is one of the many independent Mastodon servers you can use to participate in the fediverse.
We're a Brazilian IT Community. We love IT/DevOps/Cloud, but we also love to talk about life, the universe, and more. | Nós somos uma comunidade de TI Brasileira, gostamos de Dev/DevOps/Cloud e mais!

Administered by:

Server stats:

249
active users

bolha.us: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#swift

21 posts16 participants2 posts today
Public
rogelin

Help!!!
Does anyone know how to address ITMS-90048: This bundle is invalid - Your archive contains paths that are not allowed: [._Symbols]
My is being rejected from AppStore Connect since Xcode 16.3, and now even switching back to 16.2 or older branches it will give me the same issue.

Not sure what this is exactly…

Any guidance is greatly appreciated
#Xcode #Swift #Apple #iOSDev

Continued thread
Public
Rachel Brindle

The testing attachments proposal has been accepted (with modifications)! To be attached to some upcoming swift version! forums.swift.org/t/accepted-wi

No real negative feedback, either. I guess people quickly became attached to the idea.

There were some disagreements about naming in the review, but I’m glad that we resolved that amicably. I’d really hate it if we were too attached to an idea to come to an agreement.

Swift Forums · [Accepted with Modifications] ST-0009: AttachmentsHello Swift community. The review of ST-0009: Attachments ran from March 20 through April 8, 2025. Feedback on the review was light but positive. There were some concerns about API naming. With that in mind, the Testing Workgroup has decided to accept this proposal with modifications. Specifically, we will change AttachableContainer to AttachableWrapper in order to avoid accidentally using the same term for unrelated features. Thank you to everyone who participated in this review for helping ...
#SwiftLang#swift#testing
Continued thread
Public
Patrick McConnell

Biggest tip I can offer when working through a migration strategy, is to work on a new git branch so you can delete a bad data store, restore the old working branch and start over.

You can create a rollback strategy as well but I found it just as easy to delete the bad data store, revert to working data and try again.

If you don't start a migration clean and it has previously failed you may find a lot of duplicate data once it does work all the way thru.

#SwiftData#Swift#iOSDev
Continued thread
Public
Patrick McConnell

In my case I was migrating from a schema where a relationship was becoming many to many. I needed to gather all the current single relationships in willMigrate and then in didMigrate I had to add them to the new to many relationship.

There is no relationship between willMigrate and didMigrate so you need to do some sketchy (globals) things to pass data across contexts.

Once I'm comfortable I've gotten this all correct, I’ll do a blog post.

#SwiftData#Swift#iOSDev
Public
Patrick McConnell

TIL working with #SwiftData migrations the past few days.

The documentation is non-existent. The sample code, tutorials, etc are all copying mostly trivial examples and sadly each other.

A custom migration schema has two phases each is passed a context. The first, willMigrate, will have the context for the schema you are migrating from, the second, didMigrate will have the newest context.

developer.apple.com/documentat

Apple Developer DocumentationMigrationStage.custom(fromVersion:toVersion:willMigrate:didMigrate:) | Apple Developer DocumentationThere's never been a better time to develop for Apple platforms.
#Swift#iOSDev#macOSDev
ExploreLive feeds
About