Getting a runtime crash like that while trying to connect room in Vidyo io SDK.
Thread 1: EXC_BAD_ACCESS on this file. #1 0x0000000103aec9dc in
LmiWindowCreateChild_ at
/tmp/SDK.Release.TRINITY_20_1_0_9.build.7uOSFpBWGF/source/SDK/Lmi/Ui/LmiWindowIPhone.m:394
If you did everything on documentation's said. Removing both UnsafeMutableRawPointer & UnsafePointer like below helped me overcome that runtime crash on newly created Swift app.
If you're still experiencing an error, checking sample app's (from GitHub) build settings may help too.
Documentations should be updated with up-to-date informations by Vidyo.io team.
VCConnectorPkg.vcInitialize()
self.connector = VCConnector(&self.vidyoView,
viewStyle: .default,
remoteParticipants: 4,
logFileFilter: "warning",
logFileName: "",
userData: 0)
Related
In the project organizer, one project I'm working on hasn't shown any crashes since I updated to Xcode 9. All of the previously shown crashes disappeared too. I have Fabric in the app, but I'm testing mostly on Apple Watch and Fabric doesn't support watch crashes. I submitted the bug to Apple's Bug Reporter several weeks ago but haven't received a response. Is there anywhere or any way else I can get crash reports, specifically for WatchKit?
Thank you!
You could try on your phone going to Settings -> Privacy -> Analytics -> Analytics Data. Scroll through the Data and look for crashes related to your application.
after using my App created with PhoneGap + iOS for some time, the app crashes with following error message:
[UIWebOverflowScrollView _viewDelegate]: message sent to deallocated instance 0x21e330
I have no idea why this problem is happening. I can not reproduce the error, it happens just suddenly. I am aware that this problem is related to any kind of object that has been released, but as I am using PhoneGap (+ QrCode Plugin) I am sure that this problem is related to Phonegap or to the BarcodeScanner plugin. Could someone give me any insights on how to solve this problem? I have updated to the new PhoneGap version 1.9.0.
Related question: UIWebOverflowScrollView Exception in Phonegap Application
Do you use "-webkit-overflow-scrolling: touch" in your CSS?
We had the same problem with our phonegap-app, it sometimes crashed with the same error message (and sometimes only locked up the upper screen), and it got fixed by removing that said bit of CSS.
If you are using "-webkit-overflow-scrolling: touch", perhaps test if you can get your app to crash without it?
See apache.org for more info on the said bug and possible solutions.
We solved the situation by using iScroll instead of the CSS.
Sorry for the late answer, we just got our problem fixed :P.
I've been using Xcode to develop iPhone Apps for a couple of years now. In the last couple of months I've updated to Xcode 4.2 for iOS 5 development.
On previous versions of Xcode I've found it very rare that I get a crash without any log of where the error happened. With Xcode 4.2 / iOS 5 I find that I regularly get crashes without any log. I just end up with the code stopped in main.m with a message like "program received signal SIGABRT" (or a couple of other messages) but no log messages at all. (I'm looking in the "All Output" window at the bottom of the Xcode gui).
For example, my last one was where I used the initWithNibName:bundle: method but typed in the incorrect nib name. The code passed this line without error, but when I got to the pushViewController:animated: method the code crashed with the SIGABRT message but no log messages. It took a while for me to find my typo...
I'm sure in previous versions of Xcode I would see a far more informative message...
Is there something I'm missing in Xcode 4.2? Should I enable some extra debugging feature? Any way to get it to give more useful crash information? Or is this a know problem with iOS 5 / Xcode 4.2?
Thanks for any pointers...
You are not alone, I have found this too. I often find there is not enough information in the log to diagnose the crash with the lastest xcode. I have two tips that might help.
Run on the actual device. I often find for some reason I get more detailed logs when it crashes on the device.
Worst case, you can go into the organiser and check the crash logs of the device, this will give you what thread crashed and what you call stacks looked like when it crashed.
Switch between the GDB and LLVM compiler and or debugger. I havent experitmented enough with this but I believe this has helped on occasion.
I am getting an assertion error when I launch Xcode 4, which I just installed. I have looked on Google and Stackoverflow, and I could not find anybody with the same problem as me. As soon as I open Xcode 4, it shows me the welcome screen. I try to open a project, and Xcode gives me a message saying I can continue using Xcode in an inconsistent state or I can crash Xcode. When I click on more details it says "ASSERTION ERROR" followed by some other debugging info. I can't copy it because when I try to highlight it Xcode freezes completely.
Any suggestions?
NOTE: This is different from other people who get this error when they build, I am getting this when it is LAUNCHED.
Could it also be because I am continuing a project from the previous version of Xcode?
[UPDATE] I have solved the problem. If you are also encountering such an error, try reinstalling Xcode 4. If you continue getting the same error, then follow the advice of #mrueg.
Xcode 4 has various bugs, and the assertion error is just a general warning that an inconsistency was detected.
The best way to get more info on the actual error that happened is to crash Xcode when you get the error and then show the details.
It probably also makes sense to send the crash report to Apple so they can fix the bug.
It is probably best to keep using Xcode 3 (which is still downloadable for the newest SDKs) and wait for the next version of Xcode 4 if your project crashes it.
Debugger is telling me this, when I run my app on device:
Program received signal: “EXC_BAD_ACCESS”.
mi_cmd_stack_list_frames: Not enough frames in stack.
mi_cmd_stack_list_frames: Not enough frames in stack.
I don't get information about where in code that happens. That's all I get. Any idea what that could mean?
The app crashes after that. When the device is not connected to the mac, it still crashes, so not a debugger problem.
Building on the 4.0 sdk onto a 3.1.3 phone caused this for me.
Fixed by weak linking UIKit in the target.
EXC_BAD_ACCESS happens when a message is sent to an object that has already been released.
I've seen "mi_cmd_stack_list_frames: Not enough frames in stack" before when trying to release something that's already been released as well.
My suggestion is to set the NSZombieEnabled environment variable and see which released object you are trying to access.
This site has a great tutorial on it:
http://www.codza.com/how-to-debug-exc_bad_access-on-iphone
I've seen this caused by at least three different kinds of problems:
• As described in the other answer, overrelease errors can do it.
• I had it happen when I was upgrading an app to use iAd and IOS 4.0. I think the problem was that I tried to use the iAd framework in the 3.0 version of the app as well, which of course isn't possible because iAd is only around in 4.0 and above.
• I had it happen when I removed a bunch of stuff from an app and recompiled, but vestiges of the old stuff were still around on the simulator. Resetting the simulator cleared the problem. What I was removing was the Flurry API. I'm afraid I don't know what, specifically, in there stuck around and caused the problem.
I have the same issue. My solution is:Quit the Xcode and then restart it after waiting some time.
I've got such a message when was trying to launch an app on iPhone under iOS 3.1.2 with a string like that
Class messageClass = (NSClassFromString(#"MFMessageComposeViewController"));
At the same time that works well when I use a device with iOS 4.
So I can assume that app could crash when start running on device if there are any references to iOS4-only classes.
Creating a new project and copying all the existing files in it solved this problem for me.