Sending and receiving Codable data with URLSession and SwiftUI – Cupcake Corner SwiftUI Tutorial 1/9

preview_player
Показать описание

Other parts in Project 10:

1. Sending and receiving Codable data with URLSession and SwiftUI: This video

Рекомендации по теме
Комментарии
Автор

Thanks for updating the 100 Days of SwiftUI course! This content is absolutely amazing

samsHandle
Автор

Hello Paul and thank you very much for these videos. I am a novice programmer wannabe and am trying to learn Swift through following your videos. I completed the code for the first tutorial but I am getting nothing back from the API call, just a blank screen. I get the following message: "Communication with Apple failed. Your team has no devices from which to generate a provisioning profile. ..." I am working on a current MacOS machine and the app large is iPhone 15 Pro. Do I need to do something with the App Sandbox under "Capabilities"? When I look under "Capabilities" I do not see the option to add App Sandbox

AltonWilson-qm
Автор

Paul Hudson! If you're reading this ....Can you PLEASE organize your videos into a mini 'playlist' because the order on which they are uploaded on YouTube are not in order. Would be greatly appreciated as always thank you for your videos!

guarino
Автор

Thanks for this amazing course! I manage to fetch data from my own API but I run into a strange behaviour with JSONDecoder instead of Response.self I have to use [Result].self with the same structure of the course and the data retuning by my api is of type [ { "firstName": "my name", "lastName": "name" } ] so is not different from iTunes data. Can you please explain why ?

BenoitSchwartz
Автор

Hi Paul, I got blank page with these codes. No error, no failed build, just blank page.

slowmodon
Автор

can some kind soul tell me why this works perfect on iOS - but not on macOS (no error, just a blank window). Thank You so much!

msch
Автор

Dear Paul, you are influencing positively so many people with your extraordinary courses, but why on earth do you suggest to print meaningless literal strings rather than the real error in catch blocks and even ignore the Decoding error? I’m a frequent user of Stackoverflow and there are so many questions about your Bundle extension which throws fatal errors instead of handling or at least printing the often comprehensive and enlightning thrown errors to help the users to fix their mistakes. No offense, I’m a big fan of your work. Regards Stefan

Vadian-iy