“Xcode”

Thank you for you quick response! 🙂X-code didn´t like the self declaration. Autocorrect wants me do do this:ref?.child(users).child(user).observeSingleEvent(of: .value, with: { (snapshot) in guard let userDict = snapshot.value as? [String: Any], self.address == (userDict[Address] as? String)!, self.name == (userDict[Name] as? String)! else { return } print(self.address + self.name) })The variables name and address isn´t returning anything with this.

Thanks Pany, that's a viable solution assuming you are not restricted to deploying and testing on iOS10+ devices, which XCode7 doen't not support.And did not upgrade to Sierra which in turn requires xCode 8. Unfortunately I am constrained by both of the above so that's not going to work for me.I am now trying to use the Swift 2.3 toolchain in XCode 8.2 and enabling Use Legacy Swift Code to see if I have more luck with it, but it complains about the Swift 2.3 value being overridden by the TOOLCHAIN build setting (...).Interestingly enough, it seems easier to use a variety of Swift toolchains on Linux than on MacOS (although I am sure that some fo you guys have managed a working toolchain with SimpleTunnel). It could be useful to set up a Slack channel with all interested devs working on the Network Extensions: I've found that a life safer when working on Swift server side (PerfectServer across intermediate Swift3 snapshots) as it allows for instantanous sharing of knowledge / common

For sure, Xcode may be very verbose and some warnings are hard to solve (even impossible). But you can silence the warnings and just keep errors. In the Issues navigator click on x at the bottom on the Filter line Could you show the real and more complete code, so that we can understand these hang pont (???) messages

Looks like you can... My Xcode 9.3 supports down to iOS 8.0 via the Deployment OS setting. You may need to code around any deprecations, etc. Idioms might help.And just a note that after all the chatter surrounding Apple's repeated admonition that as of April 2018 (May 1 is tomorrow...), 'all new apps and updates must support iOS 11', which would mean latest Xcode 9.3 (as of now), iTunes Connect, after nearly two years, remains unchanged, still saying this about that:Submit your builds using Xcode 6 or later, or Application Loader 3.0 or later.If you want to build w/base SDK iOS 9.x, you're free to use Xcode 7.x - which of course means you can't also support iOS 11 - but you seem to be good-to-go in that example, since you have no interest in iOS 11 support.Good luck.

Not in that example, no.The usual process in that case is to lower the '[ <target>General/Deployment Info ]Deployment Target' - just be aware your code may need updating as well.Otherwise, if you must stay at 8.x iOS, install an older Xcode, such as 6.2, (where a need to submit to the store using iOS 10.x would be set aside), but that may only present different issues, requiring you to learn outdated code, processes etc. - my advice is to modernize now, instead.