Standalone Link-Clicker UI doesn't start a call on FxOS if the FxOS app is not installed (until configuration is present)

RESOLVED WONTFIX

Status

RESOLVED WONTFIX
4 years ago
4 years ago

People

(Reporter: standard8, Assigned: standard8)

Tracking

unspecified
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

4 years ago
Per bug 1077059, we currently don't have a valid config for FxOS application settings.

If the FxOS app is not installed, and we don't have the config settings, then we should revert to doing a call in the standard way.
(In reply to Mark Banner (:standard8) from comment #0)
> Per bug 1077059, we currently don't have a valid config for FxOS application
> settings.
> 
> If the FxOS app is not installed, and we don't have the config settings,
> then we should revert to doing a call in the standard way.

Is this bug specific to the Desktop client or the B2G client?
(Assignee)

Comment 2

4 years ago
(In reply to Anthony Hughes, QA Mentor (:ashughes) from comment #1)
> Is this bug specific to the Desktop client or the B2G client?

Neither: Standalone link-clicker UI.
(In reply to Mark Banner (:standard8) from comment #2)
> (In reply to Anthony Hughes, QA Mentor (:ashughes) from comment #1)
> > Is this bug specific to the Desktop client or the B2G client?
> 
> Neither: Standalone link-clicker UI.

Okay thanks. I'm moving this to Loop::General since this isn't actually about the Desktop client itself.
Component: Client → General
(Assignee)

Comment 4

4 years ago
We've been dealing with all standalone bugs under client, hence moving it back. Some of the code is shared between the two which is why we've kept the one component (at least so far). I will update the title though.
Component: General → Client
Summary: Loop client should still start a call on FxOS if the loop.config.fxosApp* configuration settings aren't present → Standalone Loop client should still start a call on FxOS if the loop.config.fxosApp* configuration settings aren't present
(Assignee)

Comment 5

4 years ago
I've just been discussing this with Maire over irc. The work to fix this is more complicated than initially thought. For now, we're going to deploy and be aware that this is an issue.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WONTFIX
Summary: Standalone Loop client should still start a call on FxOS if the loop.config.fxosApp* configuration settings aren't present → Standalone Link-Clicker UI doesn't start a call on FxOS if the FxOS app is not installed (until configuration is present)
(Assignee)

Updated

4 years ago
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
(Assignee)

Updated

4 years ago
Status: REOPENED → NEW
(Assignee)

Updated

4 years ago
No longer blocks: 1077059
Depends on: 1077059
backlog: --- → -
(Assignee)

Comment 6

4 years ago
Standalone is now updated & deployed, marking this as wontfix.
Status: NEW → RESOLVED
Last Resolved: 4 years ago4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.