Hi guys, I got one issue about sending data with interval 1000 seconds to the server, while the app has been killed by user. I found the relevant document about app in background mode. https://developer.apple.com/library/ios/documentation/iPhone/Conceptual/iPhoneOSProgrammingGuide/BackgroundExecution/BackgroundExecution.html but I checked the document, it seems there is no way to use NSTimer inside the block of beginBackgroundTaskWithName... function. NSTimer.scheduledTimerWithTimeInterval(10, target: self, selector: #selector(AppDelegate.handleTimer), userInfo: nil, repeats: true) Question: How to consistently send data to server with interval time while app has been terminated? Thank you, e

Dear developers, I suddenly have a massive confusion about the undergoing big programming revolution inside apple developers. I understand swift has been officially announced since 2014. As a normal iOS mobile developer, I respect and follow all the new policy from apple. But I just had such thoughts and doubts: What makes Objective C so weak comparing to Swift? Is that because all the banks use Java as programming language? Is objective cannot easily access windows system? Is Swift wrapped with Objective C or Swift is totally a brand new programming language? How many new hardware interface have been available to access by accepting Swift? Is Objective C going to disappear within next 5 years? How many years will it take apple to stable its own programming language? NOTE: I met a lot of iOS mobile developers change to learn JAVA, Become an android developer. eg: https://developer.apple.com/library/ios/samplecode/Reachability/Introduction/Intro.html#//apple_ref/doc/uid/DTS40007324-Intro-DontLinkElementID_2 The sample code from apple documents was still written in Objective C @2016, Are we going to use Swift or Objective C? and some of the APIs documents are not completed, class initializer cannot be accessed such as https://developer.apple.com/library/tvos/documentation/SystemConfiguration/Reference/SCNetworkReachabilityRef/index.html#//apple_ref/doc/uid/TP40007260-CH101-SW4but was writted beautifully in apple documents.

https://devforums.apple.com/message/1130381#1130381I had the same problem as description on the above link. I applied the solution about removing armv7 from valid architecture on both iPhone and Watch extension app, Then did the following steps:Build & run your iOS app in the simulator.Wait for it to finish launching, then hit the stop button in Xcode.Switch your active target to your WatchKit app, build, and run it.When the Watch app has finished launching, tap your iOS app's icon in the main simulator window.In Xcode's menu bar select Debug > Attach to Process.Select your iOS app from the list. Chances are you'll find it under Likely Targets.But xcode still display complain message "waiting for attach", I would be very appreciate it if someone could help.Thank you ( :