lack0fsystem
@lack0fsystem
Hey there @dwr.eth could we start a conversation here about signers on /farcaster ? Everytime I try to log in the /warpcast app using my seed phrase I receive this error: { "error": "\n######################################################################\n\nHandledFetchError\n...message: getOnboardingState 403 - No active Warpcast signer exists for FID undefined\n...name: Farcaster API Error\n...absoluteUrl: https://client.warpcast.com/v2/onboarding-state\n...body: undefined\n...endpointName: getOnboardingState\n...hasTimedOut: false\n...isNetworkError: false\n...method: GET\n...relativeUrl: /v2/onboarding-state\n...resolvedTimeout: 20000\n...response: [object Object]\n...responseData: [object Object]\n...status: 403\n...timeout: undefined\n\n######################################################################\n", "localTimestamp": 1721935408868, "unauthed": true } I assumed that the /warpcast client isn't a valid signer for me so is there a way to turn it into a signer atm or soon?
1 reply
0 recast
0 reaction
lack0fsystem
@lack0fsystem
please ignore the farquest URL: this is the warpcast error: { "error": "\n######################################################################\n\nHandledFetchError\n...message: getOnboardingState 403 - No active Warpcast signer exists for FID undefined\n...name: Farcaster API Error\n...absoluteUrl: https://client.warpcast.com/v2/onboarding-state\n...body: undefined\n...endpointName: getOnboardingState\n...hasTimedOut: false\n...isNetworkError: false\n...method: GET\n...relativeUrl: /v2/onboarding-state\n...resolvedTimeout: 20000\n...response: [object Object]\n...responseData: [object Object]\n...status: 403\n...timeout: undefined\n\n######################################################################\n", "localTimestamp": 1720224810639, "unauthed": true }
0 reply
0 recast
0 reaction