Line app after new iOS

Pol86 wrote:

Line app after new iOS

the app “Line” (the western version, the eastern is slightly different but they comunicate each other) stopped working. I cannot send or receive any messages. Plus it seems that there is no notification menu in iOS dedicated to Line anymore, so I cannot even simple turn on them. In fact, Line is keep on asking me to turn on the notifications. It seems weird for a message app to get out with an update like this, clearly blocking everyone that are using it, but I’m receiving some feedback from other users to have the same problem. Is a know problem?

The app developer may not have updated their software to ensure compatibility with the iOS version your device is currently running.

If you encounter any challenges with third-party applications, the best course of action is to directly contact the app developer for further assistance. Here's a brief guide on how to do it:

1. Identify the app developer.
2. Visit their website or app store listing.
3. Look for their contact information or support channels.
4. Clearly describe the issue you are facing.
5. Provide any necessary information they may need.
6. Follow their instructions and provide feedback.
7. Be patient and follow up if needed.

By reaching out to the app developer, you increase your chances of receiving accurate and personalized support for the challenges you're experiencing. To contact an App developer --> How to contact an app developer - Apple Support

Hello, after update 27.0.1 LINE it's ok.

maybe the developers needs to do an update to their app to support ios27

Home | LINE Help Center

Pol86 wrote:

Line app after new iOS

Hello, after the update of my iPhone 17 pro to iOS 27,

Not every issue an individual encounters on their device can be attributed to an iOS update. iOS 27 or later may have coincided with what you are experiencing, but that does not mean the issue was triggered by iOS. Coincidence in timing is not, by itself, evidence of causation.

If the update itself were the root cause, then every device running that same version of iOS would exhibit the identical problem. In such a scenario, the forums would be flooded with countless posts reporting the same malfunction, creating an unmistakable wave of complaints that no one could possibly overlook.

The absence of such widespread reports strongly indicates that the issue is not a general, system-wide problem with iOS 27 or later, but rather something specific to the individual device, its configuration, installed apps, settings, hardware, or another interacting factor.

In short: iOS 27 or later may be a coincidence in timing, but there is no basis to conclude that iOS itself triggered the problem simply because the issue appeared after the update.

Me too

Me too on iPhone 16 pro