Guideline 3.2.1 (vi) already gives a lot of information. But you have probably noted that it is likely Reviewer will ask you additional information: Additional information shall be provided to App Review upon request. If I understand you'll be an intermediary for other charities. Hence, an absolute requirement is that you get a proof that they have gone through the nonprofit approval process, as explained here : https://developer.apple.com/apple-pay/nonprofits/ Nonprofit platforms that connect donors to other nonprofits must ensure that every nonprofit listed in the app has also gone through the nonprofit approval process

You have breakpoints at lines 13 and 16. Is it on purpose ? Remove them and see what happens.

@endecotp you're right, this bot is nonsense. I filed a bug report: Dec 4, 2024 at 10:48 AM – FB16038067

IMHO publishing articles is not the purpose of the forum which is, as you noticed, to ask technical questions about app development. May be the forum misses a section for general technical discussions. I suggest you file a FB to ask for this.

Welcome to the forum. You're new here, and it shows. The forum is not the place to post such complaints. It is to help developers in developing their apps. Threatening of legal action is just useless here and would not help. So, you'd better either: contact Apple support contact Support Community write to the company Customer support Service file a bug report if the product (which ?) does not work as described.

It is always hazardous to try to guess the full rational of rejection. So the best is to read back the guideline: Your app should include features, content, and UI that elevate it beyond a repackaged website. If your app is not particularly useful, unique, or “app-like,” it doesn’t belong on the App Store. If your App doesn’t provide some sort of lasting entertainment value or adequate utility, it may not be accepted. You only can say if it is really “app-like” and if it does "provide some sort of lasting entertainment value or adequate utility" If I were to guess, I would suspect the second point. So you should try to bring some fun in your app. So, just an idea to illustrate. If the books are novels, you could list the names of main characters. And create a quizz like : in which book does Sherlock appear ? Hope that will help.

If you have any technical question, even beginner's question, you can ask on the forum. It is done for that. And you can access a lot of free Apple tutorials to start learning. Good continuation.

AFAIK, .mb is the correct unit for MegaBytes. Did you try with .all instead, just to see what you get ? And file a bug report.

Welcome to the forum. You have an extra space before ! modelData.landmarks.firstIndex(where: { $0.id == landmark.id}) ! Correct code is modelData.landmarks.firstIndex(where: { $0.id == landmark.id})! As you know, ! is the unwrapping operator, it is postfix and must be immediately after the optional. The same for ? optional operator For instance: var myVar : Int? let unwrappedVar = myVar!

@endecotp Good point. Effectively, Unicode 2007 figure space appears to be double char width.

@jlilest Thanks for the answer. Yes, I did, but AttributedStrings is really over complex for such a simple thing. So the simple solution is likely: let largeWidthSpace = " " // Double space And use it for padding.

You can filter what is typed, with TextField delegate. Don't forget to declare the ViewController as the delegate for the TextFields. Can be improved if you want to allow to move insertion cursor in an existing text.. let gcTabAscii = 9 let gcLineFeedAscii = 10 let gcReturnAscii = 13 func textField(_ textField: UITextField, shouldChangeCharactersIn range: NSRange, replacementString string: String) -> Bool { guard let charCode = string.first?.asciiValue else { if string == "" { // Accept backspace return true } return false } if charCode == gcLineFeedAscii || charCode == gcReturnAscii { // It is lineFeed even when typing return return true } if charCode == gcTabAscii { // Tab textField.text = textField.text! return false // You should fine tune here to allow for - sign or dot sign at start } let newString = textField.text! + string if Int(newString) != nil { // So we typed something in newString and it is a valid number ; if you do not expect an Int but any number, test for Float(newString) return true } else { return false // You could allow for - or starting dot with // return newString == "-" || newString == "." } }

Use String with format: let percentString = String(format: "%4.2f", valueToPrint) + " %"

Welcome to the forum. You don't give enough information. Xcode version is 16.1. Is it a beta or a release ? When does it occur ? When compiling your app ? If so, do you get error message ? At launch ? : if so you should reinstall Xcode.

AFAIU, your app is not trading cryptocurrencies but advise about trading. So, in a sense, it facilitates transactions. That could be the reason for the constraints you get according to 3.1.5 (iii) Exchanges: Apps may facilitate transactions Note: this is a bit similar to medical app: even if they do not sell medicine or practice any medicine, if they advise on health they must meet some strict requirements. Did you try to contact support ?