This is my favorite course so far! I hope you plan to show us the best ways to put shadows on the Today cards. Plus, when the card is clicked, it should shrink a little and then spring open when the click ends.

When I clicked the card, I found an error message in the console as following: AppStoreJSONApis[5492:181955] Warning once only: Detected a case where constraints ambiguously suggest a size of zero for a collection view cell's content view. We're considering the collapse unintentional and using standard size instead. Do you have any idea about this? Thanks Brian! I learned a lot from this course!

When you select the card and open the detail vc, then scroll up and click to dismiss, the close button lingers when you return to the card. Also, your rig must be much faster than mine. After returning from the detail vc, the card is unclickable for a noticeable amount of time. The delay has to do with dismissing the detail vc after you return, I guess!

I was amazed that you finally used a child VC. Good on ya! But, I had read that 3 calls are necessary for allocation and deallocation: https://www.swiftbysundell.com/posts/using-child-view-controllers-as-plugins-in-swift) extension UIViewController { func add(_ child: UIViewController) { addChild(child) view.addSubview(child.view) child.didMove(toParent: self) } func remove() { // Just to be safe, we check that this view controller // is actually added to aparent before removing it. guard parent != nil else { return } willMove(toParent: nil) view.removeFromSuperview() removeFromParent() } }

Hi Brian, what do you think the difficulty level of this animation? 0 - 10

i feel like a chimp at the moment, but im going to keep on pushing through

Dude, I bought this course just to watch how you did the Today animations. I've managed to implement the Transitioning delegate by myself, and although it's cool that you can swipe back to dismiss interactively, IT'S NOT WORTH THE EFFORT! Your approach is way way more simpler and it freaking works. Thanks. This alone was worth 60$

I think I understood most out of it except the super.tableView(tableView, heightForRowAt: indexPath) part. Based on my understanding, tableview by default has really small size; therefore, we have to override this function to match with the height which we want. So I guess what I want to say is that how come by calling super.tableView(tableView, heightForRowAt: indexPath), tableview manage to autofit the height of the cell... Any hint or explanation will be very appreciated.

Hi Brian, thank you, this is such a great course! I have a question, when using transitioningdelegate, i know it uses a container and its important to remove the previous screen from the container after presenting the new screen. With this way of animating, do we need to do something like that? What will happen if the FullScreenController presents another view modally and I want to unwind to the very first screen? Thank you.

Hi Brian, I followed your tutorial but one more thing I had to do is to deactivate all the constraints after the dismiss animation completion. Otherwise, I had a "Can't satisfied multiple constraints" warning and the dismiss animation was buggy after the modal was opened once (only the first dismiss was working well). It's a mystery for me because I had the exact same code and I didn't forget the 2 view.layoutIfNeeded(). Anyway, it works well now though :)

The part with self.appFullscreenController.tableView.contentOffset = .zero doesn't work in iOS 13 anymore.

Hi Brian! The transition of these two screens was one of the main reasons I purchased this course (which I'm enjoying a lot so far). Unfortunately it remains really glitchy in iOS 13. Were you able to find a solution to this problem?

so was having some issues with closing , if your on xcode 11 and iOS 13, this fixed it or me: in the close animation , put the scrollToRow code after. don't use the contentOffSet. simulator may still show an issue, but test on your phone, should be perfect self.view.layoutIfNeeded() //self.appFullScreenController.tableView.tableView.contentOffset = .zero self.appFullScreenController.tableView.tableView.scrollToRow(at: [0,0], at: .top, animated: true)

Dear Brian, One symptom, when TodayCell scroll to top < saftAreaInset.top or the bottom > view.frame.height The closing animation will include the AppFullscreenController top safe area (notch background) There is no problem will TodayCell location at center of list view Seems the animation will not shrink safeArea background color more high priority I use SwiftUI to create initial project. It different with "Download Project" Are there any suggestion for the issue? Thanks a lot

Having an issue where cells that encroach into the top and bottom safeAreaLayoutGuides do not animate back correctly. It appears as though the top safe area inset for the expanded view is being preserved. Any chance you could take a look? https://github.com/seventhaxis/lbta-appstore

the code self.appFullscreenController.tableView.contentOffset = .zero in handleRemoveRedView function no longer working with iOS 14, Could you please find another solution?