1181642 - RunWhatsApp sometimes disconnects until restarted

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia, defect)

Description

[[e-mail]]

User-Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0

The app remains functional, you can navigate contacts and settings, but it doesn't send or receive, until restarted (apparently). I waited about an hour before restarting the first time.
This happened twice in one day.

Comment 1

[[e-mail]]

Attachment: system-b2g-application.ini

Comment 2

[[e-mail]]

Attachment: dev-log-main.log

Comment 3

[[e-mail]]

Attachment: properties.log

Comment 4

[[e-mail]]

Attachment: screenshot.png

Comment 5

[Doug Sherk (:drs) (inactive)]

Myk, any thoughts on what we can do with PluotSorbet issues being reported in BMO? I'm moving them to the Gaia component for now since we want to minimize the amount of bugs in Gaia::Feedback.

Comment 6

[Myk Melez [:myk] [@mykmelez]]

(In reply to Doug Sherk (:drs) (use needinfo?) from comment #5)
> Myk, any thoughts on what we can do with PluotSorbet issues being reported
> in BMO? I'm moving them to the Gaia component for now since we want to
> minimize the amount of bugs in Gaia::Feedback.

I've been filing issues in the PluotSorbet tracker to track the problems being reported in BMO and then leaving the bugs open pending resolution of the issues.

We could create a component in BMO for these bugs to get them out of Gaia::Feedback, but I'd still create issues in the PluotSorbet tracker, since that's where its developers are.  Alternately, I could close the bugs after filing the issues and direct folks to the issues for followup, although I'm not quite sure what resolution to use for such bugs.

Ideally, folks would file the issues directly in the PluotSorbet tracker, but I'm loathe to warn them away from BMO, since it's one of the primary feedback mechanisms for the Foxfooding program, and I'd rather do the extra work to transfer an issue than miss it because someone gets confused about which tracker to use.

Perhaps the ideal solution is to have a lightweight primary feedback tool for users to report any problem, which developers like us can then use to file bugs, issues, etc. as appropriate.  But maybe that's what bzlite is supposed to be. The problem is just that the reports it produces are actually fairly heavyweight (i.e. bugs in the bug tracking system).

Anyway, I guess I don't have a great idea.  I'm open to the options, however.  Do you have a preference?

Comment 7

[Myk Melez [:myk] [@mykmelez]]

As Bill Walker notes in bug 1177394, comment 24, he has directed his engineering team to stop work on RunWhatsApp in favor of our new focus on progressive web apps, so we won't have time to spend on this.