[FEATURE REQUEST] Enable Runtime Region Configuration in runtime for Workspace Migration | Community
Skip to main content
Submitted

[FEATURE REQUEST] Enable Runtime Region Configuration in runtime for Workspace Migration

  • November 20, 2025
  • 0 replies
  • 12 views

Forum|alt.badge.img

Feature Request: Runtime Region Configuration for Mobile SDK

Currently, the Mobile SDK requires region configuration to be set in AndroidManifest.xml/Info.Plist using meta-data tags, which are read only at app startup and cannot be changed at runtime. This creates limitations when working with workspaces in different regions or during migration scenarios.

https://developers.intercom.com/installing-intercom/cordova-phonegap/data-hosting-region-configuration
 

Requested Enhancement:

Add the ability to configure the Intercom server region at runtime, similar to how the existing changeWorkspace() method works. This would allow developers to:

  • Switch between workspaces in different regions without rebuilding the app
  • Support migration scenarios from US to EU/AU regions more seamlessly
  • Handle multi-region deployments dynamically

Proposed Implementation:

Option 1: A new method like setServerRegion(region: String) that accepts values such as "US", "EU", or "AUS" and can be called before or alongside workspace changes.
Option 2: Enhancing the existing changeWorkspace() method to accept an optional region parameter, like:

changeWorkspace("api_key", "app_id", region: "EU")

This would let developers switch both workspace and region in a single call, making cross-region migrations much smoother without needing separate app builds.

Business Impact:

This would significantly improve the developer experience for regional workspace migrations and eliminate the need for separate app builds for different regions.