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
NSInternalInconsistencyException: Invalid state machine SDLStateMachine transition of target SDLLifecycleManager occurred from Reconnecting to Connected #1172
Comments
After our FordSync library was integrated in a third party app and released to production a significant number of these exceptions was recorded in one day - approximately 130. I have attached Crashlytics reports forwarded to us, these unfortunately aren't fully symbolicated crash logs though. |
Unfortunately, there's not much we can do without symbolicated crash logs. |
I was able to recreate a similar issue: Reproduction Steps: Logs: |
@justingluck93 Out of curiosity, which version of the library are you using? Also 6.1.2? |
@rosscintelematics no I was trying to reproduce the timer crash issues you are having and happen to come across this instead. I was testing on 4.7.5, I have been unable to reproduce the issue on the newest version of the SDL |
@ashwink11 we believe PR #1236 resolved this issue. Can you please review and confirm? Thanks! |
We are closing this issue as resolved via PR #1236. @rosscintelematics if you experience the issue after updating to the latest version of the SDL iOS Library, please let us know and we will re-open the issue. Thanks! |
I have still seen this issue appear with a few apps on SDL v6.4, v6.3.1 and v6.2.3 |
Okay, I'll reopen the issue. We have never been able to reproduce it and additional information would be helpful. We would like to know if at all possible:
|
|
@joeygrover -san @theresalech -san This issue is a top priority for Toyota. I would like know if it will be reproduced in the latest version. |
@E-SAITO-TMC This issue has not been directly addressed in the latest release. If you have reproduction steps, logs, or fuller crash reports, those would be helpful in addressing this issue. |
@joeljfischer -san Thank you for your reply. I understand that this issue is not solved. I have not been able to reproduce it too. So, I have no data such as logs, crash reports. |
@joeljfischer -san We tried 50 times, and could not reproduce this issue. Would you like to keep this issue open? |
@E-SAITO-TMC Because there was activity on this in February, we will keep this open for now to see if additional information can be gathered. |
@joeljfischer -san I understand. Thank you for your cooperation. |
This has become a top crash for a good amount of our users. From what I can gather with our own logs, this is occurring when users are connecting to CarPlay and then SDL crashes. We just updated to 6.7.0 of SDL, but I do not think this will resolve the issue because of the @throw exception inside of |
@djbrooks111, thank you for the crash report. What version of sdl_ios are you using? Some of the lines in the crash report don't make sense based on the current version. If you are ever able to capture an SDL debug log when this occurs that would also help tremendously. We have never been able to repro this issue. |
Unfortunately, I only found the crash logs via Xcode/Firebase so I can't get any debug logs. We are on 6.7.0 of sdl_ios. My initial thought does have to do with a CarPlay connection somehow interfering with SDL |
I would suggest that if the SDL tries to transition and the states in invalid, that it doesn't throw so the SDK/app doesn't crash |
Bug Report
NSInternalInconsistencyException: Invalid state machine SDLStateMachine transition of target SDLLifecycleManager occurred from Reconnecting to Connected
Reproduction Steps
Received crash report from released app, no steps know.
Expected Behavior
App should not crash
Observed Behavior
OS & Version Information
Test Case, Sample Code, and / or Example App
issue_695_crash.txt
The text was updated successfully, but these errors were encountered: