Closed Bug 914636 Opened 8 years ago Closed 8 years ago
[Cost Control] Cost Control is not processing incoming system messages if the application is not running in background
STR: This is better observed if DEBUG traces for Cost Control are enabled. 0- Set DEBUGGING to true in costcontrol/js/utils/debug.js and observe logs 1- Open Cost Control application 2- Kill the Cost Control application 3.a- Start a call and end or 3.b- Send a message or 3.c- Receive a message Expected: Some Cost Control logs are shows as the system messages are treated. Actual: Nothing is shows as the system messages delivered to the application but not handled.
The bug has a very low impact. Not taking leads to a complete unusable application (at least, the credit part).
Attachment #802370 - Flags: review?(francisco.jordano)
Comment on attachment 802370 [details] Fixing message handler Thanks for the fix Salva, the patchs is pretty clean and straight forward.
Attachment #802370 - Flags: review?(francisco.jordano) → review+
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Leo? is requested because this bug was detected during the device certification and it's required by it.
found in cert
blocking-b2g: leo? → leo+
Uplifted 986ad07aad596c5006c229e5f2304783f601c4cc to: v1-train: 163cbb1761b9d98902aed2a70d6f11dd6fd7dd18
You need to log in before you can comment on or make changes to this bug.