api_url Override Not Reflected in Magic Link for Android Emulator

[tulipekoni]

I'm running Supabase locally on an Android emulator, which requires using 10.0.2.2 instead of 127.0.0.1. I have updated the config.toml file accordingly:

[studio]
enabled = true
# Port to use for Supabase Studio.
port = 54323
# External URL of the API server that frontend connects to.
api_url = "http://10.0.2.2"
# OpenAI API Key to use for Supabase AI in the Supabase Studio.
openai_api_key = "env(OPENAI_API_KEY)"

However, after running supabase start, the logs still show:

API URL: http://127.0.0.1:54321

Even though API requests from the Android emulator correctly resolve to http://10.0.2.2:54321, I face an issue with the magic link authentication:

• The magic link is correctly sent and arrives at Bitbucket.
• The issue is that the magic link contains http://127.0.0.1:54321/auth/v1/verify?token={xxx}=magiclink&redirect_to=schema:// instead of using http://10.0.2.2:54321.
• Since 127.0.0.1 does not work inside the emulator, the verification request fails, causing the login process to break.

Expected Behavior

The magic link should use http://10.0.2.2:54321 as defined in config.toml instead of http://127.0.0.1:54321.

Steps to Reproduce

1. Update config.toml to set api_url = "http://10.0.2.2".
2. Run supabase start.
3. Try to authenticate using a magic link on an Android emulator.
4. Observe that the generated magic link contains 127.0.0.1 instead of 10.0.2.2.

Possible Causes

Could it be that api_url in config.toml is not applied to the magic link generation? Is there another setting that controls this URL?

Any insights on how to properly override this would be appreciated!