#Developers Edition7 debatiendo

Hi, That message means the token request did not land on an org where this consumer is installed. Enabled on the app record is not the same thing. Check Distribution State in External Client App Manager. For a login in this same Developer Edition, it needs to be Local. A Packaged app is not usable for OAuth in the org where you created it, even when the status says Enabled. Flipping it back to Local often does not re-register the consumer. Create a new app and leave it Local from the start. The other usual cause is the CLI audience. login.salesforce.com is not a valid JWT audience anymore, and the CLI reports that as "not installed". Pass --instance-url with this org's My Domain URL from Setup, not https://login.salesforce.com. On the app, open Policies and set permitted users to Admin approved users are pre-authorized, then add the profile of the user you pass as --username. On Settings, keep JWT Bearer Flow on, with your certificate, and include the api and refresh_token scopes. Copy the consumer key again after you save, and wait a few minutes before you retry. For the 2GP work, enable Dev Hub in this org and log in as a user in that Dev Hub. The app has to live in the same org as that username.

Hi CM Seb, 

Two separate root causes here, both well-documented, and both explain your exact symptom (works as admin in Debug, silently does nothing for guest users on the live site). 

1. Record creation not happening: most likely the flow isn't actually enabled for the Guest User profile, even if it "worked" in Debug. 

Profile-level object permissions (Read/Create on Application) are necessary but not sufficient. You also need to explicitly grant the flow itself to guest users, this is a separate step from object permissions: 

   - Experience Builder > Settings (gear icon) > General tab > confirm "Guest users can see and interact with the site without logging in" is checked, then click the guest user profile link. 

   - Under Enabled Flow Access, click Edit, and confirm your Transitional Coach Application flow is moved into the Enabled Flows column (not just present in the Available list). 

   Reference:

   This is the single most common cause of "works when I test it logged in, does nothing for actual guest visitors", the flow needs this explicit enablement separate from object CRUD permissions. 

2. Emails not sending: this is a hard platform restriction, not a config you're missing. 

As of Spring '23, Salesforce permanently removed the "Send Email" system permission from the Guest User profile across ALL orgs, and since permission sets can't be assigned to guest users either, there is no way to grant this back declaratively. This is intentional (anti-spam/abuse prevention for public-facing guest contexts), not a bug. 

   Workaround: don't send the email directly from the guest-context flow. Instead: 

   - Have the guest flow create the Application record only. 

   - Use a separate Record-Triggered Flow on the Application object (After Save), running as an internal/system context, not the guest user, to send the confirmation email. Since this second flow runs on the object trigger rather than in the guest user's session, it isn't restricted by the Guest User "Send Email" removal. 

Given your record creation is also failing (not just email), I'd fix #1 first, that's likely blocking everything, and once records start getting created successfully, wiring up a Record-Triggered Flow for the email (per #2) will resolve the email gap cleanly without depending on guest user email permissions at all.

Log out from every account then just login with a single account and then open your simulator.

If it still not work, then from browser switch to lightning experience, then open developer console and switch to mobile view. Now, remove everything after 'one/one.app' from URL and hit enter. The page will load as it is in Salesforce1.

Let me know if it still not works.

Thanks

Ajeet