Hi @Jeet Vora, you can have the files with different names, you just need to make sure that the Extensibility Configuration of each environment, is targeting the right ones.

The Extensibility Configuration is set in Lifetime, under the application settings, inside that page you can then set it for each environment, I haven't tested it with the new outsystems supported plugin, but for dev it would be something like 

"resources": {

         "android": {

             "AndroidResource": {

                 "src": "www/google-services-dev.json2",

                 "target": "app/google-services.json"

             }

         },

         "ios": {

             "IosResource": {

                 "src": "www/GoogleService-Info.plist2",

                 "target": "GoogleService-Info.plist"

             }

         }

Hope this helps

Best regards

Hi @Jeet Vora 

The easiest way is to override the extensibility configurations in lifetime as stated in https://success.outsystems.com/documentation/11/managing_the_applications_lifecycle/deploy_applications/override_the_default_mobile_extensibility_configurations/

I would suggest to change the name of your file for the different environment to something like google-services2.json and GoogleService-Info2.plist and make the extensibility configuration as @Diogo Madeira suggested.

Cheers,

Paulo Solipa

The extensibility configurations must be changed to comply with the Google services file names. You can configure your files by updating the "src" information on the configurations, like the image below:

For the configuration to be applied to the other environments, please follow the public documentation on how to Override the Default Mobile Extensibility Configurations. You need to set the custom extensibility configuration for each environment, like the image below, from our sandbox QA environment:
 Please apply the configurations to your environments and try to build the applications.

 The easiest way is to override the extensibility configurations in lifetime as stated in 

https://success.outsystems.com/documentation/11/managing_the_applications_lifecycle/deploy_applications/override_the_default_mobile_extensibility_configurations/