We understand the issue you mentioned requires configuration on our end, and we are currently working on it. If proceeding with the service replacement does not align with your needs, please let us know.
If it aligns with your approach, you can temporarily replace the LocalStorageListenerService with your own service to manage this part.
//app.module.ts
@NgModule({
...
providers: [
{
provide: LocalStorageListenerService,
useValue: MyLocalStorageListenerService,
},
...
],
...
})
export class AppModule {}
//my-local-storage-listener.service.ts
@Injectable({
providedIn: 'root',
})
export class MyLocalStorageListenerService {}
Hello, you can upgrade your packages to the latest version on the angular side. In the meantime, you should be able to continue using .net8. If you encounter any problem, I can assist you further.
This fix covers the old cli for the time being. You can use this command to install/update the old cli abp install-old-cli --version 9.0.4 . Then you should be able to use the command as abp-old or with --old flag.
Hi, I apologize for the confusion regarding Angular ui. I’ve removed my answer, and my teammate will assist you with this moving forward.
We have also checked the list that you have provided, the problems should have been solved by now. If you face any other issue, I can assist you further.
Hello, may I ask whether your issue is still active?
Hello, We’ve updated the Expo SDK to version 52, which now requires TypeScript configuration. Additionally, this version will include React Navigation for enhanced functionality.
You find the solution in https://abp.io/support/questions/7942/Angular-layered-application-seems-broken-in-83 I believe.
We have fixed the related problem within this question previously.
We are really sorry for the delay. We are working on a solution to fix this issue and appreciate your understanding while we are sorting it out.
