How to Change The Domain Name for Existing BuddyBoss App

Introduction

Changing the domain name for your BuddyBoss App allows you to update your app’s connection settings without unpublishing the old version.

This process reconnects your BuddyBoss App license to a new domain, ensures the mobile app communicates with the correct backend, and keeps all app features working seamlessly after migration.

Reconnect Your BuddyBoss App License to the New Domain

1. Log in to your WordPress Dashboard.
   
2. Go to BuddyBoss App > Configure.
   
3. Update the Domain Name field to reflect your new domain (e.g., app.yourdomain.com).
   
4. Click Save Settings.
   

Note: Confirm that your new domain is fully active and has a valid SSL certificate before saving.

Reconfigure Your iOS App

1. Navigate to BuddyBoss App > Configure > iOS Settings.
   
2. Enter your new domain in the appropriate field.
   
3. Review and update any related settings affected by the domain change (e.g., redirect URLs, API endpoints).
   
4. Click Save Settings.
   

Reconfigure Your Android App

1. Go to BuddyBoss App > Configure > Android Settings.
   
2. Update the Domain Name field with your new domain.
   
3. Adjust other configuration details if needed (e.g., REST API endpoints, app links).
   
4. Click Save Settings.
   

Build and Release an Updated App Version

After updating your domain in both iOS and Android configurations:

1. Generate a new build of your app.
   
2. Publish it to the App Store and Google Play Store.
   

This ensures that your mobile app communicates with your new backend domain. Users running older versions will not be able to connect correctly until they update.

Enable the Minimum Build Version

Once your updated app is live:

1. Go to BuddyBoss App > Configure.
   
2. Enable Minimum Build Version.
   
3. Set it to the new version number that includes your domain update.
   
4. Click Save Settings.
   

This feature forces users to update to the latest app version, ensuring compatibility with your new domain.

Test Your Configuration

Before and after releasing the new build:

• Verify that your app connects properly to the new domain.
  
• Check user authentication, API requests, and media loading.
  
• If issues occur, review your DNS, SSL, and REST API/JWT settings.
  

Always test on both iOS and Android devices using real accounts to confirm smooth connectivity.

Note: You do not need to unpublish your existing app. Simply update the configuration, rebuild, and reconnect your BuddyBoss App license to your new domain.
All user data and App Store listings remain intact.

Troubleshooting and FAQs

Q: What changes or risks should I expect when switching to a new domain?

A: When changing your primary domain, both your BuddyBoss Web and App will need to reestablish their connections to the new domain. You may experience temporary downtime or authentication errors if configurations are not updated properly. Always test the new domain setup before making it live to ensure seamless connectivity and avoid login or data-sync issues.

Q: Which BuddyBoss App settings need to be updated after a domain change?

A: You’ll need to update the following configurations inside BuddyBoss App > Configure:

• iOS and Android app domain fields
  
• REST API / JWT Authentication URLs
  
• Whitelisted domain entries (if applicable)
  

After saving your changes, you’ll need to generate and publish a new build of your mobile app with the updated domain configuration. This ensures users connect to the correct site backend.

Q: Will this affect our existing App Store or Play Store listings?

No, your app listings remain active. However, if your Privacy Policy URL, support links, or screenshots include your old domain, you’ll need to update those in your Apple App Store and Google Play Console settings.

Your bundle ID, certificates, and provisioning profiles remain the same and do not require updates unless you’re changing your app’s package name or publisher.

A: How do we update iOS Universal Links and Android App Links?

You’ll need to upload new configuration files to your new domain:

• apple-app-site-association > for iOS Universal Links
  
• assetlinks.json > for Android App Links

These files should list your new domain and all relevant paths that need to open directly in the app. This ensures in-app routing and deep links continue to work properly after the domain transition.

Q: What do we need to update for authentication and social logins?

A: If you’re using OAuth, Social Login, or JWT/REST API authentication:

• Update your redirect URIs and allowed domain lists to include the new domain.
  
• Check your BuddyBoss Platform and any third-party integrations to ensure authentication callbacks point to the correct URLs.

Failing to update these may result in login errors or failed token exchanges.

Q: Do we need to change anything for push notifications?

A: No changes are typically needed for APNs (Apple) or FCM (Google) keys, certificates, or project IDs, since these are tied to your app, not your domain.

However, if your push notification payloads include URLs (such as links to posts or groups), make sure those URLs now point to the new domain.

Q: Are there any CORS, CDN, or asset issues to watch out for?

A: Yes, you may encounter CORS (Cross-Origin Resource Sharing) or mixed-content warnings if fonts, images, or scripts are still being served from your old domain or unsecured links (HTTP instead of HTTPS).

To avoid issues:

• Ensure all assets use HTTPS and the correct new domain.
  
• Update CDN and cache configurations to point to the new URLs.
  
• Clear all caches and verify that in-app assets render correctly.
  

Q: Do you have a recommended step-by-step guide for switching domains?

A: Yes! Here’s a recommended domain transition checklist:

1. Set up the new domain, SSL, and DNS records.
   
2. Update WordPress Home URL and Site URL.
   
3. Configure 301 redirects from the old domain to the new one.
   
4. Update your BuddyBoss App configuration (iOS & Android settings).
   
5. Generate and release a new app build.
   
6. Enable Minimum Build Version to require users to update.
   
7. Upload new deep link configuration files (apple-app-site-association and assetlinks.json).
   
8. Test login, deep links, push notifications, and media rendering.
   
9. Monitor app and website performance post-launch to confirm stability.