Thanks for feedback. Lesson here is that in such a case, direct contact by phone is far better than mail.

Are you based outside US ? In some countries, verification process takes much longer.

@ahlabib is it a .strings file ? Or is it a Swift file with let declarations ? Could you show a small part of the file ?

@mtoag please refrain from using the forum for your company promotion. It is simply forbidden here.

What is your question ? If it is just promotion, that's not allowed on the forum. So please explain what you are looking.

Thanks for feedback. Effectively, the message is not very helpful. In addition, points.y should be detected as an error… Don't forget to close the thread.

Could you tell what your assignment exactly requires ? May be not to save all data to UserDefaults, but just some meta data ?

I'm just guessing here, sorry for that. Doc (SFSpeechRecognitionRequest) states that you could analyze partial request "For example, use the shouldReportPartialResultsproperty to specify whether you want partial results or only the final result of speech recognition." I interpret that, if you don't ask for partial request, recognitionTask will wait for a full buffer before calling its closure. But that's just a guess. I read this. Interesting , but not the answer to the question       https://stackoverflow.com/questions/51888726/speechrecognizer-not-returning-answer.

have a good end of year too. If you are interested in Swift inner details, there is a good site to visit: https://www.swift.org

Si vous voulez, donnez une adresse mail de contact. Ce sera plus pratique.

You should ask to Apple support.

Where did you define columns ? And this code is different from original post (no Button { } here). So what is the complete code to test ?

Yes they have been cleared. Thanks. It would be great to have this spam issue solved (notably those spam which always have the same pattern). Could there be a learning process to recognise such spams (training based on the moderator decision to remove) ?

There is a detailed explanation of it here: https://stackoverflow.com/questions/48658574/jsonencoders-dateencodingstrategy-not-working

I never noticed using 60 GB more at each update. But maybe, If I add a new version along existing ones.