# News: Articles for 2018/11

LINE SDK 4.0.10 for Android released

The LINE SDK 4.0.10 for Android has been released. You can download the SDK from the following page.

Changes:

  • Fixed an issue where an activity is not found when authenticating with LINE Login after LINE is invalidated on the device.

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

[Update] Change to the imagemap message

We decided not to make the specification change of the imagemap message that we announced on November 14, 2018, for compatibility. We apologize for any inconveniences caused and appreciate your understanding.

You can continue to send imagemap messages even if you set actions in the area that does not fit the width and height of the image specified by the baseSize property.

However, the layout of such imagemap messages might be broken on the user device. We recommend setting actions within the area that fits the width and height of the image specified by the baseSize property.

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 Things Developer Trial released

LINE Things Developer Trial has been released. For usage, see the following guide and API reference:

These documentation sets will be translated into English soon.

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:

Correction to documentation

There were errors in the news release and documentation for the new LIFF server API to update a LIFF app. We apologize for any inconvenience.

# News

【Incorrect】 The HTTP request to the API endpoint to update a LIFF app is changed from PUT to PATCH. Now you can partially update the properties of your LIFF apps.

【Correct】 The API endpoint for updating a LIFF app is changed. Now you can partially update the properties of your LIFF apps.

# API reference

【Incorrect】 PATCH https://api.line.me/liff/v1/apps/{liffId}

【Correct】 PUT https://api.line.me/liff/v1/apps/{liffId}

For more information, see Update LIFF app.

Renewed LIFF server API

Now you can set the following properties to your LIFF apps.

  • description property
  • features.ble property

The HTTP request to the API endpoint to update a LIFF app is changed from PUT to PATCH. Now you can partially update the properties of your LIFF apps.

For more information, see the following sections:

New webhook events are added for the Messaging API

We have added two webhook events: Member join event and member leave event.

For more information, see the following sections:

A new login method has been added

Now you can use your LINE Business ID to log in to the LINE Developers console.

If you are an enterprise user who satisfies both of the two conditions below, click "Log in with email" and enter the email address and password associated with your LINE Business ID to log in to the console.

  • You use the LINE Developers console for the first time.
  • You have a LINE Business ID.

Otherwise, click "Log in with LINE" and enter the email address and password associated with your LINE account to log in to the console.

Maintenance period for the LINE Developers site is extended

Today, we will perform maintenance for the LINE Developers site to change its domain name. Due to circumstances, the maintenance period is extended as below.

We apologize for any inconvenience and appreciate your understanding.

# Scheduled maintenance time

November 15, 2018 12:00-13:00 JST (+9 GMT)

The maintenance period is extended by 50 minutes.

# Impact

The LINE Developers site will be unavailable during the maintenance time.

In this maintenance the LINE Developers site's domain name will change from "developers.line.me" to "developers.line.biz". All accesses to the old domain will be redirected to the new domain.

Change to the imagemap message is scheduled

We'd like to inform you that we will change the specification of the imagemap message.

After the specification change, if the method of setting actions in imagemap messages is incorrect as below, an error occurs and you cannot send imagemap messages.

The current specification: You can send imagemap messages even if actions are set in the area that does not fit the width and height of the image specified by the baseSize property.

In this case, the layout of the imagemap displayed on the user device might be broken.

The new specification: You cannot send imagemap messages because the API request fails if actions are set in the area that does not fit the width and height of the image specified by the baseSize property.

This specification change will be released on November 27th.

Domain name change for the LINE Developers site

On November 15, 2018, we will perform maintenance for the LINE Developers site to change its domain name.

# Scheduled maintenance time

November 15, 2018 12:00-12:10 JST (+9 GMT)

# Impact

The LINE Developers site will be unavailable during the maintenance time.

In this maintenance the LINE Developers site's domain name will change from "developers.line.me" to "developers.line.biz". All accesses to the old domain will be redirected to the new domain.

Correction to documentation

There were errors in the description of the new destination property added to webhook events released yesterday. We correct it as below:

【Incorrect】The destination property includes the MID of a bot that should reeive the webhook events. The property value is a string that matches the regular expression, "u[0-9a-f]{32}".

【Correct】The destination property includes the user ID of a bot that should reeive the webhook events. The property value is a string that matches the regular expression, "U[0-9a-f]{32}".

For more information, see Request body.

Specification change for the Messaging API

# You can play videos in imagemap messages

Now you can play videos in imagemap messages.

For more information, see Imagemap message.

Note that this change doesn't include the validation of action areas of imagemap messages announced on October 24. We will inform you once we decide on our schedule.

# New properties are added to webhook events

  • The body of webhook events now includes the user ID (destination) of a bot that should receive the webhook events. For more information, see Request body.
  • New information is available in message objects for image, video, and audio messages. For more information, see Image, Video, and Audio.

Correction on November 9, 2018 : MID -> user ID

# Flex Messages can now be multicast

Now you can send Flex Messages with the /v2/bot/message/multicast endpoint.

For the /v2/bot/message/multicast endpoint, see Send multicast message in the Messaging API reference.