Log in or register to post comments

Vuforia::init() EXC_BAD_ACCESS

June 12, 2020 - 12:25pm #1

Hi Guys,

I am currently migrating an app from Vuforia v7 to the latest available version (9.1.7).

After a few optimizations, the app works flawlessly, the object is recognized correctly at startup, POI are augmented as desired, the world is fine.

When selecting a POI, additional information is displayed and Vuforia is paused and deinitilized. When the AR-View is visible again, Vuforia is initialized from scratch again.

Everything works as expected up to the point where you resume the app after it was put in the background when I get EXC_BAD_ACCESS(code 1) and a useless stack trace in the following line:

NSInteger initSuccess = 0;

        do {

            initSuccess = Vuforia::init(); // Error occurs here

        } while (0 <= initSuccess && 100 > initSuccess);

While debugging with Zombie, I found "message sent to deallocated instance". What object is deallocated that should not be? Why does the exact same Workflow work if you resume from a POI but not from the background? What am I missing here?

The problem occurs on different devices with iOS 12 and 13.

Although I don't have much experience with Vuforia, I've worked with other AR frameworks in the past and this is the first time I've seen anything like this.

Any help is highly appreciated.

Greetings,

Lucas

Vuforia::init() EXC_BAD_ACCESS

June 15, 2020 - 4:04am #2

Hi,

Is the information in another when you pause Vuforia in another scene? If yes, Vuforia will init and deinit automatically on scene entry/exit.

If not, could you please confirm that you are using VuforiaBehaviour.Instance.enabled = true/false to init/deinit vuforia?

Thank you.

Vuforia Engine Support

Log in or register to post comments