In early 2023, we plan to discontinue providing company internal identifiers of chat rooms (one-on-one chat ID, group ID, and room ID) to LIFF apps.
After reviewing the functions of LIFF apps, we decided to discontinue providing company internal identifiers of chat rooms to LIFF apps. This change applies to all LIFF SDK versions, regardless of the LIFF versioning policy. This also applies to LINE MINI App since it is based on the LIFF system.
# Impact of discontinuing
Discontinuing the provision of company internal identifiers of chat rooms to LIFF apps will have the following impacts:
- Impact 1: Return value of
liff.getContext()
- Impact 2: Return values of APIs that issue, refresh, or verify the validity of LINE Login access tokens
# Impact 1: Return value of liff.getContext()
liff.getContext()
is the method to get the screen type (1-on-1 chat, group chat, multi-person chat, or external browser) from which the LIFF app is launched.
After the specification change, the return value of liff.getContext()
will no longer include properties that return the following identifiers:
- One-on-one chat ID (
utouId
) - Group ID (
groupId
) - Room ID (
roomId
)
For more information, see liff.getContext()
in the LIFF API reference.
# Impact 2: Return values of APIs that issue, refresh, or verify the validity of LINE Login access tokens
If chat_message.write
was selected as the LIFF app's required scope, a one-to-one chat ID (utouId
) would be included in the response's scope (scope
) of the following endpoints:
After the specification change, a one-to-one chat ID (utouId
) will no longer be included in the scope.
Before the change (as-is) | After the change |
---|---|
chat_message.write:UU29e6eb36812f484... | chat_message.write |
For more information, see Issue access token, Refresh access token, and Verify access token validity in the LINE Login v2.1 API reference.
# Alternatives
If you're currently providing LIFF apps that rely on the company internal identifiers described in the Impact of discontinuing section above, you should consider the following alternatives:
- Issue unique ID by your service instead of using the chat room identifiers
- Use group ID / room ID included in webhook events
# Issue unique ID by your service instead of using the chat room identifiers
Your service should issue a unique ID for each chat room and assign it to the LIFF URL (https://liff.line.me/{liffId}
) that the user accesses, so that your service can identify the chat room.
E.g., https://liff.line.me/{liffId}/?talk_id={ID issued by your service}
Example of current implementation | Alternative method |
---|---|
|
|
For the handling of LIFF URLs, developers should follow the LIFF app development guidelines.
For more information, see Create a secondary redirect URL in the LIFF documentation.
# Use group ID / room ID included in webhook events
If you're currently retrieving the group ID or room ID from the return value of liff.getContext()
of your LIFF app, you can retrieve them from the Messaging API's webhook event instead.
Example of current implementation | Alternative method |
---|---|
|
|
For more information, see Webhook events for one-on-one chats or group chats and multi-person chats in the Messaging API documentation and Webhook Event Objects in the Messaging API reference.
# Scheduled date of change
Early 2023
The content and date of this specification change are subject to change without notice. The date of the change will be announced as soon as it's determined.
LINE will continue to work on further improving our services to our customers. Thank you for your understanding and cooperation.