# News: Articles for 2020/01

Introducing the redesigned LINE Developers site

We're excited to introduce our new, redesigned LINE Developers site. We believe this update makes it easier to use the LINE Platform products and find the documentation you need.

Here are the key changes to the site:

# Pages load faster

The site is now a single-page application running on VuePress, resulting in much shorter page load times than before.

# Better readability

We've improved the responsive design of the API reference. The layout adapts to the size of your screen, making it easier to read API arguments and sample code.

As you type your search terms, suggestions appear instantly, helping you find the information you need more quickly.

Search Results

Note: Although the new search is faster, it only returns results based on page titles and headings. We'll collect internal feedback over the coming weeks to see if people are satisfied with this new search, or we need to adjust it.

(We're working hard to bring the user feedback form from the old site to the new site.)

# What's next?

In addition to bringing back the user feedback form, we'll continue looking for ways to make it easier for you to use the LINE Developers site and documentation.

Keep up-to-date with the latest developments by adding the LINE Developers Official Account as a friend with the QR code or button below.

QR code for the LINE Developers account

Add friend

Notice about Flex Message Simulator outage (resolved)

We'd like to inform you about a service outage regarding Flex Message Simulator. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.

# Date and time of outage

January 21, 2020 13:03 JST (GMT+9) - January 22, 2020 11:59 JST (GMT+9)

# Cause

Issues with our servers.

# Affected services

Flex Message Simulator (https://developers.line.biz/flex-simulator/)

# Details

During the specified time, Flex Message Simulator was inaccessible.

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

LIFF v1 Server API end-of-life on March 31, 2020

March 31, 2020 marks the end-of-life date for LINE Front-end Framework (LIFF) v1 Server API. On that date, these features will be removed:

Use the latest version of LIFF

As announced on October 16, 2019, LIFF v1 will be discontinued.

# Use LIFF v2

All discontinued Server API functions can be used in LINE Developers Console. For more information on how to add a LIFF app to a channel, read this:

You can use other features with the same process.

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

New Messaging API endpoint for sending narrowcast messages

An endpoint for sending narrowcast messages has been added to the Messaging API.

This endpoint lets you send push messages to multiple users at any time.

You can specify the recipient using certain attributes (gender, age, OS type, region etc) and retargeting (audience).

For more information, see Send messages to multiple users using attribute information and retargeting.

Documentation available in Japanese only. English coming soon.

Update your code that uses the suspended LIFF SDK API

As announced on November 29, 2019, these APIs on LINE v9.19.0 and later for iOS were temporarily suspended due to technical issues.

  • liff.scanCode()
  • liff.bluetooth.*

Starting today, for end users using the LIFF app on LINE v9.19.0 and later for iOS, each API works as follows.

API Function
liff.scanCode() API is undefined
liff.bluetooth.* If the Bluetooth plug-in fails to initialize when calling liff.initPlugins(['bluetooth']), a FORBIDDEN error is returned.

If you use liff.scanCode(), we recommend that you also consider the above case and verify that the function exists.

Before modification:

liff.scanCode().then(result => {
  // result = { value: '' }
});

Modified:

if (liff.scanCode) {
	liff.scanCode().then(result => {
	  // result = { value: '' }
	});
}

For more information, see LIFF v2 API reference.

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

[Updated] Make sure the provider name is correct

Added on January 9, 2020

This specification change was scheduled to take place on January 9, 2020, but has been postponed to January 16, 2020.

Starting January 16, 2020, LINE Official Accounts using the Messaging API will display the provider name registered by the developer at the bottom of the profile.

Corporate LINE Official Accounts may also have personal names registered as provider names. Make sure that the correct name is registered. The provider name can be changed from the LINE Developers Console.

Profile

*The provider name is displayed in the red frame