abpframework/abp · error · CliUsageException
Please login with your account.
Error message
Please login with your account.
What it means
Thrown by SuiteCommand.ExecuteAsync when _authService.GetLoginInfoAsync() returns a login info whose Organization property is null or empty. ABP Suite is a commercial product requiring authentication with a valid ABP account tied to an organization with an active license. This check is skipped in DEBUG builds (#if !DEBUG), so it only fires in release/production CLI builds.
Source
Thrown at framework/src/Volo.Abp.Cli.Core/Volo/Abp/Cli/Commands/SuiteCommand.cs:64
SuiteAppSettingsService suiteAppSettingsService)
{
CmdHelper = cmdHelper;
_nuGetIndexUrlService = nuGetIndexUrlService;
_packageVersionCheckerService = packageVersionCheckerService;
_authService = authService;
_cliHttpClientFactory = cliHttpClientFactory;
_suiteAppSettingsService = suiteAppSettingsService;
Logger = NullLogger<SuiteCommand>.Instance;
}
public async Task ExecuteAsync(CommandLineArgs commandLineArgs)
{
#if !DEBUG
var loginInfo = await _authService.GetLoginInfoAsync();
if (string.IsNullOrEmpty(loginInfo?.Organization))
{
throw new CliUsageException("Please login with your account.");
}
#endif
var operationType = NamespaceHelper.NormalizeNamespace(commandLineArgs.Target);
var preview = commandLineArgs.Options.ContainsKey(Options.Preview.Short) ||
commandLineArgs.Options.ContainsKey(Options.Preview.Long);
var version = commandLineArgs.Options.GetOrNull(Options.Version.Short, Options.Version.Long);
var currentSuiteVersionAsString = GetCurrentSuiteVersion();
switch (operationType)
{
case "":
case null:
await InstallSuiteIfNotInstalledAsync(currentSuiteVersionAsString);
_abpSuitePort = await _suiteAppSettingsService.GetSuitePortAsync(currentSuiteVersionAsString);
RunSuite(commandLineArgs);View on GitHub (pinned to 7ed43b1931)
Solutions
- Run 'abp login' and enter your ABP Commercial account credentials
- Verify your account has an active ABP Commercial license at abp.io > Account > Licenses
- If already logged in but still failing, run 'abp logout' then 'abp login' again to refresh the token
- Check that the organization associated with your account has Suite enabled
Defensive patterns
Strategy: validation
Validate before calling
// Pre-check authentication before running Suite commands
#if !DEBUG
var loginInfo = await _authService.GetLoginInfoAsync();
if (string.IsNullOrEmpty(loginInfo?.Organization))
{
Console.Error.WriteLine("Not logged in. Run 'abp login' first.");
return;
}
#endif Try / catch
try
{
await suiteCommand.ExecuteAsync(commandLineArgs);
}
catch (CliUsageException ex) when (ex.Message.Contains("Please login"))
{
Console.Error.WriteLine("Authentication required. Run: abp login");
Environment.Exit(1);
} Prevention
- Run 'abp login' at the start of each development session
- Verify your ABP Commercial license is active before using Suite
- If sessions expire frequently, script 'abp login' into your environment setup
- Check that your account is associated with an organization in the ABP.IO portal
When it happens
Trigger: Running any 'abp suite' subcommand (install, update, remove, generate, or bare launch) while the CLI authentication state has no organization. This means either the user never ran 'abp login', the session expired, or the account has no commercial license organization associated.
Common situations: First-time use without 'abp login', expired session token (tokens have a lifetime), account without an active ABP Commercial license, using a community/free account that lacks Suite access.
Related errors
- Please log in with your account!
- ERROR: Remote server returns '{response.StatusCode}'
- Username name is missing!
- Password is missing!
- No active license found.
AI-assisted analysis of abpframework/abp@7ed43b1931 (2026-08-13).
Data as JSON: /api/errors/f49e46bdc24f085d.
Report an issue: GitHub.