Purpose

This pull request updates the FlowMetaProvider component in FlowMetaProvider.tsx to improve how it handles the initialization state of the Asgardeo authentication context. The main goal is to ensure that metadata fetching waits until Asgardeo is fully initialized, preventing unnecessary UI flickers and supporting flows that may not have an applicationId.

Improvements to initialization and metadata fetching logic:

• The isInitialized property from useAsgardeo is now used in addition to applicationId to determine when to fetch flow metadata, ensuring that fetching only occurs after Asgardeo is ready. This prevents design flicker and supports flows without an applicationId (e.g., AcceptInvite). [1] [2]
• The effect dependencies for fetching metadata have been updated to include isInitialized, ensuring the effect reacts to changes in initialization state.

Related Issues

• N/A

Related PRs

• Refactor FlowMetaProvider to prevent duplicate fetches during re-mounts #462

Checklist

• Followed the CONTRIBUTING guidelines.
• Manual test round performed and verified.
• Documentation provided. (Add links if there are any)
• Unit tests provided. (Add links if there are any)

Security checks

• Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines?
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets?