iOS app OpentOk library crashes with INVALID_ADDRESS - opentok

We have an issue with iOS app stability. Our Application crashes inside the OpenTok library. It crashes inside the library and the stack trace does not contain any reference to the app code.
A list of last calls in the stacktrace:
[OTKitSessionDelegate otkitStreamCreated:]_block_invoke
Fatal Exception: NSInvalidArgumentException
-[_NSInlineData session:streamCreated:]: unrecognized selector sent to instance 0x106044600
[OTKitSessionDelegate otkitSessionWillCloseSocket] + 3482407
Crashed: Thread
EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x00000000c202000c
[OTKitPublisherDelegate otkitPublisherStreamCreated:]_block_invoke
EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x0000000000000010
I'm using the latest version of OpenTok library 2.14.
Also, I've used different tools for monitoring the app if there are some thread synchronization or buffer overflow issues by using Address Sanitizer and Thread sanitizer and other xcode tools. No issues found.
Please assist with that. I will be very appreciate for any clue.
Thanks

It looks like you are releasing the delegates without setting the OpenTok objects' delegates to nil.
Follow this order:
publisher.delegate = nil;
subscriber.delegate = nil;
session.delegate = nil;
yourDelegate = nil;

Related

Xcode won't start after OS update

I just updated my macOS to 10.13.3 supplemental with the Telugu fix. Now I can not start Xcode 9.2 anymore.
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: DYLD, [0x1] Library missing
Application Specific Information:
dyld: launch, loading dependent libraries
Dyld Error Message:
Library not loaded: #rpath/libswiftDispatch.dylib
Referenced from: /Applications/Xcode.app/Contents/MacOS/Xcode
Reason: image not found
Any suggestion on how to fix this?
Confirming that Avast Business Antivirus broke my Xcode. To fix it, I made sure OSX was updated, then I opened Avast, opened Virus Chest, and restored libswiftDispatch.dylib then restarted my machine.
Turns out that AVG anti virus placed the libswiftDispatch.dylib in quarantine as a false positive. Multiple programs on my Mac failed to start due to this reason.
I removed the AVG app and reinstalled XCode to get everything working again.

Unable to find system thread 1C10

I am developing an Electron app for Windows and within the past couple weeks the app has begun to crash intermittently without any apparent cause. I downloaded the windows debugging tools to examine the crash dumps and found the error Unable to find system thread 1C10. What does this error mean? How can I proceed?

Xcode 7.1 crash when create new project/file

I'm experiencing a crash in Xcode 7.1 when I try to create a new Project on Mac OS X 10.11 (15A178w)
Crash Log:
Process: Xcode [69405]
Path: /Applications/Xcode.app/Contents/MacOS/Xcode
Identifier: com.apple.dt.Xcode
Version: 7.1 (9079)
Build Info: IDEFrameworks-9079000000000000~8
App Item ID: 497799835
App External ID: 813804225
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Xcode [69405]
User ID: 501
Date/Time: 2015-11-11 16:09:56.301 +0800
OS Version: Mac OS X 10.11 (15A178w)
Report Version: 11
Time Awake Since Boot: 110000 seconds
Time Since Wake: 17000 seconds
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Application Specific Information:
Sending goNextOrFinish: to <IDEAssistantWindowController: 0x7f87e7885220> from <NSButton: 0x7f87e942fe00>
ProductBuildVersion: 7B91b
UNCAUGHT EXCEPTION (NSInvalidArgumentException): -[NSOpenPanel setAccessoryViewDisclosed:]: unrecognized selector sent to instance 0x7f87e9669840
UserInfo: (null)
Hints:
0: Sending goNextOrFinish: to <IDEAssistantWindowController: 0x7f87e7885220> from <NSButton: 0x7f87e942fe00>
Does anyone know what causes this issue & how I can fix it?
I've just tried the same: create an empty project (with main interface set to LaunchScreen) and it crashed. Doing the same with main interface set to main works. Probably, in the first case, you should define your LaunchScreen ;)
Same happened to me, and I tried installing the Xcode 8 beta 2, to find if the problem was with my XCode 7. The issue happened again. Just tried to recollect how it happened first time, and it came to my mind that I had actually tried to create a git repository online, using my gitHub account, from XCode. When creating a new project, Xcode provides option to choose to create a local git repo or an online repo. I'd opted for an online repo option, and ever since i got this issue.
Finally I tried turning off the WiFi, and Voila!!! There it runs, just fine!
Once the project is created and built fine, I turned WiFi back on, and Thank God, things are back to normal!
Hope this helps someone!
I faced same issue it was very irritating , what i did is i just cleared derived data for the project in which i was facing the issue and it worked for me!! :)

App rejected due to crash on app store

I had developed an app and uploaded it on app store. The app got rejected due to crash. But my problem is that I cannot detect this crash while running app on device for testing. App is working properly on the device.
The app is been created in unity and then I had exported it to xCode.
So I want to ask that how can I get to know about where it is getting crashed. Also how can I traverse the crash log.
Any help will be appreciated
Thanks in advance
Did they tell you about:
– Where crash happened? (At launch, On logging in, or in specific screen)
– Did they send you any images?
– Which devices and iOS they were testing
– They will surely send you crash log, please post it.
You said you cannot replicated the crash, but did you tried with simulator or real devices?
Since you are missing many information, I cannot give you a certain answer. My advice for you is to
1) Updating your question
2) Read my post about how to do when your app got rejected, or my post about how to symbolicate crash log
3) You can also follow the topics in stackoverflow: Iphone App was Rejected Due to We found your app crashed on launch so we were unable to review it and App rejected due to crash. They are very helpful
Actually, app was getting crashed on devices with 64 bit architecture. as older version of unity don't support 64 bit architecture. Unity 4.6.2 onwards support 64 bit architecture. Thus rebuild the ios app and it worked fine.

Delphi Mac OS X

I have problem with Delphi Mac OS X development. I get debug assertion failure error when I try to debug program. My application is just simple form where is few TLabel and TEdit component. Also there is two TImage components where is two images included. And there is also one TProgressBar component on my form. Connection between mac and my pc works ok. It tries to start application when I run it but it disappiers and Windows 7 and Delphi shows error debug assertion failure.
At first there was problem with deployment and my project file was corrupted so I created new project and then I added my old form to new project. After that compiling application works ok but now I get error message debug assertion failure.
I have Delphi XE5 and Windows 7 64-bit.
Mac computer is macbook pro.
PAServer on OSX is a bit buggy and it sometimes crashes with these assertion failures. It's not your application that raises the assertion failure.
If PAServer crashes with an Assertion when trying to start your application, then I'd suggest the following:
1. Close Delphi and PAServer
2. Wait until both have completely shut down
3. Start Delphi and PAserver again
Sometimes this already solves the problem.
If this does not help, try starting your application from OSX from the Terminal and see what happens. Chances are you see an access violation or similar printed to the terminal window. If that is the case you might have a bug in the initialization part of a unit. PAServer likes to crash with an assertion failure if that happens. You'll have to debug the start-up process of your application using F7 and F8. You might be able to speed this up by setting breakpoints in the initialization of some units.
Agree with Sebastian. PAServer is not stable at this stage. There are MANY reports about this:
PAServer can't load dyld: Library
Delphi XE5 PAServer Unauthorized user
How can i debug my DLL project with Delphi's PAServer
Delphi XE4 iOS can't connect to PAServer
https://stackoverflow.com/questions/28115855/paserver-crashes-on-win64
Delphi Mac OS X
Solution: wait until they release something stable. (You will have to pay again, of course)

Resources