My guess for the first is that the compiler in the first performs type inference and analyses ["hello", "world"] as array of optional. let result = ["hello", "world"].contains(Optional("hello")) // ✅ Works fine But in the second, let stringArray = ["hello", "world"] let result = stringArray.contains(Optional("hello")) // ❌ Compile-time error you explicitly declare stringArray to be [String]. Then in second line, compiler balks at it.

10 years later… with Xcode 16.2, same error message. I do not call snapshotView.

Found it. My mistake. I had a test for iPad in the viewDidload. I inadvertently put the register in the iOS section ; so it did not apply for iPad !

Many thanks ffor the information.

You cannot beyond 1 hour after posting. If it is critical to get it deleted, ask forum administrator. You may try to just mark your own post as 'Duplicate', or 'other cause' (not spam, nor inappropriate, that could cause you problems later) ; usually, post is rapidly deleted.

@DuBu error messages are, IMHO, a real weakness of SwiftUI. Messages are at best not helpful, at worst misleading.

Thanks Scott. I filed a bug report: Mar 13, 2025 at 3:24 PM – FB16853197 I'll leave the thread open for a while, in case some compiler engineer notices it.

That's because dataTask has not completed when you return. Look here to see how to wait until it has completed: https://stackoverflow.com/questions/38952420/swift-wait-until-datataskwithrequest-has-finished-to-call-the-return Write the sendRequest function, func sendRequest (request: NSURLRequest,completion:(NSData?)->()){ NSURLSession.sharedSession().dataTaskWithRequest(request) { data, response, error in if error != nil { return completion(data) } else { return completion(nil) } }.resume() } And use it inside var quotes. The completion will return output

Wanted Feature : Get a warning when compiling if an IBOutlet is not connected. Pain point: It may happen to forget a connection and not see it (notably because in some cases, Xcode is mislead to show a connection that does not exist in this project). That's crash at runtime. Feasibility: When using storyboard, Xcode notes when an IBOutlet is connected or not to the storyboard object. So it must be easy to have it detected at compile/build phase.

Welcome to the forum. I hope your next posts will be more interesting and useful 😉

Welcome to the forum. You can access, but of course to a limited scope if you have no account. Why this question ?

I tested on a WhatsApp conversation and could get a screen capture. What page is this ? If that could help: https://www.reddit.com/r/ios/comments/14yyvzo/can_i_disable_screenshot_detection/?rdt=61137 Note: have you tested to take a photo of the screen with another iPhone ? Does it work ? If so, even if you prevent direct screen capture, there are simple workaround…

"Promillewert" Do you effectively reference to blood alcohol content ? If so, the problem is the app itself, as explained by reviewer. Just changing the wording by speaking of estimation will most likely not be enough. It remains a blood alcohol value. And this has to be provided by approved hardware (there are likely legal liability behind this).

The bug cannot be reproduced anymore (Xcode 16.2, Watch simulator Series 9 45mm 10.0 or Series 6 45 mm OS 10.4). It seems solved ; may be thanks to MacOS update to Sequoia 15.3.1 (24D70). I closed the bug report as well.

Thanks a lot. That's so simple, once you know.