Closed Bug 1907643 Opened 1 year ago Closed 1 year ago

Using a localhost FxA server throws: Remote server error: '0' '0' 'Not Found' 'Not Found' ''

Categories

(Firefox for Android :: Accounts and Sync, defect)

Firefox 130
All
Android
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: jonalmeida, Unassigned)

References

()

Details

Steps to reproduce

  1. Use a local FxA server setup at localhost:3030.
  2. Ensure all adb ports are forwarded correctly. See adb-reverse.sh.
  3. Sign into or register an account. (Using an existing account is probably better.)
  4. Click on Manage account in the Fenix UI.
  5. Observe adb logcat.

Expected behaviour

The Custom Tab UI opens with the logged in account.

Actual behaviour

E  Error while running: getManageAccountURL
    mozilla.appservices.fxaclient.FxaException$Other: other error: Remote server error: '0' '0' 'Not Found' 'Not Found' ''
        at mozilla.appservices.fxaclient.FfiConverterTypeFxaError.read(fxa_client.kt:3318)
        at mozilla.appservices.fxaclient.FfiConverterTypeFxaError.read(fxa_client.kt:3307)
        at mozilla.appservices.fxaclient.FfiConverter$DefaultImpls.liftFromRustBuffer(fxa_client.kt:189)
        at mozilla.appservices.fxaclient.FfiConverterRustBuffer$DefaultImpls.liftFromRustBuffer(fxa_client.kt:201)
        at mozilla.appservices.fxaclient.FfiConverterTypeFxaError.liftFromRustBuffer(fxa_client.kt:3307)
        at mozilla.appservices.fxaclient.FfiConverterTypeFxaError.liftFromRustBuffer(fxa_client.kt:3307)
        at mozilla.appservices.fxaclient.FfiConverterRustBuffer$DefaultImpls.lift(fxa_client.kt:202)
        at mozilla.appservices.fxaclient.FfiConverterTypeFxaError.lift(fxa_client.kt:3307)
        at mozilla.appservices.fxaclient.FfiConverterTypeFxaError.lift(fxa_client.kt:3307)
        at mozilla.appservices.fxaclient.FxaException$ErrorHandler.lift(fxa_client.kt:3303)
        at mozilla.appservices.fxaclient.FxaException$ErrorHandler.lift(fxa_client.kt:3302)
        at mozilla.appservices.fxaclient.Fxa_clientKt.uniffiCheckCallStatus(fxa_client.kt:265)
        at mozilla.appservices.fxaclient.Fxa_clientKt.access$uniffiCheckCallStatus(fxa_client.kt:1)
        at mozilla.appservices.fxaclient.FirefoxAccount.getManageAccountUrl(fxa_client.kt:4942)
        at mozilla.appservices.fxaclient.FxaClient$getManageAccountURL$1.invoke(FxaClient.kt:250)
        at mozilla.appservices.fxaclient.FxaClient$getManageAccountURL$1.invoke(FxaClient.kt:249)
        at mozilla.appservices.fxaclient.FxaClient.withMetrics(FxaClient.kt:546)
        at mozilla.appservices.fxaclient.FxaClient.getManageAccountURL(FxaClient.kt:249)
        at mozilla.components.service.fxa.FirefoxAccount$getManageAccountURL$3.invokeSuspend(FirefoxAccount.kt:174)
        at mozilla.components.service.fxa.FirefoxAccount$getManageAccountURL$3.invoke(Unknown Source:8)
        at mozilla.components.service.fxa.FirefoxAccount$getManageAccountURL$3.invoke(Unknown Source:2)
        at mozilla.components.service.fxa.UtilsKt.handleFxaExceptions(Utils.kt:32)
        at mozilla.components.service.fxa.UtilsKt.handleFxaExceptions(Utils.kt:64)
        at mozilla.components.service.fxa.FirefoxAccount.getManageAccountURL(FirefoxAccount.kt:173)
        at org.mozilla.fenix.settings.account.AccountSettingsFragment$getClickListenerForManageAccount$1$1.invokeSuspend(AccountSettingsFragment.kt:379)
        at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
        at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:104)
        at android.os.Handler.handleCallback(Handler.java:942)
        at android.os.Handler.dispatchMessage(Handler.java:99)
        at android.os.Looper.loopOnce(Looper.java:201)
        at android.os.Looper.loop(Looper.java:288)
        at android.app.ActivityThread.main(ActivityThread.java:7872)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:936)

Device information

  • Firefox version: Debug in order to get the full logs needed.
  • Android device model: All
  • Android OS version: All

Any additional information?

n/a

Possibly related to bug 1907616 where there might be some parsing problems happening within the rust component, so we could see if there is some check we need to do at the browser chrome level to avoid these kind of exceptions once they are fixed.

See Also: → 1907616
Blocks: 1857021

With or without the react account page checked I see the same error.

I see this in the pm2 log output when I click the Managed account:

14|profile-static  | 2024-07-12T15:05:26: VERBOSE fxa-profile-server.server.static.hapi.request: {"request":"1720811126851:jalmeida-v3.local:53864:lyizvg6i:10017","timestamp":1720811126852,"tags":["handler","error"],"error":"Error: Not Found","channel":"internal"}

Hmm.. going directly to localhost:3030 in the regular tab works as I would have expected, but this is because the fully URL with all of these params:

http://localhost:3030/oauth/signin?showReactApp=true&deviceId=1c89faddc72242dbb0fabdc34245d935&flowBeginTime=1721057101473&flowId=f7f4ee86e090f3716a44812d4a56ab1220d9922f557db8e2e107c7ae720d43fa&action=email&response_type=code&entrypoint=settings-menu&client_id=a2270f727f45f648&scope=profile%2Bhttps%3A%2F%2Fidentity.mozilla.com%2Fapps%2Foldsync&state=vLckUe9A7fxM1UDGBKagDg&code_challenge_method=S256&code_challenge=l8dygmBmtE75QEvM9T7xWB1BL9kJOw4UHV4zvEyB84Q&access_type=offline&keys_jwk=eyJrdHkiOiJFQyIsImNydiI6IlAtMjU2IiwieCI6IlRhMm11Qk5oN2N1WnZqV3U0Z0Zvd3JGRnRESS1zSmJFbHhqaFhIdXBrM3ciLCJ5IjoibnAwdXl6XzRoY2pOZ19XWGZ1WFRlNEo1eEUzSFdhTzRTS0sxRWFPdncxMCJ9&context=oauth_webchannel_v1&forceExperiment=generalizedReactApp&forceExperimentGroup=react&email=tester%40gmail.com

I think we can say this is solved now. We needed to add more ports to forward and Dan has updated the port list here.

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.