Provide way to define "target environments" for mobile project apps for build/pack

[kfawcett]

bumpy bump

[kfawcett]

Back again for another bump

[kfawcett]

Back for another bump. Still a really frustrating issue when building mobile projects.

[George]

Just a heads-up to let you know that we are working on this issue.

It will be implemented by using global App Connect data that can be defined for your app (main page) and be different per target.

So then you can add there for example host urls - and prefix your server connect actions with those so they get dynamically changed.

So that will solve the client side publishing.

We still have to check the local database connections, and make them target dependent for apps.

[Teodor]

Please check:

Dynamic API Prefixes with App Connect Global Data

Intro You can now set up different target environments for your mobile and desktop apps. Build against a dev API during testing and switch to production when deploying. The new prefix attribute in Server Connect and API components works with App Connect Global Data, letting you define prefixes like https://dev.example.com/ or https://example.com/ and switch between them easily without manually updating URLs. Selecting Active Environment You can set the active environment from the menu located …