When builds fail — patience, parallel terminals, cost control

Transcript preview

Okay, so I'll go over here, we have that done and I have asked it for the publication. No, this is the next, this is the flutter, right? So we were going to run it on the phone and some issues are happening but the good part is guys, it's able to handle a lot of it. As you might have realized, so far nothing has been like we have to tell it for the issues. To give you a context of how we used to code, we used to find one issue, we used to search for that issue for a very long time. It used to take for us to actually figure out the solution to that and then we will try that and then it might not work, we will try another solution and so on and so forth. The reason I'm telling you all of this is because I'm realizing that you might be thinking since Karthik is taking time, it should have been done so far. There are different ways, right? There are different issues which happens with the different code which has been written. We literally made an app. So you see it did that part where it launched it on Xcode and it has already done the, this is the name of the phone, and 25% completed. Without me having to tell it all these things, it's going to do it and it's going to launch that. So we are very close to completion, I'm going to just quickly unlock the phone and you can see it's launching. I don't know what happened, it's just taking quite a long time. Okay, so sometimes if that is going to pause the error, just click on this play and it's going to do the build and it's going to do the launch. Okay, some error came up guys, that's why it's taking some time.…