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
TIMOB-3286 Enable services to be re-startable #1433
Conversation
…ce), don't let getTopActivity hang on latch.
…he first module being executed is service-related, not activity-related.
Conflicts: android/modules/app/src/java/ti/modules/titanium/app/AndroidModule.java
…_NOT_STICKY and START_REDELIVER_INTENT mode constants.
Code reviewed and Accepted. Functional test pending |
During functional testing on rooted droid 2 2.2 under V8, the service code (log) never starts executing again after the process is killed. This was done with the app currently in the foreground. The log shows the application service being restarted but then 5-10 seconds later dying and being rescheduled to start again EDIT: it should be noted that this behavior is before startMode is changed and I have not yet tried with changed start modes |
I just tried a device (2.2) for the first time (using 3rd party process killer) and the behavior as expected. Do you have a logcat or something to show me? |
Crash log provided on ticket for V8. Same problem exists on Rhino and seems to stem from "InputManagerService: Got RemoteException sending setActive(false) notification to pid 4935 uid 10042" for both runtimes. |
From the trace:
I submitted the PR when it was already 2.0.0. I checked out cb70ac8 and checked the So, at least the time that you got the log, you seemed to have built against the wrong version. But maybe the original time you saw the failure was when built against the correct version. |
Functional test passed. Accepted |
TIMOB-3286 Enable services to be re-startable
See Testing Notes