Could not successfully update network info during initialization

Question

I get the above mentioned issue all the time when I first launch the app in the day. When I first launch the app, I make server calls to get some data and then play animation video. Server calls is in a separate thread than main UI Thread. Is it something to do with Network Reachability or the animation video ? I think the first part is the major issue but cannot recreate this all the time.

Has anyone experienced the issue ?

Below is the code when I first launch the app.

override func viewDidLoad() {
        super.viewDidLoad();


        self.navigationController?.navigationBarHidden = true;
        self.view.backgroundColor = UIColor.whiteColor();
           dispatch_async(dispatch_get_global_queue(DISPATCH_QUEUE_PRIORITY_DEFAULT, 0)) { () -> Void in
            Items.setup(); //AFNetworking call
        };

        animationViewController.delegate = self;
        animationViewController.view.autoresizesSubviews = true;
        animationViewController.view.autoresizingMask = [.FlexibleLeftMargin, .FlexibleRightMargin];
        animationViewController.view.center = CGPointMake(self.view.bounds.size.width / 2, self.view.bounds.size.height / 2);

        self.view.addSubview(animationViewController.view);    

    }

Possible duplicate of [Why can't this iOS app access the network?](http://stackoverflow.com/questions/16975525/why-cant-this-ios-app-access-the-network) — JAL, Dec 18 '15 at 15:50
but there are no answers on it....And I am seeing the issue on Devices.. — lifemoveson, Dec 18 '15 at 15:51
You're not giving us any details of what you do, when you do it, how you do it. — jcaron, Dec 18 '15 at 15:54
It is working and I can compile it too...if you want Ill edit it.... — lifemoveson, Dec 18 '15 at 16:33
It is a method call to setup the network calls.I have changed the call so that it doesnt look like an array. — lifemoveson, Dec 18 '15 at 17:08

score 3 · Answer 1 · edited Jan 24 '19 at 15:23

3

I have resolved this issue in Xcode 9.1 with below steps.

1.Select Simulator

2.Select Debug from top menu items.

3.Select Location from Debug menu list.

4.Select Apple location.

edited Jan 24 '19 at 15:23

Kerem Baydoğan

10,475
1
43
50

answered Dec 12 '17 at 06:29

Srithar Rajendran

320
3
14

score 1 · Answer 2 · answered Jun 06 '18 at 17:57

1

Check if you have an exception breakpoint to capture "All Exceptions" in breakpoint navigator. This fixed it for me.

answered Jun 06 '18 at 17:57

1337holiday

1,924
1
24
42

score 0 · Answer 3 · edited Oct 30 '17 at 22:50

0

I had similar problem. Turns out in the App/Capabilities, I have Wireless Accessory Configuration with some red warnings. Click the button automatically solved the problem.

Not sure if it would work for you. I am using Xcode 8.

edited Oct 30 '17 at 22:50

shim

9,289
12
69
108

answered Oct 17 '16 at 18:14

Q Liu

737
1
5
7

score 0 · Answer 4 · answered Oct 19 '17 at 13:50

0

Was experiencing this too, fixed it by giving the simulator a default location. It may be a code smell so watch how you handle the new location permissions in iOS11.

answered Oct 19 '17 at 13:50

jusynth

183
7

score -1 · Answer 5 · answered Sep 24 '17 at 16:54

Issue: same with Xcode 9.0 iOS11. Resolution: new iOS requires you to manually turn on privacy for new deployment apps. Upgrades of the app is not needed. Following these steps: (1) iPhone "Settings" icon: click (2) "Privacy": click (3) "Location Services": click (4) [Your app]: click on your app (5) "While Using the App": click

score -1 · Answer 6 · answered Apr 20 '18 at 08:26

-1

You might have overrided loadView() without calling super method.

Change

override func loadView() {

}

To

override func loadView() {
  super.loadView()
}

answered Apr 20 '18 at 08:26

Saranjith

11,242
5
69
122

3

the view controller lifecycle has nothing to do with this issue. besides, [the documentation for that method](https://developer.apple.com/documentation/uikit/uiviewcontroller/1621454-loadview) clearly states that your custom implementation should not call `super`. – Eric Sep 10 '18 at 11:36

Could not successfully update network info during initialization

6 Answers6

Linked