Group Group Group Group Group Group Group Group Group

Your Second iOS and SwiftUI App | raywenderlich.com

<p>Use the knowledge you&#39;ve gained from creating a SwiftUI app, and learning the fundamentals of Swift, to create a more complex app: a task list!</p>


This is a companion discussion topic for the original entry at https://www.raywenderlich.com/5662524-your-second-ios-and-swiftui-app

The second app seems to be running but if I select a task from the list and the return to the list with the Back button, I get a long error message that includes UITableView was told to layout its visible cells and other contents without being in the view hierarchy. Doesn’t seem to hurt anything but the message sounds pretty bad.

(Course is great, BTW!)

??

1 Like

I got all kinds of fun error messages when putting this together—it was pretty much guaranteed that in every beta, old ones would disappear, but new new ones would come about! Here’s hoping for a stabler SwiftUI over the next year. :smiley_cat:

OK - ignoring that problem and on to the next.

FIrst, I have to say the course was terrific. It’s been decades since I wrote any serious code and, somehow, PL/1 skills don’t help much these days. Your course has me writing the productive app I wanted within days. Thanks!

So - made progress on my app and it seems to be working well on iPhone simulator. Decided to try it on an iPad simulator since that’s what I really want and when I run it on the iPad Air simulator, all my lists are empty. Couldn’t find anything obvious so I went back to the TaskList app from the course and when I run TaskList on an iPad Air simulator I get a blank white screen! TaskList runs fine an iPhone simulator.

I’ve tried it on both 11.1 and the 11.2 beta with same results

Help?

My experience:

  • Works on device in landscape.
  • Works in Simulator after two rotations back to landscape.

That’s not good enough! :smile_cat:
It’s clear that the iPhone took priority for SwiftUI development, but there are some workarounds here: https://stackoverflow.com/questions/57888032/swiftui-navigation-on-ipad-how-to-show-master-list

Hi,

I’ve done the course, it was really good, thanks for that. As my own little challenge I’ve tried to adopt dark mode in the app - I know iOS provides it already so I’ve decided to just change a few things like accent colour or tried to make the background colour a bit lighter than just black. And problems.

Can’t find anywhere online how to actually change the background colour of the app i switfUI even in light mode - any of the courses you’re offering on the webiste tackle dark mode, colours and using assets color sets?

Thanks

Currently, these screencasts are all we have; we don’t have any Dark Mode-focused content specifically for SwiftUI.

https://www.raywenderlich.com/3788563-dark-mode-the-basics
https://www.raywenderlich.com/3979883-dark-mode-deep-dive

What do you think would be a good umbrella topic for a future course in which Dark Mode is covered? Perhaps “Colored Assets in iOS”?

1 Like

I couldn’t help but notice that when editing a task, you have left out the ability to change the task priority. You are forever stuck in a single priority. I tried, but failed to implement that feature. Had all sorts of issues with passing a bound priorityTask.
Would love to see an additional section on adding this.

1 Like

I’ve actually been thinking about what createch is talking about but instead of changing the priority on a task I was wondering if its possible in SwiftUI to move between priorities (eg dragging a task from high priority to low). I know it’s possible with UIKit but have no idea how to implement it with SwiftUI, I’d really appreciate any help.

As far as anyone seems to know, it’s not possible.

I mention that at the end of the episode on Section Views.

As for changing task priority, I left it out because SwiftUI didn’t offer a beginner-friendly solution. I expect this to change next year.

I was wondering when the IOS learning path will be swiftUI instead of a combination of UIkit and SwiftUI? I feel like its really unorganized at the moment.

As Ray goes over here, the learning path is going to cover both frameworks until we feel UIKit isn’t relevant anymore.

The transition to the hybrid learning path is not complete; we’re working on updates for the courses that come after this one. In general, when we can cover a topic with SwiftUI, then we’ll be using SwiftUI exclusively for new and updated content, and primarily only updating the projects for the older UIKit content on similar topics.