Closed Bug 1202632 Opened 10 years ago Closed 10 years ago

Can't send or receive SMS

Categories

(Firefox OS Graveyard :: Gaia::Feedback, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1202788

People

(Reporter: theo, Unassigned)

Details

(Keywords: foxfood, Whiteboard: [bzlite])

Attachments

(5 files)

User-Agent: Mozilla/5.0 (Mobile; rv:43.0) Gecko/43.0 Firefox/43.0 Since a couple builds on dogfood-latest, when I try sending a text message, I got 'An error occured' popup. Don't receive messages either.
Attached file dev-log-radio.log
Attached file dev-log-system.log
Attached file dev-log-main.log
Attached file properties.log
What's logged when I try sending it: E/GeckoConsole( 315): [JavaScript Error: "IndexedDB UnknownErr: ActorsParent.cpp:895"] E/GeckoConsole( 315): [JavaScript Error: "IndexedDB UnknownErr: ActorsParent.cpp:593"] E/GeckoConsole( 315): [JavaScript Error: "UnknownError" {file: "resource://gre/modules/MobileMessageDB.jsm" line: 2910}] E/GeckoConsole( 315): [JavaScript Error: "AbortError" {file: "resource://gre/modules/MobileMessageDB.jsm" line: 2866}] E/Messages( 1611): Content JS ERROR: Error Sending: {} E/Messages( 1611): at onError (app://sms.gaiamobile.org/gaia_build_defer_index.js:575:47) W/Built-in Keyboard( 1319): Content JS WARN: InputMethodManager: inputcontext.getText() was rejected. W/Built-in Keyboard( 1319): at InputMethodManager.prototype.updateInputContextData/p< (app://keyboard.gaiamobile.org/gaia_build_defer_index.js:257:346) W/Built-in Keyboard( 1319): Content JS WARN: InputMethodGlue: call setUpperCase() when inputContext does not exist. W/Built-in Keyboard( 1319): at InputMethodGlue.prototype.setUpperCase (app://keyboard.gaiamobile.org/gaia_build_defer_index.js:252:142) E/Built-in Keyboard( 1319): Content JS ERROR: TypeError: this.app.inputContext is null E/Built-in Keyboard( 1319): at AbortablePromiseQueue.prototype.run/this._queuedTasks< (app://keyboard.gaiamobile.org/gaia_build_defer_index.js:309:18) I/Gecko ( 1319): InputContextDOMRequestIpcHelper received message without context attached.
Ok, with a fresh profile it worked, most likely a IndexedDB corruption — no idea how this happened.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: