Start a new topic

crash if app comes back from background to foreground

crash if app comes back from background to foreground


iOS 6.0.1, iPhone 4, Wikitude 1.1.1, Xcode 4.5.2

If i stop the app with the home button an start it again i have no problems as long i do not start the wikitude part in the app.

If i start the wikitude part in my app and stop it (leave the view) again and press the home button and start the app again i get a crash as soon the app comes back to foreground. i get this error message:

2013-02-24 16:51:59.322 Bildungsapp -: unrecognized selector sent to instance 0x1e98ad10
2013-02-24 16:51:59.325 Bildungsapp *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-: unrecognized selector sent to instance 0x1e98ad10'
*** First throw call stack:
(0x33bcd2a3 0x34a8b97f 0x33bd0e07 0x33bcf531 0x33b26f68 0x36bad119 0x33ba26b1 0x33ba1d85 0x33ba0fdd 0x33b13ebd 0x33b729bb 0x36bacef7 0x36206311 0x362061d8)
libc++abi.dylib: terminate called throwing an exception


i do following if i leave the architectViewController:

- (void)goBack {
    architectView.delegate = nil;

If i leave the viewController and launch it again without terminating the app (put in background), it does not crash.

If i really terminate the app (double press home and so on...) i have no problem at all.

What can i do? Can i do something if app goes to background or if app comes back to foreground?

I need some help. I'm a paying user (perhaps this makes a difference).

I tried a lot and tried to get some help before.

You can download the app in the app store for a demo, its free (bilden und forschen wädenswil).

ps: i do not use wikitude 1.2 because i have some other problems with 1.2 (see next post). please tell me if this is a known problem with 1.1 and if it would be better with 1.2


This seems to be related to my issue too:


 I switched on zombies.

Now i can see the cause of the crash:

2013-02-27 10:31:56.472 Bildungsapp *** -: message sent to deallocated instance 0x201f9df0

I did read that this is a bug in the iOS.

Is there any way to stop the MotionManager from the old ARView if apps comes to foreground?

I think that would help.




Looks that this post is related to the same problem:

If anyone has a solution please let me know you would safe my day or even my week.



Login or Signup to post a comment