Solved by using --no-launch-profile
For some reason even though the environment was set it was still using the launch profiles
hi
The device code flow is used to authenticate/generate tokens for a
device. e.g., ABP CLI supports this flow. You can try runabp login --device.
- it will generate a user code.
- open the abpio website. sign in and enter the user code
- abp will get an access token.
The source code : https://github.com/abpframework/abp/pull/10857
Yes that is working, I have already tried that, and also implemented the custom grant as well, both are working well in a test abp project. But I am just trying to understand how the default flow works under the hood for authorizing the device, so whatever happens in the /connect/verify POST endpoint, but maybe in my own appservice for example. Or maybe I want to authorize someone else's device code that was received from /device.
I had to remove this AuditLoggin.AuditLogs.SettingManagement as well, any idea how this came to be?
Features Table
But that's not even related to the problem. And also it failed because build failed due to errors.
Anyways a restart solved the issue.
New sample project, new entity, still got the same issue.
Hi followed all your steps for a clean install, only difference is I installed version 7.1 for CLI and SUITE.
Still getting same original error
Never mind using the file path instead of the folder path solved it.
lost all my added projects, while trying to add it again
The difference between using the proxy is just a connection string in terms of what ABP uses. So not sure why the duplication only on proxy, but willl investigate.
Thanks for your help, as it's not a problem with ABP, closing this now.
