24 hours is not a big deal. As long as it is not more than 3 days, you should not worry.

You should either declare from and to in: an init() - just declare type in the general declaration and set value in init in .onAppear as a modifier of the VStack But there are many errors in the code that you have to correct first: you call distance in the distance func. That will cause infinite loop return from.distance(from: to) You need to set values of parameters, let distanceFrom = from.distance(from: to) such as let distanceFrom = from.distance(from: from, to: to) from is a CLLocationCoordinate2D But distance is defined for CLLocation only…

You'd better show the complete code. Is it SwiftUI ? UIKit ? The fact that image is of Niagara Falls or a corn field in Kansas does not matter and is useless information.

Really messy here. This post was rejected several times as well, after a Gateway timeout in some cases. You will need Swift in anycase, either you use UIKit or SwiftUI. But you will probably learn the two at the same time. Go to pathway : https : / / developer.apple.com/pathways/?cid=ht-pathways

You will need Swift in anycase, either you use UIKit or SwiftUI. But you will probably learn the two at the same time. Go to pathway : https : / / developer.apple.com/pathways/?cid=ht-pathways

Just filed a bug report: Apr 7, 2025 at 2:09 PM – FB17148876

A 20 lines dense text, mixing facts and just feelings and recriminations, is just unreadable. Please state clearly what is the question you have that other developers may help you resolve.

The problem could come from the baseline offset: https://stackoverflow.com/questions/69760382/how-do-i-fix-clipped-ascenders-and-descenders-in-a-custom-font See more here: https://medium.com/mobimeo-technology/what-if-your-designers-want-a-baseline-grid-on-ios-d5234c7b52c0 Here on how to change offset (through attributes): https://developer.apple.com/forums/thread/124799 Why did it change in iOS 18.4 is another question…

Removed

So, I try now to answer my own post (this one)… It works. But not when trying to reply to another thread, such as: https://developer.apple.com/forums/thread/779777 I tried from an iPhone, doesn't work either. It seems that the (new) anti spam is at work. • If I post this answer, with the word f r e e (edited from f--e), reply not accepted. Go here for (f r e e) material to get started: https://developer.apple.com/pathways/?cid=ht-pathways • But this reply is accepted: Go here for material to get started: https://developer.apple.com/pathways/?cid=ht-pathways Anti spam is now way too sensitive.

Go here for (gratis) material to get started: https://developer.apple.com/pathways/?cid=ht-pathways

You once had problem with your Suzuki, now with your Skoda… It would probably be time to stop installing betas on your main phone… In any case, the forum is not the place to expose usage issues. Go to the support forum or file a bug report instead.

What happens if you set the frame height ? Text("\(count.toMyanmarDigits())") .frame(height: 50) // or even 60 .font(.system(size: 40, weight: .bold, design: .rounded)) .monospaced() .foregroundStyle(.accent)

Very good news Quinn. And thanks for taking the time to reply.

That's an intrinsic limite of GPS localisation (not iPhone): vertical precision is less than horizontal. You have probably noticed in your car. Sometimes, at the same point on a road, it says 295m, another day 305. 30 ft difference. See details here and may be some hints to a workaround: https://stackoverflow.com/questions/8282169/cllocation-elevation-accuracy Ot to get info on vertical accuracy: https://developer.apple.com/documentation/corelocation/cllocation/verticalaccuracy