New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
StartSession Request Timeout Occurs Every Time After Unplugging/Reconnecting A Phone #238
Comments
I'd appreciate it if this issue could be tested with a different app and a different environment to rule out the phone/app/TDK as the cause. |
Relevant log snippet from when the Data Session actually gets established:
|
I just did some testing, and I think I have some more insight. I built and ran the SDL Example app and ran it on the same phone/TDK; it worked fine. I then noticed that the other app I had been using was trying to send RPCs after the proxy was disconnected. E.g., it was sending a Show and an UnsubscribeVehicleData RPC after the onProxyClosed, due to a bug in the code logic. I'm not sure which proxy instance it was actually sending this through (old or new). I put in a simple BOOL to have the app check proxy connection state before sending RPCs, and now it seems to be working fine. Obviously this is a case of an app doing a bad thing, but it seems like something that the proxy should be able to prevent? I'm not exactly sure where or what in the proxy is getting messed up to create this behavior, but this seems like another item to discuss as a future improvement. |
I was able to reproduce the behavior with the SyncProxyTester app by doing the following:
At step 4, the app shows that the StartSession request was sent, but believes that no response came back. The SPT app then times-out the request, and recycles the proxy. |
I created #241 to track the underlying error here, and linked back. I think we can close this issue, unless you have anything else. |
Sounds good. I'll close this one. |
Environment:
Reproduction Steps:
Expected Results:
App re-registers with Sync
Actual Results:
The SDL proxy connects to the Control Session, obtains a new protocol index, and closes that session. Then it starts a Data Session on the new protocol index, but does not receive a response to the StartSession request.
Recovery:
Terminate the app (swipe it out of the recent apps tray) and re-launch it.
Notes:
Based on viewing iAP traces, it does appear as if the headunit (SYNC3) is sending the response, but the proxy doesn't receive / process it somehow.
Log snippet:
The text was updated successfully, but these errors were encountered: