Hi, have anybody succeeded in completing a recovery via "code" method using an API flow? When I submit the code, I don't get a session token for some reason 😞

Hi, what response do you get?

Hi! Here's the response after submitting the recovery code:

{
  "error": {
    "id": "browser_location_change_required",
    "code": 422,
    "status": "Unprocessable Entity",
    "reason": "In order to complete this flow please redirect the browser to: <http://localhost:3000/settings?flow=2bc236eb-78c3-4a60-a8b8-d5452ea26bb4>",
    "message": "browser location change required"
  },
  "redirect_browser_to": "<http://localhost:3000/settings?flow=2bc236eb-78c3-4a60-a8b8-d5452ea26bb4>"
}

Then I'm parsing the flow id from the redirect URL and fetching /self-service/settings/flows?id=2bc236eb-78c3-4a60-a8b8-d5452ea26bb4 :

{
  "error": {
    "code": 401,
    "status": "Unauthorized",
    "reason": "A valid Ory Session Cookie or Ory Session Token is missing.",
    "message": "The request could not be authorized"
  }
}

I don’t hink we send a token with that response, that’s correct. You could try and send the cookie (from the

Set-Cookie

header) along as if you’re a browser application, but it’s getting really hacky at this point. Sorry that the recovery flow is not working on for native yet.

I see... Unfortunately we have a native application :<

We have it on the roadmap. Do you have any way to use the browser in the meantime?

Good to hear! That's a little inconvenient, but yeah, we can use the browser until it's ready.

Hi, We are also interested in this topic. Do you have any ETA for the native app support, or any suggestion for workaround?

No concrete ETA yet. cc @fast-lunch-54279 As a workaround, you can use a browser, even if your main application is running natively. But that’s obviously not always possible.