Create a new OneSignal application
You can use this action to automatically create a OneSignal application. You can also upload a
.p12with password, a GCM key, or both.
|Supported platforms||ios, android|
onesignal( auth_token: "Your OneSignal Auth Token", app_name: "Name for OneSignal App", android_token: "Your Android GCM key (optional)", android_gcm_sender_id: "Your Android GCM Sender ID (optional)", apns_p12: "Path to Apple .p12 file (optional)", apns_p12_password: "Password for .p12 file (optional)", apns_env: "production/sandbox (defaults to production)" )
||OneSignal Authorization Key|
||OneSignal App Name|
||ANDROID GCM KEY|
||GCM SENDER ID|
||APNS P12 File (in .p12 format)|
||APNS P12 password|
* = default value is dependent on the user's system
Actions can communicate with each other using a shared hash
lane_context, that can be accessed in other actions, plugins or your lanes:
onesignal action generates the following Lane Variables:
||The OneSignal app ID of the newly created app|
||The auth token for the newly created OneSignal app|
To get more information check the Lanes documentation.
To show the documentation in your terminal, run
fastlane action onesignal
It is recommended to add the above action into your
Fastfile, however sometimes you might want to run one-offs. To do so, you can run the following command from your terminal
fastlane run onesignal
To pass parameters, make use of the
: symbol, for example
fastlane run onesignal parameter1:"value1" parameter2:"value2"
It's important to note that the CLI supports primitive types like integers, floats, booleans, and strings. Arrays can be passed as a comma delimited string (e.g.
param:"1,2,3"). Hashes are not currently supported.
It is recommended to add all fastlane actions you use to your
This action, just like the rest of fastlane, is fully open source, view the source code on GitHub