Frequently asked questions
Using the LINE Platform
With LINE Login, you can retrieve the IDs, names, profile image URLs, and status messages of your users.
You can fill in a report here. Please note that we don’t provide technical support for LINE Login and BOT API Trial.
In the LINE@ Manager, go to Settings > Bot Settings > Details and make sure you have selected Allow for the “Allow bot to join group chats” item. Also note that only one bot can be in a group chat at one time. You cannot invite a bot to join a group or room which already has a bot.
No, we haven’t provided a way of getting the user IDs of the individual members of a group or room.
No, we haven’t provided a way of getting detailed information for groups.
This indicates that your account only has the DEVELOPER role. You must have the CHANNEL_EDITOR role to log in to the Channel Console. To obtain the CHANNEL_EDITOR role, ask a user with either the CHANNEL_CREATOR or CHANNEL_EDITOR role to assign you the CHANNEL_EDITOR role.
In LINE Login, you are only allowed to use the PROFILE permission.
You may not have submitted a registration request for your Channel. Once you submit the request, you’ll be able to see the technical configuration page for your Channel.
The SDK can be downloaded from the Channel Console. To access the download page, submit a Channel registration request with the NATIVE_APP application type. Once you’ve submitted the request, you’ll see a Download SDK link on the Channel Console.
Developing your app
You may not have the required credentials to log in. Check the Roles page on the Channel Console to see a list of users and their roles. Only users with the CHANNEL_EDITOR or DEVELOPER role can log in while your Channel is in the DEVELOPING stage.
In the Channel Console, go to the Roles page to add team members to your Channel. Once they are added to the Channel, they will be able to log in to your app.
Channels have 2 primary stages, DEVELOPING and PUBLISHED. Once your Channel is PUBLISHED, it cannot return to DEVELOPING. If you want to create a staging or beta environment to restrict access to certain users, you must create another Channel. However, such Channels cannot become PUBLISHED.
To use the LINE Login button, follow the guidelines on the LINE Login button page.
Technical support is not currently available for LINE Login and BOT API Trial. Business partners can contact their LINE representative for technical support.
NLChannelGatewayErrorDomain errors (for example, “NLChannelGatewayErrorDomain Error 102”) can occur if there are incorrect or missing settings in the Channel Console.
If your iOS application is getting this error, you should confirm the following items:
- The iOS bundle ID is registered in the “Technical Information” section of the Channel Console
- The iOS URL scheme is registered in the “Technical Information” section of the Channel Console
- The LINE account that you are using to log in is registered in the “Roles” section of the Channel Console
Publishing your app
Check the following items before publishing your app.
|Name||Confirm that your Channel’s name is correct and ready for publication.|
|Description||Confirm that your Channel’s description is correct and ready for publication.|
|Icon||Confirm that you have uploaded an app icon image in two sizes. (256×256 and 80×80)|
|Technical configuration||Confirm that you have set the correct application type, either WEB or NATIVE_APP.|
|LINE Login button||Confirm that your LINE Login button complies with the LINE Login button usage guidelines.|
The LINE Developers official account provides you with the latest updates on the LINE Platform. By adding the official account to your friend list, you’ll receive information on documentation updates, SDK releases, specification changes and more. To add the LINE Developers official account to your friend list, scan the QR code or if you are using a smartphone, tap the “Add Friends” button below.
LINE uses Open Graph tags from websites to generate URL previews.
Open Graph tags used by LINE:
|#||Open Graph tag||Example|
|1||og:image||<meta property=”og:image” content=”http://static.naver.jp/line_lp/img/ogp.png”>|
|2||og:title||<meta property=”og:title” content=”LINE : Free Calls & Messages”>|
|3||og:description||<meta property=”og:description” content=”LINE is a new communication app which allows you to make FREE voice calls and send FREE messages whenever and wherever you are, 24 hours a day!”>|
Examples of URL previews
- URL preview in a chat
- URL preview on Timeline
If you have integrated your application using LINE Login v1 and want to migrate to v2, you’ll find that users are identified using userId in v2 instead of mid in v1. Although we do not provide an API for checking whether an mid and userId belong to the same user, it is possible for you to check using an access token retrieved from LINE Login and the v1 and v2 profile endpoints by following the steps below
- Get an access token using LINE Login
- Call the /v1/profile endpoint to get the user’s mid
Getting user profile (v1)
- Call the /v2/profile endpoint to get the user’s userId
Getting user profile (v2)
- Map the user’s mid to the userId
Note: All versions of the LINE SDK (Android/iOS) from 4.0.0 and above use “v2”. All versions below 4.0.0 use “v1”.