Thank you for sharing the output from Expo-doctor. I would like to assure you that the concerns mentioned, such as validation warnings and package compatibility, are being addressed in upcoming releases.
These issues should not disrupt the core functionality of the app directly in the current version, but we recommend keeping an eye out for the next updates, which will resolve these points and improve overall compatibility.
Thank you for providing details, and bringing this to our attention. We are currently updating the templates, and these issues will be resolved in the next studio release. I appreciate your patience, and I have processed a refund for your ticket.
Regarding the antiforgery token issue, as a temporary solution, I recommend overriding the service like this. You can also apply the same logic in your app.component.ts if that works better for you.
//app.module.ts
@NgModule({
...
providers: [
{
provide: LocalStorageListenerService,
useValue: MyLocalStorageListenerService,
},
...
],
...
})
export class AppModule {}
//my-local-storage-listener.service.ts
import { DOCUMENT } from '@angular/common';
import { inject, Injectable } from '@angular/core';
@Injectable({
providedIn: 'root',
})
export class MyLocalStorageListenerService {
window = inject(DOCUMENT).defaultView;
constructor() {
this.window.addEventListener('storage', event => {
if (event.key !== 'access_token') {
return;
}
const tokenRemoved = event.newValue === null;
const tokenAdded = event.oldValue === null && event.newValue !== null;
if (tokenRemoved || tokenAdded) {
location.assign('/');
}
});
}
}
Hello, I’m having trouble understanding your steps. Could you please clarify how you created and integrated the modules into your app? If possible, sharing your package.json file would also help in identifying the issue. Thanks!
Hello, you can use this key eThemeLeptonXComponents.MobileNavbarSettings to manage the mobile navbar settings.
May I also ask how you have added the FAQ component that would result in a scroll problem?
Hello, thank you for bringing this to our attention. This issue will be resolved in the next release, and I’ll be processing a refund for your ticket as well.
Hello again, have you had a chance to try upgrading? If so, did it address your requirements and resolve the issue?
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.
