Problems logging in to Facebook on iPad A16

The latest Meta update to the Facebook app includes a bug that makes it unusable on the iPad. You will need to wait until Meta releases another update to fix the bug. Everyone else is experiencing the same problem with that update and in the mean time you can access Facebook on the web using Safari.

Beyond that report the issue to Facebook as that is what should always be done when there is a problem with the app. To be honest, it is unacceptable that Meta is not doing a better job testing their updates before they are released. It is apparent that is not being done, since there have been 9 updates to Facebook in just the last month and it is their users that are the bug testers.

You are likely seeing a known problem launching the current version of the Facebook App for iPad (version 563.0.0). This is not a problem created or resolvable by Apple - but is a problem introduced by the last Facebook update.

This Facebook release fails to launch correctly with the iPad in Landscape orientation. For those users struggling with this issue - try physically rotating the iPad from Landscape orientation to Portrait - then launch the Facebook App in Portrait orientation. The Facebook App may launch normally. After Facebook is running normally, you can rotate the iPad back to Landscape orientation if preferred.

Others have had some success by disabling WiFi while launching the App:

1. Disable Wi-Fi
2. Launch the Facebook app. It will quickly skip past the "Logging in" screen to another that has a big Continue button.
3. Re-enable Wi-Fi
4. Tap the Continue button.

In the meantime, until such time as Meta releases a fresh update to the Facebook App, you need to direct your complaints to Meta. Try posting lots of comments on the Facebook platform itself - as this might actually be noticed by the App Developer.

I was able to get around this on my iPad by using the Web version. Simply open Safari ... go to Facebook.com ... sign in ... and it works!

Good on you, Mac Jim. I wrote a similar response on this forum and got blocked! None of the remedies posted fixed the issue for me. Meta needs to do better.