Closed sodastsai closed 9 years ago
zenelk
commented
9 years ago Hey there, I'm having trouble reproducing your issue. Could you tell me which commit you are using? This looks like an issue that was fixed at commit e0fcc6c82625d91c1a97cccc9d41877a10d67cfd on the beta branch.
sodastsai
commented
9 years ago orbotix/Sphero-iOS-SDK@3609b627381b8ebf135d036fcc11f1ecfb32d000
zenelk
commented
9 years ago That's the same commit that I'm using. Can you give me a rough idea what you are sending to the robot (and what the robot should be sending back) so that I can try to get it reproducing?
Also, can you get this problem to occur in any of the samples that are shipped with the SDK frameworks?
zenelk
commented
9 years ago After taking some time and looking through this, I don't see any way this can happen. I am thinking that you have the wrong version of the framework. In the RKSession class, parseStringRepsonse is never recursively called (in any released versions). Try the newest framework that I just pushed, it should work for you.
I'm going to leave this issue open for a bit until I'm sure that this is fixed.
sodastsai
commented
9 years ago Hi, just encounter this again.
This time I met this when switching apps (click the iPad home button quickly). (as the instruction in demo app, while the app resigning active, the app will disconnect sphero)
At first, I receive following lines in console
2015-03-31 18:33:27.989 Tickle[1049:244621] OBX:-[RKSession processPartialResponse] - Correct SOP1, incorrect SOP2. Dumping to string response...
2015-03-31 18:33:27.991 Tickle[1049:244621] OBX:-[RKSession processPartialResponse] - Correct SOP1, incorrect SOP2. Dumping to string response...
2015-03-31 18:33:27.992 Tickle[1049:244621] OBX:-[RKSession processPartialResponse] - Correct SOP1, incorrect SOP2. Dumping to string response...
2015-03-31 18:33:27.993 Tickle[1049:244621] OBX:-[RKSession processPartialResponse] - Correct SOP1, incorrect SOP2. Dumping to string response...
2015-03-31 18:33:27.994 Tickle[1049:244621] OBX:-[RKSession processPartialResponse] - Correct SOP1, incorrect SOP2. Dumping to string response...
2015-03-31 18:33:27.996 Tickle[1049:244621] OBX:-[RKSession processPartialResponse] - Correct SOP1, incorrect SOP2. Dumping to string response...
2015-03-31 18:33:27.997 Tickle[1049:244621] OBX:-[RKSession processPartialResponse] - Correct SOP1, incorrect SOP2. Dumping to string response...(repeated many lines ...)
then crashed and get call traceback like above post.
zenelk
commented
9 years ago This is with the frameworks pushed in commit d6a47785d06dc71a399b376400f7b45c1ee682af, right? If so, could you give me a snippet of your app will resign active code where you are disconnecting? I still cannot reproduce the issue.
sodastsai
commented
9 years ago it's d6a4778 right. and the code while receiving UIApplicationWillResignActiveNotification is just following lines:
- (void)applicationWillResignActive:(NSNotification *)notification {
[RKRobotDiscoveryAgent stopDiscovery];
[RKRobotDiscoveryAgent disconnectAll];
}I could not reproduce this issue each time either. Actually it's rare, about 1~2 times during our internal test (about 2 days). I'll update to you if encountering this again.
thalmicMark
commented
9 years ago I'm noticing this issue as well on d6a4778. In our appWillResignActive we only call [RKRobotDiscoveryAgent stopDiscovery] though. We've got the background bluetooth capability set up, and it looks like Sphero and Ollie can be controlled fine while the app is backgrounded.
zenelk
commented
9 years ago Hey guys, we have a fix coming down through the pipes and is slated for the next release of the beta SDK. That being said, I actually don't have the timeframe on that release, but I would imagine sooner than later.
sodastsai
commented
9 years ago Any update on this? I've got lots of crash events from users ...
zenelk
commented
9 years ago We are slating a release for next week, and I haven't seen anything like this in our base for quite some time. Can you check again when that release comes out?
sodastsai
commented
9 years ago sure. looking forward to it :)
zenelk
commented
9 years ago Hey sodastsai, our current release didn't quite meet the quality that we wanted, so it had to be delayed. We're still looking for as soon as possible to get it out, and I'll let you know when I find out more.
sodastsai
commented
9 years ago 👍
vves
commented
9 years ago Fixed in 3.1
Hi,
While connecting with Sphero by the 3.0 Beta 3 SDK, sometimes I encounter this crash event about
RKSession. It seems an infinite recursion.