Hello! I've implemented a similar Angular application and applied the same modifications to the login button, but I’m unable to reproduce the issue on my end. To assist you more effectively, could you please share a minimal, reproducible example?
That way, I can help debug the issue more precisely.
Hello, I will check and get back to you soon. Thank you for your patience and cooperation.
Hello! You're right—the generated proxy service is reflecting the lookup properties based on the navigation fields, and in this case, it's duplicating them due to both pointing to the same model (Grade).
This behavior comes from the controller generation pattern, which typically results in something like:
[HttpGet]
[Route("entity-one-lookup")]
public virtual Task<PagedResultDto<LookupDto<Guid>>> GetEntityOneLookupAsync(LookupRequestDto input)
{
return _entityThreesAppService.GetEntityOneLookupAsync(input);
}
The duplication issue is acknowledged and we're planning to address it in a future release. For now, the manual removal workaround is the best option—though we understand it's not ideal, especially when files are regenerated.
If you believe the issue stems more from the controller generation logic itself, feel free to share more details and I’d be happy to look into it further with you.
Yes, you can safely migrate your Angular project to use the standalone structure in Angular 19.
The components <abp-loader-bar> and <abp-dynamic-layout> are not standalone; they are declared and exported by the ThemeSharedModule. Therefore, you shouldn’t encounter issues related to them during the migration.
Let us know if you need any further help.
I'm glad to hear the workaround resolved the issue.
Hello again, to clarify, you'll need to replace the .suite folder in the root of your Angular project (same level as projects, node_modules, etc.).
Thank you for giving mode details on that. However, I cannot produce the same problem on my end. Could you specify which package manager you use? You can also create a minimal reproducible example and send it to this address sumeyye.kurtulus@volosoft.com, so that I can assist you further.
Hello, it currently works as expected as you have mentioned. However, if encryption is required, you’ll need to apply a workaround until we release an official fix for that.
In the meantime, you can override the related service just to skip the error. Here’s a suggested approach:
// new-remember-me.service.ts
export class NewRememberMeService extends RememberMeService {
readonly #rememberMe = 'remember_me';
override getFromToken(accessToken: string): boolean {
const tokenBody = accessToken.split('.')[1].replace(/-/g, '+').replace(/_/g, '/');
try {
const decoded = JSON.parse(atob(tokenBody));
return Boolean(decoded[this.#rememberMe]);
} catch {
return false;
}
}
}
You need to add this provider to the app.module.ts :
{ provide: RememberMeService, useClass: NewRememberMeService },
We appreciate your patience and cooperation while we work on a permanent solution.
Thank you for the update. Since the issue persists, could you please share your package.json file so we can verify the package versions?
Could you also try deleting temporary files such as node_modules,yarn-lock or package-lock.json and re-install dependencies depending on your package manager.
Thanks for the detailed feedback and for sharing the steps you followed—it is much appreciated.
To clarify: the React Native template is intended primarily for mobile platforms, and while Web support via Expo is possible, it is not officially supported or prioritized at the moment. We understand that Web can be useful for development workflows, especially in CRUD scenarios, but it falls outside the main scope of the template.
The points you raised around DBMigrator config, local IP usage, and HTTP access are all valid, and we’ll look at improving the docs accordingly.
If you encounter specific issues with the dev build or something clearly tied to the template, feel free to raise them in a separate thread so we can address them in a focused way.
