# News: Articles for #LINE Login

LINE's APIs now support TLS 1.3

Added July 30, 2020

For access to the APIs from outside Japan, TLS 1.3 will be available after August 4, 2020. For more information, see the news on July 30, 2020, LINE's APIs will support HTTP/2.

LINE's APIs now support TLS 1.3.

# Domain names subject to the update

  • api.line.me
  • api-data.line.me
  • access.line.me

# SSL/TLS supported protocol versions

See this table for the differences before and after the update:

Protocol version Before update After update
TLS 1.3
TLS 1.2
TLS 1.1
TLS 1.0
SSL 3.0
SSL 2.0

# Impact

If you are using any of the above APIs, please confirm that your app can communicate using the updated supported protocol versions.

# Transition period

  • For access from Japan: TLS 1.3 is available after July 1, 2020.
  • For access from outside Japan: TLS 1.3 is available after August 4, 2020.

Support for TLS 1.0 and TLS 1.1 will be discontinued in the future. The discontinuation schedule is undecided. We will make an announcement as soon as it is decided.

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

Notice about service outage for LINE Login (resolved)

We want to inform you about a service outage regarding LINE Login. The issue has now been resolved. We apologize for any inconvenience this may have caused.

# Date and time of outage

Date: 2020/6/24 Time: 15:30-16:14 JST (GMT+9)

# Cause

Issues with our servers.

# Details

The LINE Login process did not work properly in some cases.

Auto login and LINE login with Single Sign On (SSO) were not affected.

LINE will continue to improve the quality of its services to prevent future outages. Thank you for your understanding.

LINE Login允許存取的畫面變更

我們修改了LINE Login允許存取畫面的部分設計與文字,以更加方便使用者的閱讀與使用。

# 變更

  • 為了讓使用者更加容易了解在畫面上應採取的動作,我們刪除了畫面標題允許存取並將畫面說明修改為此服務提供者要求以下的存取權限
  • 您可以藉由點選要求存取的項目中的Arrow icon圖示,來決定是否要顯示或隱藏各項的說明文。
  • 我們將許可的按鈕放大使其更加明顯。

Improved LINE Login Consent Screen

本次修改的許可畫面將會出現在app向使用者請求存取權限的過程中。更多資訊請查看要求授權

不建議使用LINE URL scheme 'line://'

由於LINE URL scheme line://可能會產生接管攻擊,因此不建議使用。請改用https://line.me/R/https://liff.line.me/

line://接管攻擊是指使用者在點擊line://時,其他非LINE的app可能會不顧使用者的意願自動開始執行。這項攻擊僅會在特定的情況下發生。

line://將來有可能會受到中止。如有進一步的決定,我們會在此通知。

更多關於LINE URL scheme的資訊,請查看『透過LINE URL scheme使用LINE功能』。

Notice about service outage for LINE Login (resolved)

We want to inform you about a service outage regarding LINE Login. The issue has now been resolved. We apologize for any inconvenience this may have caused.

# Date and time of outage

Date: 2019/12/19 Time: 19:10-19:32 JST (GMT+9)

# Cause

Issue with our servers.

# Details

LINE Login and LIFF operations were unstable and did not work properly.

LINE will continue to improve the quality of its services to prevent future outages. Thank you for your understanding.

新的 LINE Login 通知訊息

當用戶使用 LINE Login v2.1 登入網頁,來自官方 LINE 帳號的登入通知訊息,內容會因登入方式而有所不同。

自 2019 年 12 月 9 日起,無論登入方式為何,用戶將收到統一的通知訊息內容。

LINE Login notification message

dummy dummy
登入成功 LINE系統提醒您,您目前已在 X 上登入 Y (Z)。
IP位址: {ip_address}
登入位置: {Location}
若您本人並未執行上述操作,請盡速由此連結的畫面中點選登出: {device_link}
如有疑慮,您可由此變更LINE密碼: {help_link}
登入失敗 LINE系統提醒您,剛剛有人嘗試在 X 上使用您的帳號登 Y (Z),但並未成功。
IP位址: {ip_address}
登入位置: {Location}
若您本人並未執行上述操作,請透過此連結來確認登入中的裝置: {device_link}
如有疑慮,您可由此變更LINE密碼:

請注意 (Z) 代表網頁連結,在某些情況下可能會被刪除。

# 適用對象

所有使用 LINE Login v2.1 登入網頁的 LINE 用戶。

最新 ID token verification endpoint 正式上線

當開發者的後端伺服器收到來自 LINE Login v2.1 或 LINE SDK 的 ID token,開發者需要驗證此 ID token 是否可靠。

過去開發者必須使用 JWT library,或自行撰寫用以譯解和驗證的程式碼。

在最新 ID token verification endpoint 正式上線後,開發者只須將 HTTP request 發送至 verification endpoint,便可確認 ID token 是否可靠。

如欲了解如何驗證 ID token,請查看 Transfer ID token to back-end server

Notice about system maintenance

We're performing system maintenance at the below time. We apologize for any inconvenience.

# Scheduled maintenance time

September 26, 2019 16:20-16:50 JST (+9 GMT)

The maintenance will only last a few seconds and will take place somewhere in this time window.

# Impact

Messaging API, LINE Login, and LIFF operations may result in errors. Specifically, the following events can occur:

  • Messaging API (https://api.line.me/v2/bot/*) returns an error with status code 500.
  • An error with status code 500 is returned when a user logs in with LINE Login or starts a LIFF app.

LINE SDK v4.x end-of-life on December 12th, 2019

December 12th, 2019 marks the end-of-life date for LINE SDK v4.0 for Android and LINE SDK v4.1 for iOS (from hereon collectively called LINE SDK v4.x). On that date, we'll remove from this site the following things:

# Why we're doing this

To ensure a consistent, secure, up-to-date experience for LINE users, our partners' apps and services should use the latest version of our technology. We already marked LINE SDK v4.x as deprecated some time ago, but continued to offer documentation and download links as a courtesy to partners who couldn't upgrade on short notice. Now we're taking the next logical step: declaring LINE SDK v4.x end-of-life and removing all references from our site.

# Upgrading to a new SDK version

What you need to do to upgrade depends on what version you're currently using.

From To Notes
LINE SDK v4.x for iOS Objective-C LINE SDK v5.2 for iOS Swift The old and new versions use different programming languages, which makes migrating a big task. We hope the migration instructions in Upgrading the SDK will make it easier.
LINE SDK v4.x for Android LINE SDK v5.1 for Android There are minor differences between the old and new version, particularly with relation to how login works. The page Integrating LINE Login with your Android app explains how to integrate the latest version.
LINE SDK v3.x for iOS Objective-C LINE SDK v5.2 for iOS Swift There are major differences between the old and new version, meaning you'll have to redo your integration from scratch. See Integrating LINE Login with your iOS app for instructions.
LINE SDK v3.x for Android LINE SDK v5.1 for Android There are major differences between the old and new version, meaning you'll have to redo your integration from scratch. See Integrating LINE Login with your Android app for instructions.

Notice about service outage for LINE Login (resolved)

We want to inform you about a service outage regarding LINE Login. The issue has now been resolved. We apologize for any inconvenience this may have caused.

# Date and time of outage

Date: July 18, 2019 Time: 9:38–10:40 JST (GMT+9)

# Cause

Issue with our servers.

# Details

LINE Login returned http error codes with the pattern 5xx (500, 501, etc.) for some requests. As a result, LINE Login was unavailable in the following applications:

  • Web application
  • Desktop app

LINE will continue to improve the quality of its services to prevent future outages. Thank you for your understanding.

LINE SDK for Flutter released

We've released a new LINE SDK for Flutter. This SDK is a Flutter plugin that lets you access the functions of LINE SDK for iOS and LINE SDK for Android in your Flutter app with Dart. For details, see these pages:

The LINE SDK for Flutter documentation is only available in English, for now.

LINE Login: new parameters and properties added

We've added new parameters and properties to LINE Login v2.1:

  • The parameter ui_locales lets you specify the display language and script for LINE Login.

  • The property amr specifies the authentication methods used in authentication. This corresponds to the OpenID Connect 1.0 amr Claim.

    The amr property is automatically added to all LINE login v2.1 enabled channels, so no additional development work is required.

See also Integrating LINE login with your web app. If you haven't integrated LINE Login yet, we hope you'll consider doing so now.

Note

New or changed LINE Login functions may cause changes in the structure of the payload JSON object. These changes may include added properties, variations in property order, and added/removed white space and line breaks. Make sure your implementation can handle both current and future payload data objects.

Any functionality we offer may be changed without notice. However, we'll try notify you in advance if we believe that the change will significantly affect developers.

Notice about service outage for LINE Login (resolved)

We'd like to inform you about a service outage regarding LINE Login. The issue has now been resolved. We apologize for any inconvenience that this may have caused.

# Date and time of outage

Date: June 17, 2019 Time: 11:41–13:01 JST (GMT+9)

# Cause

Issue with our servers.

# Details

LINE Login returned error code "400 Bad Request" when some users attempted to log in.

LINE will continue to improve the quality of its services to prevent future outages. Thank you for your understanding.

Notice about system maintenance

We will perform maintenance for LINE Login and the Social API. We apologize for any inconvenience caused by this.

# Scheduled maintenance time

March 05, 2019 05:30-06:30 JST (+9 GMT)

# Impact

API operations using the access token for LINE Login v2.0 and the Social API v2.0 can be interrupted for 30 seconds to 1 minute.

This maintenance will not affect API operations using the access token for LINE Login v2.1 and the Social API v2.1.

Notice about service outage for LINE Login and the Social API (resolved)

We'd like to inform you about a service outage regarding LINE Login and the Social API. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.

# Date and time of outage

Date: February 26, 2019

Time: 6:46–7:16 JST (GMT+9)

# Cause of the outage

Issue with our servers.

# Details

HTTP status code 500 was sometimes returned when requests were sent to the LINE Login and Social APIs.

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

LINE Login: You can log in with a QR Code

Web apps that use LINE Login v2.1 now allow users to log in by scanning a QR code on the login screen. They can scan the QR code with LINE on their smartphones. As before, they can also log in with their email address and password.

QR Code login

We have applied this new feature to all channels with LINE Login v2.1 enabled. You don't need any further development.

Don't let your users miss out on this great UX feature — implement LINE Login today!

QR Code is a registered trademark of DENSO WAVE INCORPORATED in Japan and in other countries.

The behavior of a consent screen displayed to LINE Login users has changed

The behavior of a consent screen displayed to users at login has been changed when you use LINE Login to request your users to grant your app permission to get their email address.

Previously, when a user attempted to log in, a consent screen was displayed at each login with or without the prompt parameter.

Currently, a consent screen is not displayed for a certain period unless the user's email address changes.

For more information, see Authentication process.

LINE SDK 5.0.0 released

The LINE SDKs 5.0.0 for Android, iOS Swift, and iOS Objective-C have been released. For installation and usage instructions, see the following guides:

# Changes

# LINE Login v2.1 and Social API v2.1 are supported

You can set permissions to be granted to your app as scopes when users log in to your app with LINE Login. By setting scopes, you can get ID tokens when you get access tokens. Those tokens contain user information according to the scopes you set with the login request.

You can display an option to add your bot as a friend to users logging in to your app. You can get the friendship status between users and your bot with login responses and the Social API.

# New SDK version in Swift

Developed in Swift, the LINE SDK for iOS Swift provides a modern way of implementing LINE APIs. The LINE SDK 5.0.0 for iOS Objective-C is the last version of our Objective-C SDK.

# Open-source SDK

The LINE SDK for Android and iOS Swift are open-sourced. Visit the following repositories to check the provided code and samples.

# Detailed reference

Now you can access detailed reference based on the source code. For more information, see the following references:

Notice about service outage for LINE Login and the Social API (resolved)

We'd like to inform you about a service outage regarding LINE Login and the Social API. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.

# Date and time of outage

Date: June 26, 2018

Time: 16:25–17:00 JST (GMT+9)

# Cause of the outage

Issue with our servers.

# Details

An error was returned when the following API features were accessed:

  • Get user profiles
  • Get friendship status
  • LINE Login

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

New permission to get users' email address released

Now you can request users who log in using LINE Login to grant your app the permission to get their email address. To do so, you first need to apply for the permission in the console.

For more information, see the sections below in Integrating LINE Login with your web app.

LINE Login v1 to be discontinued

Note: This notice only applies to LINE Login v1 users. These changes do not apply if you are using the latest v2.1 or v2 endpoints.

Starting from March 31, 2018 we will start terminating LINE Login V1 endpoints. Please see the following schedule on the termination date for each endpoint. After an endpoint is terminated, any access to it will result in a 4XX status code as a response.

# Endpoints terminating on March 31, 2018
  • Issue access token: https://api.line.me/v1/oauth/accessToken
# Endpoints terminating on April 30, 2018
  • Get user profile: https://api.line.me/v1/profile
  • Logout: https://api.line.me/v1/oauth/logout
# Endpoints terminating on June 30, 2018
  • Verify access token: https://api.line.me/v1/oauth/verify
  • API endpoints for the LINE SDK for iOS and Android version 3.x or earlier

To avoid any issue related to the termination of LINE Login V1, please make sure to update your service to the latest LINE Login version. Please see the following page for more details on the latest LINE Login version.

Social API overview

Please also notice that the LINE user identifier is different between LINE Login V1 and LINE Login V2 or higher. If you are using the V1 user identifier on your service, you will need to convert the user identifier to use the latest LINE Login version. Please see the following page for more details on how to convert the LINE user identifier.

Converting an MID to a user ID

If you are a partner, we will contact you individually for more details.

New article on converting an MID to a user ID

Users are identified using a user ID in LINE Login v2 or later instead of an MID in v1. If you have integrated LINE Login v1 into your app and want to migrate it to v2 or later, you need to convert MIDs to user IDs.

For more information, see Converting an MID to a user ID.

LINE Login v1 to be discontinued

Note: This notice only applies to LINE Login v1 users. These changes do not apply if you are using the latest v2.1 or v2 endpoints.

We will be discontinuing the LINE Login v1 endpoints listed below on March 31, 2018. Once these endpoints are discontinued, a 4xx status code and error message will be returned.

  • Access token endpoint: https://api.line.me/v1/oauth/accessToken
  • Verify endpoint: https://api.line.me/v1/oauth/verify
  • Profile endpoint: https://api.line.me/v1/profile
  • Logout endpoint: https://api.line.me/v1/oauth/logout

Also note that versions 3.x.x and below of the LINE SDK for iOS and Android will no longer work after LINE Login v1 is discontinued.

If you are currently using LINE Login v1, we highly recommend updating your app to the latest version of LINE Login as soon as possible to avoid any issues when LINE Login v1 is discontinued. For information on the latest version of LINE Login, see the following pages.

LINE URL scheme information released

We've added an article about the LINE URL scheme to our LINE Login and Messaging API documentation. You can use the URL schemes to help your users navigate to specific content such as the camera, location, or settings screens in LINE. The LINE URL scheme can be used in your bot (Messaging API) from within LINE or in your native or web apps to automatically open LINE.

See the new articles below.

Link your bot to your LINE Login channel

We've added an option to display a prompt to let you display an option for users to add your bot as a friend when logging in to your app with LINE Login. To do this, first, link a bot to your LINE Login account from the new "Bot linked to this channel" item in the LINE Developers console, then include the bot_prompt query parameter in the authorization URL for LINE Login.

For more information on this feature, see Linking a bot with your LINE Login channel.

In addition, we've released a new resource for the Social API which lets you get the friendship status between your bot and a user. Send a GET request to https://api.line.me/friendship/v1/status to see if the user has added your bot as a friend or not.

To see the API reference for this resource, go to Get friendship status.

Note: This feature is not currently available to enterprise users. If you are an enterprise user and would like to use this feature, please contact your LINE representative.

LINE Login and Messaging API glossaries

To help you better understand the terms and concepts used in our documentation, we've added glossaries for both LINE Login and Messaging API.

Check them out using the links below.

Notice about LINE Login service outage (resolved)

This is a notice to inform you about a recent service outage for LINE Login. The issue has now been resolved but we apologize for any inconvenience that this may have caused.

# Date and time

Date: October 16, 2017
Time: 16:30–17:36 JST (GMT+9)

# Cause

Issue with our servers.

# Situation

During the date and time stated above, certain channels may have received the following error when making an API call to retrieve an access token.

{"error":"invalid_grant","error_description":"authorization code expired or incompatible"}

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

LINE Login v2.1 released

We have released LINE Login v2.1 which provides new features to make it easier for you to implement a login feature to your application. The new version adds support for the OpenID Connect 1.0 specification which is an identity layer on top of OAuth 2.0.

Here are some of the key changes.

# ID tokens

With LINE Login 2.1, you'll be able to get ID tokens which contain user profile information when you retrieve the access token. This means that you no longer need to send a separate request to retrieve a user's profile information.

For more information, see ID tokens.

# Login sessions

In version 2.1, when users are redirected to the authorization endpoint, we'll be able to check the login session to determine if the user is logged in to LINE or not. If users are logged in to LINE and their browsing session is valid, they will not be required to enter their email and passwords to log in.

For more information, see Authentication process.

# Updated endpoints

We have updated our authorization endpoints where you can use the new version 2.1 features. You can find more detailed information on the following pages.

Note: You'll still be able to use our LINE Login v2 endpoints.

Changes to the LINE Login review criteria

The LINE Login review criteria has been modified. Up until now, a review was required to change the status of LINE Login channels from "developing" to "published". However, from now on, LINE Login channels created on the LINE Business Center will automatically have the "published" status.

For existing LINE Login channels, you will be able to change the status to "published" from the Channel Console without a review.

Note that the LINE Login review criteria may change at a later date upon the release of new APIs or features. You should also make sure that your app complies with the LINE Login Button Usage Guidelines and LINE Developers Agreement.

New versions of Web Login and the LINE SDK released

New versions of Web Login, LINE SDK for Android, and LINE SDK for iOS have been released. Details of each release are outlined below.

# Web Login v2

Key changes:

  • Endpoint URLs contain "v2" instead of "v1"
  • userId is returned in get user profile requests. mid is no longer returned in the response.
  • scope is returned with the default value of p for permission to get user profile information
  • error and state parameters are returned in error responses for authorization

For more information, see the updated documentation below.

You can also use the LINE Login starter application to help you get started with Web Login.

Note: Web Login v1 will be discontinued in January 2018. If you are using Web Login v1, please migrate to the Web Login v2 before that time.

# LINE SDK for Android 4.0.0

Key changes:

  • Implements the Auto Login feature using Chrome custom tabs, instead of app-to-app authorization
  • Automatically gets user profile information at login
  • Has a method to verify the access token
  • Has a method to refresh the access token
  • Has a method to log the user out

For more detailed information on how to use the LINE SDK for Android, see the updated documentation below.

Download the LINE SDK for Android

# LINE SDK for iOS 4.0.0

Key changes:

  • Automatically gets user profile information at login
  • Has a method to verify the access token
  • Has a method to refresh the access token
  • Has a method to log the user out

For more detailed information on how to use the LINE SDK for iOS, see the updated documentation below.

Download the LINE SDK for iOS

Note: The reference documentation for the LINE SDK for Android and iOS are currently only available in English.

We will continue to provide improvements so that developers can code more easily.

Specification change to API postponed

The date of the specification change to LINE Login (as stated in the November 22 post) will be postponed from December 15 to December 19. The details of the specification change as specified in the earlier post are shown below.

November 22 post:

Based on the OAuth 2.0 specification, we will add parameters [error, state] to the error response of LINE Login authentication.

These parameters will be added to the error response sent to the callback URL when the user selects cancel on the agreement screen which is displayed during the LINE Login process.

In addition, in accordance with the OAuth 2.0 specification, the errorCode and errorMessage parameters in the current error response will be deprecated and removed in the future.

Important: Specification change to API

Based on the OAuth 2.0 specification, we will add parameters [error, state] to the error response of LINE Login authentication.

These parameters will be added to the error response sent to the callback URL when the user selects cancel on the agreement screen which is displayed during the LINE Login process.

In addition, in accordance with the OAuth 2.0 specification, the errorCode and errorMessage parameters in the current error response will be deprecated and removed in the future.

[Date]

December 15, 2016

The LINE SDK for iOS 3.2.1 released and the LINE starter application revised

The LINE SDK for iOS has been updated to version 3.2.1. You can download it from the LINE SDK archives on the following page:

Download LINE SDK

Changes

  • LineAdapter+Login.framework and LineAdapterUI.framework merged to LineAdapter.framework.
  • Definition changed for swift.

In addition, the LINE starter application has been revised to make compatibility with this version of SDK. You can clone or download it from the below GitHub repository.

https://github.com/line/line-sdk-starter-ios

We will continue to provide improvements so that developers can code more easily.

LINE SDK for iOS version 3.1.17 released

The LINE SDK for iOS has been updated to version 3.1.17. You can download it from the LINE SDK archives on the following page:

Resources - Download LINE SDK

Changes:

  • Fixed an issue where return error message is not correct when a token refresh request fails.
  • Fixed an issue with iOS 9 where authorization process is not canceled when the cancel button is tapped.

We will continue to provide improvements so that developers can code more easily.

LINE SDK for iOS version 3.1.15 released

The LINE SDK for iOS has been updated to version 3.1.15. You can download it from the LINE SDK archives on the following page:
Changes:
  • Fixed app-to-app authentication error on iOS9.
We will continue to provide improvements so that developers can code more easily.

LINE SDK for iOS version 3.1.14 released

The LINE SDK for iOS has been updated to version 3.1.14. You can download it from the LINE SDK archives on the following page:

Resources - Download LINE SDK

Changes:

  • Fixed error when building for submission on Xcode 7.

We will continue to provide improvements so that developers can code more easily.

Settings for iOS 9 or later

For developers developing applications with the iOS 9 SDK, please use the following settings to ensure that your application works with iOS 9.

iOS - Settings for iOS 9 or later

We will continue to provide improvements so that developers can code more easily.

Specification change to API completed

The specifications of the following API has been changed as shown below as announced on August 31.

[API]
https://api.line.me/v1/oauth/accessToken

[Changes]

The expires_in value will be displayed in seconds instead of milliseconds.

It will be possible to refresh tokens before they expire. Currently, an error will occur when you refresh a token before it has expired.


[Reason]

To comply with OAuth2 specifications.


[Date and Time]
16:00 on September 14, 2015 (Finished)

LINE SDK for iOS version 3.1.13 released

The LINE SDK for iOS has been updated to version 3.1.13. You can download it from the LINE SDK archives on the following page:
Changes:
  • The "refreshWithResultBlock" method returns an error if the access token cannot be refreshed.
  • Minor bug fixes.
We will continue to provide improvements so that developers can code more easily.

Important: Specification change to API

We will be making changes to the specifications of an API on the LINE Login Platform.

[API]
https://api.line.me/v1/oauth/accessToken

[Changes]

The expires_in value will be displayed in seconds instead of milliseconds.

It will be possible to refresh tokens before they expire. Currently, an error will occur when you refresh a token before it has expired.


[Reason]

To comply with OAuth2 specifications.


[Date and Time]
16:00 on September 14, 2015

Description of the expires_in property modified

The description of the expires_in property has been modified. This change can be found in the Integrating Web Login page under the Retrieving Access Tokens section. The previous description for the expires_in property was incorrectly described as the elapsed time from epoch time. It has been corrected to describe the property as the elapsed time from when the response is generated.

This is only a modification of the documentation. The API has not been modified.

LINE Starter Application for iOS and Android released

The LINE Starter Application for iOS and Android has been released. The LINE Starter Application provides examples to help you get started on integrating the LINE SDK into your application.

The sources can be found on the following links.

We will continue to provide improvements so that developers can code more easily.

LINE SDK for iOS version 3.1.12 released

The LINE SDK for iOS has been updated to version 3.1.12. You can download it from the LINE SDK archives on the following page:
Changes:
  • Added new endpoints for the LINE Platform.
  • Added “clearLocalLoginInfo" method to remove login information from local cache.
  • Added function allowing users to switch accounts from the WebView login.
  • Added the capability to retrieve SDK version on the LineAdaptor.
We will continue to provide improvements so that developers can code more easily.

LINE SDK for iOS version 3.1.10 released

The LINE SDK for iOS has been updated to version 3.1.10. You can download it from the LINE SDK archives on the following page:

Resources - Download LINE SDK

Changes:

  • Modified to specify "kSecAttrAccessible: kSecAttrAccessibleAfterFirstUnlock" when storing to KeyChain.
  • Added the expiresDate property to the LineApiClient.

We will continue to provide improvements so that developers can code more easily.

LINE SDK for iOS version 3.1.9 released

The LINE SDK for iOS has been updated to version 3.1.9. You can download it from the LINE SDK archives on the following page:

Resources - Download LINE SDK

Changes:

  • Can no longer be used with iOS 4.9 and lower.
  • Removed the JSONKit dependency; NSJSONSerialization will be used instead.
  • Fixed the bug where the SDK crashes when the refresh token is null.

We received a lot of feedback about the SDK crashing when using JSONKit in a 64-bit environment so we decided to remove the JSONKit dependency.

We will continue to provide improvements so that developers can code more easily.