813428 - Development manifests used for the Social API when switched from Release to Beta channel

Status: RESOLVED INVALID

(Firefox Graveyard :: SocialAPI, defect)

Description

[Kinshuk Sunil]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Firefox/17.0
Build ID: 20121113065533

Steps to reproduce:

I switched channels from release to beta so that I can try out the Facebook Messenger for Firefox (It can only be disabled for beta users)


Actual results:

The Facebook Messenger for Firefox was turned on, but I only got the development demo sidebar and not the actual feature.


Expected results:

I should have gotten the Facebook Messenger for Firefox feature working as promised on the Facebook website (https://www.facebook.com/about/messenger-for-firefox)

Comment 1

[Kinshuk Sunil]

I temporarily fixed the problem by doing the following:

In about:config, I saw two manifests: social.manifest.facebook and social.manifest.http://mixedpuppy.github.com with different values.

I inferred that for some reason the Facebook manifest is not being used and since we cannot delete keys from about:config, I replaced the value for social.manifest.http://mixedpuppy.github.com with the value from social.manifest.facebook and the feature works.

Comment 2

[Kinshuk Sunil]

Attachment: A screenshot showing the Facebook messenger to be turned on, yet the user seeing the development sidebar

This screenshot shows the issue clearly:

Even after the user has the Facebook Messenger for Firefox turned on, the user only gets the developer demo of the feature

Comment 3

[Kinshuk Sunil]

Attachment: The about-config quick hack that I implemented to fix the issue at my end

In this screenshot, you can see that I copied the content of social.manifest.facebook to social.manifest.http://mixedpuppy.github.com and this resolved the issue for me, for now.

Comment 4

[:Gavin Sharp [email: [e-mail]]]

social.manifest.http://mixedpuppy.github.com isn't a pref that we ship by default - you must have added it manually at some point?

Tweaking the social.manifest.* prefs manually can currently result in some bad failures, because we don't support multiple providers (and so end up just using the "first", which can be a bit random). We're working on supporting multiple providers in bugs tracked by bug 786131, and when that is fixed this will be better supported.