Switch Tenant on newly generated projects doesn't work #7294 | Support

arodriguez created 6 months ago

ABP Framework version: v8.1.3
UI Type: Blazor Server (Lepton x)
Database System: EF Core (SQL Server.)
Tiered (for MVC) or Auth Server Separated (for Angular): tested in both cases: yes/no
Exception message and full stack trace: no error throwns
Steps to reproduce the issue: The switch tenant button on the login interface doesn't work, it does nothing. The project was generated with version 8.1.3 of abp suite.

7 Answer(s)

0

enisn created 6 months ago
Support Team .NET Developer

Do you have any logs on the running process console or in the browser console?

Also, make sure there isn't any problem while installing client-side libraries. To make sure, you can try running abp install-libs command once again in the blazor project folder.
0

arodriguez created 6 months ago

Until now i guess i'd never had the necessity to run that command over clean directory, after recently updating the cli and the suite. So, please, where can a find a command sample to this invocation of install-libs?
0

enisn created 6 months ago
Support Team .NET Developer

Firstly, I recommend checking logs to find any error there. Check both browser console and application logs.

Until now i guess i'd never had the necessity to run that command over clean directory, after recently updating the cli and the suite. So, please, where can a find a command sample to this invocation of install-libs?

Yes, you don't need to run any command normally, but there can be some temporary network problem or something like that. some of packages might be missing and couldn't be downloaded by package manager. In case of a missing script, you can navigate to your project directory and open terminal in that directory and execute abp install-libs in there.
0

arodriguez created 6 months ago

Well, i did those steps last night and stills not working. I can't keep loosing my time with this issue, when obviously the problem is with the suite. Is the first time i generated project with the suite and presents this problem; it's suppose it should work.

A question, the current RC version also have this problem?
0

enisn created 6 months ago
Support Team .NET Developer

Sadly I can not reproduce this problem, please provide us logs to understand problem and help you. Check console logs or find Logs/logs.txt under your application. And also, it might be a JavasScript problem, please check browser logs too and provide us
0

arodriguez created 6 months ago

I tried again to run the command abp install-libs, It happens that, it throws an error. Here is the command console:

Microsoft Windows [Version 10.0.19045.4412] (c) Microsoft Corporation. All rights reserved.

D:\codigoEjemplo\AbpV8NonLayered>abp install-libs ABP CLI 8.1.3 Found 2 projects. D:\codigoEjemplo\AbpV8NonLayered\src\AbpV8NonLayered.Blazor D:\codigoEjemplo\AbpV8NonLayered\src\AbpV8NonLayered.Web.Public Running Yarn on D:\codigoEjemplo\AbpV8NonLayered\src\AbpV8NonLayered.Blazor yarn install v1.22.19 info No lockfile found. warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json. [1/4] Resolving packages... warning @volo/abp.aspnetcore.mvc.ui.theme.leptonx > @volo/abp.aspnetcore.mvc.ui.theme.commercial > @abp/aspnetcore.mvc.ui.theme.shared > @abp/aspnetcore.mvc.ui > glob@7.2.3: Glob versions prior to v9 are no longer supported warning @volo/abp.aspnetcore.mvc.ui.theme.leptonx > @volo/abp.aspnetcore.mvc.ui.theme.commercial > @abp/aspnetcore.mvc.ui.theme.shared > @abp/aspnetcore.mvc.ui > glob > inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. warning @volo/abp.aspnetcore.mvc.ui.theme.leptonx > @volo/abp.aspnetcore.mvc.ui.theme.commercial > @abp/aspnetcore.mvc.ui.theme.shared > @abp/aspnetcore.mvc.ui > gulp > glob-watcher > chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies warning @volo/abp.aspnetcore.mvc.ui.theme.leptonx > @volo/abp.aspnetcore.mvc.ui.theme.commercial > @abp/aspnetcore.mvc.ui.theme.shared > @abp/aspnetcore.mvc.ui > gulp > vinyl-fs > glob-stream > glob@7.2.3: Glob versions prior to v9 are no longer supported warning @volo/abp.aspnetcore.mvc.ui.theme.leptonx > @volo/abp.aspnetcore.mvc.ui.theme.commercial > @abp/aspnetcore.mvc.ui.theme.shared > @abp/aspnetcore.mvc.ui > gulp > glob-watcher > chokidar > fsevents@1.2.13: The v1 package contains DANGEROUS / INSECURE binaries. Upgrade to safe fsevents v2 warning @volo/abp.aspnetcore.mvc.ui.theme.leptonx > @volo/abp.aspnetcore.mvc.ui.theme.commercial > @abp/aspnetcore.mvc.ui.theme.shared > @abp/aspnetcore.mvc.ui > gulp > glob-watcher > anymatch > micromatch > snapdragon > source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated warning @volo/abp.aspnetcore.mvc.ui.theme.leptonx > @volo/abp.aspnetcore.mvc.ui.theme.commercial > @abp/aspnetcore.mvc.ui.theme.shared > @abp/aspnetcore.mvc.ui > gulp > vinyl-fs > glob-stream > unique-stream > through2-filter@3.1.0: this package has been deprecated for breaking semver major warning @volo/abp.aspnetcore.mvc.ui.theme.leptonx > @volo/abp.aspnetcore.mvc.ui.theme.commercial > @abp/aspnetcore.mvc.ui.theme.shared > @abp/aspnetcore.mvc.ui > gulp > glob-watcher > anymatch > micromatch > snapdragon > source-map-resolve > resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated warning @volo/abp.aspnetcore.mvc.ui.theme.leptonx > @volo/abp.aspnetcore.mvc.ui.theme.commercial > @abp/aspnetcore.mvc.ui.theme.shared > @abp/aspnetcore.mvc.ui > gulp > glob-watcher > anymatch > micromatch > snapdragon > source-map-resolve > source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated warning @volo/abp.aspnetcore.mvc.ui.theme.leptonx > @volo/abp.aspnetcore.mvc.ui.theme.commercial > @abp/aspnetcore.mvc.ui.theme.shared > @abp/aspnetcore.mvc.ui > gulp > glob-watcher > anymatch > micromatch > snapdragon > source-map-resolve > urix@0.1.0: Please see https://github.com/lydell/urix#deprecated warning @volo/language-management > @abp/flag-icon-css > flag-icon-css@4.1.7: The project has been renamed to flag-icons [2/4] Fetching packages... error p-retry@6.2.0: The engine "node" is incompatible with this module. Expected version ">=16.17". Got "14.4.0" error Found incompatible module. info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command. Running Yarn on D:\codigoEjemplo\AbpV8NonLayered\src\AbpV8NonLayered.Web.Public yarn install v1.22.19 [1/4] Resolving packages... success Already up-to-date. Done in 0.31s.

D:\codigoEjemplo\AbpV8NonLayered>
0

arodriguez created 6 months ago

After upgrading node to latest release version (22.2), after running the app install-libs command, switch tenant works properly. Note that, on the command console, during this upgrade process one message throws in red that alerts me:

ABP CLI 8.1.3 Found 2 projects. D:\codigoEjemplo\AbpV8NonLayered\src\AbpV8NonLayered.Blazor D:\codigoEjemplo\AbpV8NonLayered\src\AbpV8NonLayered.Web.Public Running Yarn on D:\codigoEjemplo\AbpV8NonLayered\src\AbpV8NonLayered.Blazor yarn install v1.22.19 info No lockfile found. warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json. [1/4] Resolving packages... ⠁ (node:14660) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead. (Use node --trace-deprecation ... to show where the warning was created)

I tested again the generation of a new test project, to check if with node up-to-date, the suite delivers to me the right solution template. It works as expected. So this tell me one thing. We don't generate new projects frequently. The instructions we have to update the cli and the suite only includes those explicit steps. Apparently there's need to check one more: update node. BUT, what if we update and results that with the latest version for "x" or "y" it doesn't work?.

I recommend that the documentation of the abp suite installation process includes this dependency explicitly, and the expected version of it.

Thanks for your help, and sorry for the inconvenience.

Have an answer to this question? Log in and write your answer.