wordpress-mobile / wordpress-mobile/WordPress-Android

Wordpress Mobile Issue

Open
#22,965 6 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

[Type] Bug
Dominant language
Kotlin
Stars
3.2k
Forks
1.4k
Avg merge
1d 11h
Merged PRs (30d)
69

Description

Description

WordPress Android App - "The provided site does not support Application Password authentication" Error

Error Message

"The provided site does not support Application Password authentication."

Issue Summary

The WordPress Android app has suddenly stopped allowing websites to be added. After entering a website URL, the app immediately displays the above error and never proceeds to the username/password login screen.

This issue started suddenly after previously working normally for at least two days. No deliberate changes were made to the affected websites, Android devices, or network configurations immediately before the issue occurred.

The issue initially appeared on one Android device and later appeared on a second Android device, suggesting this is not device-specific.

Environment

  • WordPress Android App
  • Multiple Android devices affected
  • Multiple independent Wi-Fi networks affected (Vodafone Broadband and BeFibre)
  • Mobile data connections continue to work correctly
  • WordPress iOS/iPad app continues to work correctly
  • Jetpack Android app continues to work correctly

Observed Behaviour

On Android Wi-Fi connections:

  1. Open WordPress app
  2. Add Site
  3. Enter site URL
  4. App immediately displays:

"The provided site does not support Application Password authentication."

The app never reaches the username/password login screen.

Troubleshooting Performed

The following tests have been completed:

Android App
  • Cleared WordPress app cache
  • Cleared WordPress app data
  • Uninstalled and reinstalled the WordPress app
  • Removed and re-added sites
  • Tested on multiple Android devices

No change.

Website Validation

Multiple websites were tested, including:

All produce the same error within the Android WordPress app.

Authentication Checks

Confirmed that Application Passwords are available and working:

  • Application Passwords section exists in user profiles
  • REST API is operational
  • /wp-json/ accessible
  • /wp-json/wp/v2 accessible
  • REST API advertises Application Password support
  • authorize-application.php endpoint exists and is accessible
  • Browser access to WordPress admin works normally
Network Testing

Results are consistent across devices:

Device / Connection | Result -- | -- Android + Wi-Fi | Fails Android + Mobile Data | Works iPad + Same Wi-Fi | Works Android Browser + Same Wi-Fi | Works Jetpack Android App + Same Wi-Fi | Works

This indicates that:

  • The websites themselves are accessible
  • Authentication endpoints are accessible
  • Browsers can authenticate correctly
  • Jetpack can authenticate correctly
  • Only the WordPress Android app fails
Additional Notes

The most confusing aspect is that the WordPress Android app previously worked correctly on these same devices and networks, then suddenly began reporting that sites do not support Application Password authentication.

The websites clearly advertise Application Password support via the REST API, and the same sites continue to work in browsers, the Jetpack Android app, and the WordPress iOS/iPad app.

This appears to be either:

  • A regression in the WordPress Android app
  • An issue with the Android app's site discovery process
  • An issue with the Android app's Application Password capability detection logic

Any assistance or confirmation of a known issue would be appreciated.

Step-by-step reproduction instructions

Just logging onto app, you can choose any website

Screenshots, screen recording, code snippet
Image
Environment info

Wordpress ver 7.0, mobile version 26.7

Please confirm that you have searched existing issues in the repo.
  • Yes

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the failure in the WordPress Android app using Wi-Fi and compare it with mobile data, where the issue reports that it works. Start by tracing the Android site discovery and Application Password capability detection flow. Done means supported sites no longer produce the error before the username/password login screen.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
authentication, mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.