We've now released LIFF v2.3.0.
The changes in LIFF v2.3.0 are as follows:
You can now use paths and query parameters in the LIFF endpoint URL
As announced before, you can now use paths (
/path) and query parameters (
?key=value) added to the LIFF endpoint URL in the LIFF tab of the LINE Developers console.
Existing LIFF apps aren't effected until the setting is changed
It's necessary to change the setting in LINE Developers console to use the new specs in existing LIFF apps. Existing LIFF apps aren't affected by the new spec until the setting is changed.
To use the new specs, set Methods for converting additional information in the LIFF URL to Concatenate.
Don't change the setting if your existing LIFF app doesn't support the new specs. If setting to Replace (Backward compatibility mode), the LIFF app isn't affected by the new specs.
For more information, see Opening a LIFF app in the LIFF documentation.
A condition for the liff.permanentLink.createUrl() method to throw an exception added
When executing the
liff.permanentLink.createUrl() method, an exception is thrown if the current page URL doesn't start with the URL specified in Endpoint URL.
Especially when setting Methods for converting additional information in the LIFF URL to Replace (Backward compatibility mode), the paths and query parameters (
/2020campaign/?key=value) specified in Endpoint URL may not be included in the secondary redirect URL.
In this case, you can't get a permanent link because the
liff.permanentLink.createUrl() method meets the above conditions.
For more information, see
liff.permanentLink.createUrl() in the LIFF v2 API reference.
You can now get the send results of liff.shareTargetPicker()
As announced on April 21, 2020, you can now get the send results of
Before the spec change, the LIFF app was able to confirm whether the target picker was displayed, but not whether the message was sent after that.
After the change, the LIFF app is able to check whether the message has been sent, so you can change the behavior of the LIFF app depending on the user's situation.
- The return value of
liff.shareTargetPicker() is changed due to this spec change.
- This spec change doesn't affect users using LINE 10.3.0 - 10.10.0.
Sample code for this spec change
We recommend you to handle the return value according to the LINE versions that users are using as shown below:
For more information, see
liff.shareTargetPicker() in the LIFF v2 API reference.
An error code returned by liff.sendMessages() added
Previously, if passing the wrong parameters to
400 was returned as the error code of
LiffError. After the spec change,
INVALID_ARGUMENT is returned instead.
As long as the processing isn't split by error codes, this spec change doesn't effect your LIFF app.
Before the spec change:
After the spec change:
For more information, see Error details in the LIFF v2 API reference.