Skip to content

Conversation

@wmathurin
Copy link
Contributor

New optional args for the CLIs: consumer key, callback URL and login server.

  • forceios/forcedroid/forcereact and forcehybrid and the sfdx-mobilesdk-plugin now support three new arguments
  • test_force.js also optionally accepts a consumer key, callback URL and login server
  • READMEs have been updated

These arguments are part of the config passed into the prepareTemplate call (there will be a separate PR on the templates repo to make use of them).

Also updated the details and next steps printed out during app generation.

  • Details show the consumer key, callback url and login server if provided.
  • Next steps indicate the need to provide such values (if they were not provided) before building/running the application.

NB: there are not needed to generate/build an application, however without valid values login will not be possible.

- forceios/forcedroid/forcereact and forcehybrid and the sfdx-mobilesdk-plugin now support two new arguments
- these arguments are part of the config passed into the prepareTemplate call (there will be a separate PR on the templates repo to make use of them)
- test_force.js also optionally accepts a consumer key and callback URL

NB: there are not needed to generate/build an application, however without valid values login will not be possible)
Is also exposed on test_force.js
Also updated next steps (no longer mentioning oauth scopes)
@wmathurin wmathurin changed the title Consumer key args New optional args for the CLIs: consumer key, callback URL and login server Oct 15, 2025
@wmathurin
Copy link
Contributor Author

NB: Correspond templates changes have been merged (see forcedotcom/SalesforceMobileSDK-Templates#466).
CI running with templates changes.

@wmathurin wmathurin merged commit c5413f8 into forcedotcom:dev Oct 17, 2025
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants