Closed Bug 843906 Opened 11 years ago Closed 11 years ago

"Not Allowed" after mozContacts.save on central/inbound; works on mozilla-b2g18

Categories

(Core :: DOM: Device Interfaces, defect)

defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: jgriffin, Unassigned)

References

Details

Gaia UI tests are failing on mozilla-central and mozilla-inbound when trying to save a contact programmatically, but the same tests pass on mozilla-b2g18.  

When they fail, mozContacts.save() generates a "Not Allowed" message.  The code we use to save the contacts is here:

https://github.com/mozilla/gaia-ui-tests/blob/master/gaiatest/atoms/gaia_data_layer.js#L9

The error we get is:

E/GeckoConsole(  109): Content JS ERROR at chrome://marionette/content/marionette-listener.js:1469 in GaiaDataLayer.insertContact/req.onerror: error saving contact Not Allowed

See full log:  
https://tbpl.mozilla.org/php/getParsedLog.php?id=19960632&tree=Gaia-Master&full=1

If this can't be fixed soon, we'll have to disable contacts tests on mozilla-central/inbound.  We're trying to green up the tests so we can unhide them in TBPL.
maybe known, but to be explicit in case it helps with debugging: mozilla-central and mozilla-inbound are gecko22, while mozilla-b2g18 is... well... gecko18.
I'm disabling test_edit_contact.py on the panda until this is resolved.
Gregor or Alberto or Francisco may have ideas here.
Are the tests disabled now or did we fix the problem?
We've basically deprecated panda tests for the time being; we'll get the same tests running on B2G desktop builds, and we can revisit this then if the problem recurs.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.