The Wikitdue SDK 5.1.x adds a fix for this and at the same time enables you to control the internal memory management to be disabled.
However, if you have this crash it might point to a faulty memory management in your application. Please verify the code and especially the WTArchitectView usage and when/if it's view controller is created/released.
I have exactely the same problem since i migrate to wikitude 5.
Hope somebody can help us.
T
Technik
said
over 7 years ago
I am having the same issues. Can anyone be of help?
D
DJ B
said
over 7 years ago
I am getting the same error message. How do I deallocate WikitudeNativeSDK?
M
Mehmet Emre
said
over 7 years ago
hi, i am having same problem after updating Wikitude framework file to iOS_5_0_0 from iOS_4_1_1.
i am also not using Google Logging library or samething like that. Like i said this error happens only after upgrading wikitude sdk 5.
And i don't understand how to deallocate WikitudeNativeSDK pointer. "To deallocate the object, you need to set the WikitudeNativeSDK pointer to nil." how can i manage to do that?
i am using multiple architectView on 4 different viewcontroller. and this error happens when switching from each other. My each architectView serves differant roles like location and target image based.
NSLog(@"This device is not supported. Show either an alert or use this class method even before presenting the view controller that manages the WTArchitectView. Error: %@", );
}
;
;
any help appreciated.
Regards.
A
Andreas Schacherbauer
said
over 7 years ago
Hi, The Wikitude SDK does not offer a method called 'stopWikitudeSDKRendering'. This method also does not deallocate the object. To deallocate the object, you need to set the WikitudeNativeSDK pointer to nil.
Best regards
Andreas
B
Boggarapu Kartheek
said
over 7 years ago
Hi Andreas,
Even though I have deallocated the previous object by using ; I am getting again the same error.
Regards,
Kartheek
A
Andreas Schacherbauer
said
over 7 years ago
Hi Boggarapu, The problem here is, that you allocate a new object of type `WTArchitectView` when there is already one active or the previous one was never deallocated. Please verify that your previous WTArchitectView object is deallocated when you create a new one.
Best regards
Andreas
B
Boggarapu Kartheek
said
over 7 years ago
Hi,
I am using Official SDK version 5, And using JS API.
OS Version is 8.1. in my ipad.
This is happening in my own app.
I have checked it in my code and I never used InitGoogleLogging().
Thanks,
N
Nicola Radacher
said
over 7 years ago
Hi,
-Which SDK version are you using - the official version 5?
-Are you working with the Native or JS API
- What are your OS version and test device model.
- is this happening in your own app or in the sample app
The issue sounds like it has something to do with Google logging 'Check failed: !IsGoogleLoggingInitialized() You called InitGoogleLogging() twice!'. Can you check your code for the google logging.
Greetings
Nicola
B
Boggarapu Kartheek
said
over 7 years ago
Hi,
Everything is working fine in my application. But when I am going back and again entering into ARView my app is getting crashed with following errors.
Check failed: !IsGoogleLoggingInitialized() You called InitGoogleLogging() twice!
Boggarapu Kartheek