Posts

Post marked as solved
1 Replies
0 Views
The rule you are breaking is that capitalization matters when you spell a name. You're saying xFile = ... So the Swift compiler looks for the term xFile declared as a variable name in scope, to which something can be assigned. But the word xFile doesn't appear as a variable name in scope — just as the compiler is telling you. What does appear as a variable name in scope is xfile, which as far as Swift is concerned is a totally different name.
Post not yet marked as solved
6 Replies
0 Views
Bump. I repeat the question. Xcode 13 is final. I need the Vary For Traits feature. Some of my apps use it. Where is it?
Post marked as solved
6 Replies
0 Views
The way to see all environment variable values is to add a run script to your build phases.
Post not yet marked as solved
2 Replies
0 Views
I agree. The idea of two completely different flows emanating from primary + secondary on the one hand and compact on the other, where all three view controllers just stick around during collapse and expand, is so simple and elegant. It took me only a very short time to make a working example that works on iPad toggling between splitscreen and fullscreen, and on iPhone 8 Plus rotating between portrait and landscape. Gone is all the kerfuffle with the obscure delegate methods and the button management; everything just works.
Post not yet marked as solved
4 Replies
0 Views
What I found is that when you manipulate the view controllers during the transition from compact to regular, you need to put a short delay on that manipulation so that the runloop has a chance to complete first.
Post not yet marked as solved
3 Replies
0 Views
The limitation referred to in the other answer is now lifted. Swift Packages can now include resources and frameworks.
Post not yet marked as solved
4 Replies
0 Views
"Go to the Options tab under Run Action and choose Use Terminal for Console" I don't see it and none of my co-workers can see it. We've been looking for it really hard since this feature was announced (Xcode 11.4) but none of as can find it. Is it really there?
Post not yet marked as solved
18 Replies
0 Views
May we presume you filed a bug?
Post not yet marked as solved
10 Replies
0 Views
Same issue remains in simulator in Xcode 11.3.1.
Post not yet marked as solved
12 Replies
0 Views
It's a straightforward cast:func controller(_ controller: NSFetchedResultsController, didChangeContentWith snapshot: NSDiffableDataSourceSnapshotReference) { let snapshot = snapshot as NSDiffableDataSourceSnapshot<string,nsmanagedobjectid> self.ds.apply(snapshot, animatingDifferences: false) }I'm assuming here that your diffable data source is typed with generic resolutions String, NSManagedObjectID. In your cell population function you go back to the fetched results controller, fetch out the actual object by index path, and populate the cell from its properties.
Post not yet marked as solved
12 Replies
0 Views
Still doesn't solve the problem with sectionIndexTitles. The index now appears down the right side of the table but clicking on it doesn't actually do anything.
Post not yet marked as solved
12 Replies
0 Views
Same problem with sectionIndexTitles. It doesn't implement it and you can't get it to work by subclassing or anything like that. So I can't adopt UITableViewDiffableDataSource.
Post not yet marked as solved
5 Replies
0 Views
If your app supports multiple windows, automatic state restoration based on the storyboard has no clear place to start. But I don't see what stops you from using view controller based state restoration on a per-window basis. The scene session's `persistentIdentifier` identifies the hierarchy, as the WWDC videos explain. Or am I wrong about that?