Weird issue about permission guard in Angular after upgrade

[espindl]

I cannot tell if this is a bug or something else, but I think this is the right place to share and ask... Because there may be a small bug somewhere in the upgrade...

After upgrading to 10 (from 9.1) our Angular front-end started to act weird; if you refresh via browser in any URL, it was showing 403 and dropping to base URL. After searching and looking for the reason everywhere we tried and change the routings (that are using permission guard) from this:

data: {
        requiredPolicy: 'AbpIdentity.Roles.Create',
    },

to this old type:

data: {
      routes: {
        requiredPolicy: 'AbpIdentity.Roles.Create',
      },
    },

And refresh issue was solved. But knowing that the latter is an old format, we are wondering what might be the real issue and what might be a better solution?

[sumeyyeKurtulus]

Hello @espindl we have actually solved the refresh problem in this PR #24386.

Also, we have added support for redirect url in permission guard previously #24276 that may have caused another issue in your case. We will be looking into this. Until then, you can use this permission guard

abp/npm/ng-packs/packages/core/src/lib/guards/permission.guard.ts

Lines 51 to 81 in f3c9f43

	export const permissionGuard: CanActivateFn = (
	route: ActivatedRouteSnapshot,
	state: RouterStateSnapshot,
	) => {
	const router = inject(Router);
	const routesService = inject(RoutesService);
	const authService = inject(AuthService);
	const permissionService = inject(PermissionService);
	const httpErrorReporter = inject(HttpErrorReporterService);
	let { requiredPolicy } = route.data || {};
	if (!requiredPolicy) {
	const routeFound = findRoute(routesService, getRoutePath(router, state.url));
	requiredPolicy = routeFound?.requiredPolicy;
	}
	if (!requiredPolicy) {
	return of(true);
	}
	return permissionService.getGrantedPolicy$(requiredPolicy).pipe(
	filter(Boolean),
	take(1),
	tap(access => {
	if (!access && authService.isAuthenticated) {
	httpErrorReporter.reportError({ status: 403 } as HttpErrorResponse);
	}
	}),
	);
	};