Para as capturas de ecrã, o melhor é gerá-las com o simulador. Assim, tem a certeza de que está no formato correto. Então, tem uma empresa e um número DUNS? Qual é o nome comercial? É o nome comercial da empresa? Onde aparece nos metadados? Provavelmente seria mais simples ter o mesmo nome para ambos. For the screenshots, the best is to generate them with the simulator. You are thus sure it is the correct format. So you have a company and a DUNS number ? What is the trade name ? Is it the commercial name of the company ? Where does it appear in Metadata ? It would probably be simpler to have the same name for both.

On which version of Xcode do you build ? Have you the list of all libraries you use ? Finally, have you accepted the eventual Xcode message (appear in left panel) to update to new settings ? Old thread, but you may find interesting hints to look at: https://stackoverflow.com/questions/48501857/non-public-api-usage-the-app-contains-one-or-more-corrupted-binaries

You're not the first to ask such question. Answer here may help you: https://developer.apple.com/forums/thread/797977?answerId=855247022#855247022 With all the things you want to learn, that may take you more than 6 months full time to learn and master. So you should focus first on learning basics, like using Xcode (of course), Swift language and the basics of SwiftUI and UIKit. Good material in https://developer.apple.com/pathways/.

Bienvenido al foro. Si necesita ayuda, explique el contexto. ¿De dónde proceden las capturas de pantalla? ¿Es al realizar una búsqueda en Finder? ¿En Xcode? ¿En otro lugar? ¿Es en su aplicación? Si es así, muestre el código.

What description did you give ? Is it clear enough why the app needs microphone, not a generic statement ?

As explained in doc, Changing a component’s value often will require higher or coupled components to change as well… The exact behavior of this method is implementation-defined: Changing a component’s value often will require higher or coupled components to change as well. For example, setting the Weekday to Thursday usually will require the Day component to change its value, and possibly the Month and Year as well. If no such time exists, the next available time is returned (which could, for example, be in a different day, week, month, … than the nominal target date). Setting a component to something which would be inconsistent forces other components to change; for example, setting the Weekday to Thursday probably shifts the Day and possibly Month and Year. The exact behavior of this method is implementation-defined. For example, if changing the weekday to Thursday, does that move forward to the next, backward to the previous, or to the nearest Thursday? The algorithm will try to produce a result which is in the next-larger component to the one given (there’s a table of this mapping at the top of this document). So for the “set to Thursday” example, find the Thursday in the Week in which the given date resides (which could be a forwards or backwards move, and not necessarily the nearest Thursday). For more control over the exact behavior, use nextDate(after:matching:matchingPolicy:behavior:direction:). Note that if you set the weekday to the same value (3), results are kept the same meDate = Calendar.current.date(bySetting: .weekday, value: 3, of: meDate)! Interesting discussion here: https://forums.swift.org/t/date-from-date-components-is-incorrect-after-changing-month/54192/5

Welcome to the forum. Do you hope anyone here to know ??? You'd better contact Apple support.

could any of the following override this setting? My understanding is: Using certain third-party SDKs that might have their own encryption. -> YES The presence of specific Apple frameworks like CryptoKit or CommonCrypto, even if not used for non-exempt purposes. -> YES Standard HTTPS calls made through WKWebView. -> NO A temporary bug or caching issue in App Store Connect. -> Always possible, but unlikely.

Welcome to the forum. It likely just means they want to have your explicit commitment (not only automatic from meta data) that the app does not use encryption. I guess that if you set ITSAppUsesNonExemptEncryption to YES and declare you don't use, there would be an alert or a rejection. I've not identified any issue with it otherwise.

On which device without notch (or simulator) do you test for iOS 26 ? Here is how I detect the notch (I test the top): extension UIDevice { var hasNotch: Bool { let scenes = UIApplication.shared.connectedScenes let windowScene = scenes.first as? UIWindowScene guard let window = windowScene?.windows.first else { return false } return window.safeAreaInsets.top > 20 } }

Just file a bug report for the new symbols you would like to see in SF 8.

Take care not to try and tweak the evaluation. That could result in account termination. What you could do: add a nice feature to the app, attractive to users ask them what they think of this new feature

Depends on how large the web app is. If this is the only development you plan, you could get a try, even though you will face hurdles from time to time. More generally, I have found by experience: 16 GB are really necessary if you have mid or large size projects 1 TB of storage is really a minimum Processing power is not the issue screen size is important to work efficiently with Xcode. 13" is probably too small, except to start learning, but you can later attach an external monitor. And finally, MacBookAir 2020 will not support new OS versions (and hence new Xcode) for a long time.

The reason here: self.xaxis.text is an optional (may be nil). So you have to address it with the nil coalescing operator var xoutput = self.xaxis.text ?? "0" Which is equivalent to: var xoutput : String if self.xaxis.text != nil { xoutput = self.xaxis.text! } else { xoutput = "0" } or a bit more compact: var xoutput = "0" if self.xaxis.text != nil { xoutput = self.xaxis.text! } For more on this: https://www.hackingwithswift.com/example-code/language/what-is-the-nil-coalescing-operator Note that in the example print("Hello, \(name ?? "Anonymous")!") the final ! is not for unwrapping, it is just an exclamation point to be printed at the end of text. If you were sure it cannot be nil, you could also unwrap directly, but that is really risky. var xoutput = self.xaxis.text! Once you are sure that string is a string, not an optional, you can pass it to Double() to convert String to Double. But here again, if the content is not a number (eg: "abc", Double will return nil. And in all cases it returns an optional. So here again, use the nil coalescing operator to unwrap (transform optional to a real value) safely.

I checked and got the same behaviour, in 18.4 and 26.0. It may well be an intended behaviour. In fact, with the 18.4 behaviour, once you reach 0.7 and then step up, you get 1.2 and not the original value of 1.0. Which may cause problem as it may be hard to find back this 1.0 value. So effectively, we have now to implement it in code. Problem is that down stepper is disabled when you hit 1.0. 2 possible workarounds: set stepper behaviour as wrap (not ideal) set minimum to 0.5 and manually adjust in IBAction to limit to 0.7: if value < 0.7, set to 0.7 if value is between 1.1 and 1.3 (0.7 + 0.5 when you step up back from 0.7), set to 1.0 Not ideal, but I've not found a better way.