wordpress-mobile / wordpress-mobile/WordPress-iOS

Enabling WordPress.com login results in error message

Open
#23,353 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

[Type] Bug Login Self-hosted Site Settings
Dominant language
Swift
Stars
3.9k
Forks
1.2k
Avg merge
23h 51m
Merged PRs (30d)
58

Description

Expected behavior

No error message is shown.

Actual behavior

The following error message is shown, but the setting appears to still work.

Steps to reproduce the behavior

Note: There may be simpler steps to reproduce, but this is what I did while running tests for the unsupported block editor.

  1. Create a new self-hosted site (I used JN) that's not connected to Jetpack and add it to the app.
  2. Using the web, create a block post with a table (which is unsupported at this time in the mobile editor).
  3. Edit the post using the app to see the "Unsupported Block Editor".
  4. Save the post and exit the editor.
  5. Using the web, connect the site to Jetpack.
  6. In the app, refresh the list of sites and ensure that the site from step 1 is selected.
  7. Edit the post and try to edit the table via the Unsupported Block Editor.
  8. You should be prompted that you need to enable WordPress.com login.
  9. In the Setting screen (from the prompt) toggle on "Allow WordPress.com login".
  10. Observe the error message.
Tested on iPhone 12, iOS 17.4.1, Jetpack iOS / WordPress iOS 25.1

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

No source file or repository test is named. Reproduce the flow on an iPhone using the unsupported block editor test case, then trace the WordPress.com login setting from the prompt through the Settings screen. Done means enabling the setting succeeds without showing the reported error while preserving the login behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios, swift
Domain
authentication, mobile
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.