app-launch
When triggered by this result-view, exits users from Bixby and opens a client application. This is a one-way event: Bixby can pass a payload of data to the application being opened, but once launched, applications cannot return to or interact with Bixby.
If this key is specified, you must specify either payload-uri or payload-mapper (but not both).
You can only use this key in very specific situations. For information on when to use this component, see the App Punch Out Policies. Your capsule can be rejected from the Marketplace if you misuse this key, and if its use is not within its designed purpose. Consider using attribution-link instead.
Your payload-mapper or payload-uri is not allowed to specify any dangerous permissions, such as accessing the user's contacts or calendars. If your capsule needs this level of access, consider using an appropriate Bixby library capsule.
result-view {
match : ShareViaResult (this)
message("") // override empty string to avoid displaying default result dialog. If you want to debug, you can print `#{value(this.uri)}` here instead
app-launch {
payload-uri ("#{value(this.uri)}")
}
render{
layout{
section{
content{
paragraph{
value("Share Via view")
}
}
}
}
}
}
Child Keys
| payload-mapper optional | Enables you to send a more complex app-launch payload by invoking a local JavaScript function that maps the result-view bindings and a context object into an opaque JSON string that satisfies the client's payload format requirements |
| payload-uri optional | Embedded template for the app launch URI |
| requires optional | Lists an optional set of requirements for the app-launch to execute successfully |