The error "Identity provider configurations missing" in OutSystems 11 typically occurs when authentication settings or configurations are not properly defined in your app. If you're launching the app via an Android Studio Emulator, here's how to resolve it:

Steps to Fix "Identity Provider Configurations Missing"

1. Check the Authentication Method:

   • Go to the Service Center in OutSystems.
   • Navigate to Administration > Authentication.
   • Verify the authentication method used by your environment (e.g., LDAP, SAML, Active Directory, etc.).
   • Ensure that the necessary configurations for the chosen authentication provider are correctly set up.

2. Verify Identity Provider in Your App:

   • Open the OutSystems application in Service Studio.
   • Check if the app is configured to use an external identity provider (e.g., SAML, Azure AD, etc.).
   • Go to the Module Settings of your app:
     • Click on Module in the toolbar.
     • Select Authentication.
   • Confirm that the authentication settings match your environment's configuration.

3. Set the Identity Provider in the Emulator:

   • If your app uses external authentication, ensure the emulator has internet access to connect to the identity provider.
   • Verify that the emulator is properly configured with the necessary certificates if your identity provider requires HTTPS.

4. Test the Application Locally Without Authentication:

   • Temporarily disable authentication for testing purposes:
     • In Service Studio, go to Module > Authentication.
     • Set the Authentication to None.
   • Republish the app and test it on the emulator.

5. Verify API Key or Mobile Configuration:

   • If your app integrates with identity services through APIs, ensure the necessary API keys or credentials are configured in the Mobile App Settings.

6. Ensure Proper Build Configuration:

   • Make sure you have correctly generated and downloaded the mobile app package:
     • Go to the Environment Settings in the OutSystems environment.
     • Build the app for Android and ensure it includes all configurations.

7. Check for Emulator-Specific Issues:

   • Verify that the Android Emulator has Google Play Services installed (if required for authentication).
   • Ensure the emulator is running the same API level as supported by your OutSystems mobile app.