Skip to content
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

McuReader fails on service restart #24

Open
iulianbute opened this issue Jul 10, 2023 · 6 comments
Open

McuReader fails on service restart #24

iulianbute opened this issue Jul 10, 2023 · 6 comments

Comments

@iulianbute
Copy link

i can only restart the service only if i clear data on android settings for the service app (not the client app)
fresh full upgrade to ksw 4.0.7 firmware to check if issue persists (with full reset)
crashes on service restart, os restart, any restart :)
if i clear service data, it starts successfully.
ksw-toolkit client v1.2
service version 1.2.1
mcu 0230A0eGS-E39-KTL-BA-211011G
System 4.0.7 10-501A-EA-1-...
previosly i have used them both without issues (started crashing after updating both client/service while on os 3.9.x)

2 errors i got:

1st:
KSW-ToolKit-CoreService:
KSW-ToolKit-Service stopped

2nd:
KSW-ToolKit-CoreService:
Could not start McuReader!
[Ljava.lang.StackTraceElement;@54325d6

@ocouch
Copy link

ocouch commented Nov 11, 2023

I have the same issue.

Service version 1.2.1
Client 1.2
MCU Ver 6150A0eALS-C&C-KTL-DC-230107G
App Ver Ksw-S-M600_OD_v1.5.6NEXAI
System Ver 12-662EA-868927051813041

Could not start McuReader!

[Ljava.lang.StackTraceElement;@545fcf0

Clearing app data resolves the issue. Clearing cache data does not.

@ocouch
Copy link

ocouch commented Nov 11, 2023

Tried earlier versions of service with v1.2 of Client.

Issue persists with service version 1.2. Issue disappears with service version 1.1.0.

However, in v1.1.0 am unable to enable Start at Boot setting (gui slider toggles to on, but does not retain setting)

My car did not have an idrive system from factory. I'm not sure if this might be related to the problem?

@Snaggly
Copy link
Owner

Snaggly commented Nov 13, 2023

This is probably caused by the ConfigManager trying to parse an incompatible config file and just throws an uncaught exception. This entire manager needs to be reworked for the coming update as the current implementation seems very fragile!

@ocouch
Copy link

ocouch commented Nov 13, 2023

For now rolling back to both version 1.1 of client and service together seems to be working 👍

@Snaggly
Copy link
Owner

Snaggly commented Nov 16, 2023

I refactored that ConfigManager in this commit: 18512a8

Hopefully with that the riddles of this crash will be fixed.

@ocouch
Copy link

ocouch commented Nov 17, 2023

I tested out the update with Client v1.2 but no cigar. Still same issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants