4

Sometimes the request made by QBChat (retrieve dialog list, chat message history, send message...) cause the app to crash.

When I traced back, the EXC_BAD_ACCESS occur in [EndpointsAPIStorage retrieveEndPoint] called in [QBQuery performInBgAsyncWithDelegate].

Does anyone have any idea about this?

Jonathan Le
  • 41
  • 3
  • I too receive the same error. – ems305 Sep 27 '14 at 21:12
  • At first I thought it was iOS 8 SDK compatible issue, but when running sample chat app and creating another project, the problem doesn't appear to happen. Kinda weird. – Jonathan Le Sep 28 '14 at 12:32
  • I tried creating another application and I still get the same error. – ems305 Sep 28 '14 at 20:26
  • 1
    After digging around, I found out that the problem might related to Crashlytics, in which when I remove Crashlytics, the problem magically went away. For testing purpose, I suggest you to follow the sample-chat app, with the basic flow like this: 1) Open app --> run splashscreenVC that create QBsession. 2) Once done, go into the app, and the first thing to call is to get all dialogs from QB (which is the most common crash that I got before). – Jonathan Le Sep 29 '14 at 01:52
  • Interesting. It seems my crash comes from a completely different call. Mine crashes every time on the method QBRequest createGeoData. – ems305 Sep 29 '14 at 04:48
  • I have the same issue. I can create a session, but I get the crash in retrieveEndPoint when calling logInWithSocialProvider. Removing the call to [Crashlytics startWithAPIKey] fixes the issue. Is there any way to report a bug to QuickBlox? – Rich Bruchal Oct 01 '14 at 20:18
  • Try to use 2.0.9 update http://quickblox.com/developers/IOS#Download_iOS_SDK – Darya Oct 03 '14 at 11:24
  • I'm getting the same error as well. Is your bad access code = EXC_I386_GPFLT? – ken Nov 14 '14 at 03:38

0 Answers0