Closed Bug 831079 Opened 12 years ago Closed 12 years ago

No error from SMS database service for FS full

Categories

(Core :: DOM: Device Interfaces, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 823010

People

(Reporter: alhadp, Assigned: vicamo)

Details

There is a certification test that checks to make sure Class 0 SMS messages (one time notification messages) are shown on the UI when the phone's storage for SMS messages is full. This test relies on the RIL stack returning a memory full error on RIL_REQUEST_NEW_SMS. However the SMS database service does not return an error from nsISmsDatabaseService::SaveMessage. Since the transaction looks to be asynchronous, and even in there, the error callback is silently failing, there isn't a way to return an error back to the RIL request. Question is, is this certification test important for v1? If so, we will need support from the SMS database service to somehow notify about FS errors.
blocking-b2g: --- → tef?
Class-0 messages are shown directly to users without being stored in database. Do you have some more detailed behaviour description? Does this issue duplicates bug 823010?
Depends on: 739143
Component: General → DOM: Device Interfaces
Product: Boot2Gecko → Core
Assignee: nobody → vyang
(In reply to Vicamo Yang [:vicamo][:vyang] from comment #1) > Class-0 messages are shown directly to users without being stored in > database. Do you have some more detailed behaviour description? Does this > issue duplicates bug 823010? Vicamo, yes this issue looks like a duplicate of bug 823010. Could you please check with TEF that this feature is needed for v1 or not?
Re-request tef? in bug 823010.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Flags: needinfo?(alhadp)
Resolution: --- → DUPLICATE
blocking-b2g: tef? → ---
Flags: needinfo?(alhadp)
Furthermore, if you believe this bug blocks bug 808607, please do the same with the duplicated one (bug 823010) so it can be properly tracked
No longer depends on: 739143
You need to log in before you can comment on or make changes to this bug.