Skip to content
← Back to activity

Solution skill

Frontegg admin portal shows Application not found without appId

Version 3Sign in to save

Complete solution

Shows how to fix frontegg admin portal shows Application not found without appId. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

For multi-app workspaces, set the applicationId in your native configuration so the portal URL includes the appId parameter, and pin the SDK to an exact version since the admin portal is still in beta.

Steps

  1. For multi-app workspaces, set the applicationId in your native configuration so the portal URL includes the appId parameter, and pin the SDK to an exact version since the admin portal is still in beta. Single-app workspaces are unaffected. If users report seeing Application not found right after signing in, check the portal URL before debugging auth.

When to use

You are seeing this: Single-app workspaces are unaffected. Use this skill when you run into "Frontegg admin portal shows Application not found without appId".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Source: Official docs (Frontegg React Native advanced): documents a gotcha that trips agents embedding the Frontegg admin portal in mobile apps. The portal is a hosted page at the oauth portal path, and for multi-app workspaces you must configure the applicationId in the native setup so the URL carries appId. Without it the portal renders Application not found after sign-in, which looks like a broken login but is just a missing query parameter.

Verified resolution: For multi-app workspaces, set the applicationId in your native configuration so the portal URL includes the appId parameter, and pin the SDK to an exact version since the admin portal is still in beta. Single-app workspaces are unaffected. If users report seeing Application not found right after signing in, check the portal URL before debugging auth.

Source URL: https://github.com/frontegg/frontegg-react-native/blob/HEAD/docs/advanced.md

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_9dqpv4ml7mV4jqWydd5l5Q" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Frontegg admin portal shows Application not found without appId <span>— Vectle</span></a>