Could the problem be in the approximation when using fractional font size ? Did you try using func size(withAttributes attrs: [NSAttributedString.Key : Any]? = nil) -> CGSize and adapt the size to fit window width ? Some more details here: https://stackoverflow.com/questions/1324379/how-to-calculate-the-width-of-a-text-string-of-a-specific-font-and-font-size

timeline is from app submission to Apple publishing in the app store. By experience, typically between 4 hours and 1 day. Delays are longer if there is an issue and app is initially rejected. However, as you can read on this forum, some developers experience long delays (usually because of a submission problem which may require call to support).

Confirm. But is is so easy to submit a new version with "small bug fixes". There are always.   we’d like to avoid a situation where a feature update gets delayed or rejected due to issues in the metadata. What's the risk ? As long as the new version is not approved, the old one remains available.

Welcome to the forum. You may try to contact support, but I fear the only option is to let the app die. This is logical. Imagine if someone which is not the app owner (through its account) could remove apps from the AppStore … If I remember correctly, when there is no update during 3 years, it is automatically removed from the appstore.

Tested with Xcode 16.4 both on iOS 26 simulator and iOS 18.4. Also tested a run on Mac. Works without problem. In addition to Clean Build Folder, you may reboot.

Unfortunately, that's not a question for the developers' forum. You'd better ask to support community: https://discussions.apple.com/welcome

Have a look here: https://www.appypievibe.ai/blog/working-with-binding-in-swiftui#:~:text=In%20SwiftUI%2C%20you%20can%20create,and%20also%20stores%20its%20value or here: https://stackoverflow.com/questions/59247183/swiftui-state-vs-binding Binding does not cause the View to update the body, which State does. So, it's normal it is nor updated. You can see that boundValue is not updated by adding onSubmit: TextField("Bound value", value: $boundValue, format: .number) .onSubmit { print("Textfield submitted", boundValue) }

You should probably recontact ProofPoint support. The forum is not intended for such support (including for 3rd party products), but for helping developers. So it's not the best place to get an answer.

passed in binding Yes, and that was my initial question: to what is it passed ? But I'll let more skilled SwiftUI experts reply.

A Binding is a value that has to be passed to someone. In other words, it has to be bound to something. It does not "exist" per se. See here, which is similar to the code I posted. https://developer.apple.com/documentation/swiftui/binding So, IMHO, that's not a bug, that's a SwiftUI feature.

May be I missed something of your intent. Why using a Binding here ? That means ContentView is called from another view with a Sate var ? Otherwise, it is a misuse of Binding. I changed to this, which works. struct ContentView: View { @State var boundValue: Double? @State private var stateValue: Double? = 55 var body: some View { CallTextField(boundValue: $boundValue) // TextField("Bound value", value: $boundValue, format: .number) Text("\(boundValue ?? .nan)") TextField("State value", value: $stateValue, format: .number) Text("\(stateValue ?? .nan)") } } struct CallTextField: View { @Binding var boundValue: Double? var body: some View { TextField("Bound value", value: $boundValue, format: .number) } }

Welcome to the forum.   bottom navigation tile when it cannot be localized Why can't it be localized ? Could you give more details as well as screenshot ?   Will the app be acceptable from a publishing point of view? Do you mean Appstore review point of view ? I do not see any reason here for rejection.

I've noticed a point when installing ß7. When I installed ß6 and was asked to download iOS, WatchOS… simulators. Which I did. I kept ß6 installed and downloaded ß7 I was not asked to download simulators they are available in ß7 Does it give a hint to a workaround ? Even though I noticed you had the problem with ß6. uninstall ß7 download and install ß6: are you asked to download simulators ? install ß7. In anycase you should contact support and file a bug report.

You could try to completely reload Xcode 26ß7 from here: https://xcodereleases.com When launching Xcode, you should be asked to download simulators. Hope that helps.

Could you show the code ? How many views in the scrollView ? More than 10 ? And try to localise the error: comment out all views in scroll view except the first does it crash ? if yes, analyse this view otherwise, uncomment the second subview and continue until you get a crash Note: if there are many views, you can speed up with dichotomy approach.