Description

Fixes #24438
This PR fixes the issue where permissionGuard returns a 403 error and redirects to the base URL when refreshing a page that uses the new data: { requiredPolicy: '...' } format.

Root Cause

The permissionGuard was using take(1) which immediately consumed the first value from the BehaviorSubject in ConfigStateService. On page refresh, this initial value was an empty {} object before the application configuration API response arrived, causing the permission check to fail.

Solution

Added a filter operator to wait for grantedPolicies to be loaded before performing the permission check:

return configStateService.getAll$().pipe(
  filter(config => !!config?.auth?.grantedPolicies),
  take(1),
  switchMap(() => permissionService.getGrantedPolicy$(requiredPolicy)),
  take(1),
  map(access => { ... })
);

How to test it?

you have to change branch issue-24438-test on abp. (because i created test permission and test page)
you have to run dev-app on abp repository

First, try going to localhost:4200/test without assigning yourself the "test" role.
Then, assign yourself the "test" role and try going to the page again.