In addition to the original issue, I have another question regarding how associated domains are expected to work when an application supports multiple environments. Our application has separate test and production environments, each with its own domain and corresponding AASA file. We have configured the associated domains entitlement in Xcode, and our Passkey SDK (Fotonation FIDO SDK) is initialized with the domain corresponding to the selected environment at runtime. We also have a runtime switch that allows us to change between the test and production environments. When the environment changes, the SDK is reinitialized with the appropriate domain. Could you clarify how iOS determines which AASA file to use in this scenario? Specifically: If both the test and production associated domains are included in the app's entitlements, does iOS fetch and cache the AASA file for both domains at installation time? If the application switches environments after installation, does iOS automatically use the AASA file corresponding to the domain passed to the SDK, or is there additional behavior we should be aware of? Is there any supported mechanism to force iOS to refresh or refetch the AASA file when switching between environments? Could having multiple associated domains (test and production) contribute to the intermittent. In our testing, we noticed that the issue appears more frequently after introducing support for both environments and switching between them. We would like to understand whether this could be related to how iOS caches or validates associated domains, or whether the behavior is expected or it is our front end issue.