Skip to content

Conjugate command returns "Not in Wikidata" for valid verbs #598

Closed

Description

@catreedle

Terms

Behavior

Entering any valid verb in the conjugate input fields consistently returns "Not in Wikidata".

Expected Behavior: The app should display the correct conjugation forms for valid verbs.
Actual Behavior: All inputs result in "Not in Wikidata", even for known valid verbs.

This appears to be due to Scribe-Android now relying on data from Scribe-Server. The verbs data provided by Scribe-Server (via Scribe-Data) does not yet match the expected contract required by the conjugation feature.

Notes: Once Scribe-Data is updated to match the required contract, this issue may resolve automatically.
If the issue persists after the data update, we may need to investigate ConjugateDataManager or perform further debugging.

I’d be happy to investigate this further or collaborate with anyone interested 🙂

Device type

any type

Versions

latest

Activity

  1. added theissue type on Apr 9, 2026
  2. andrewtavis commented on Apr 9, 2026

    @andrewtavis
    Member

    Thanks so much for the issue, @catreedle! CC @angrezichatterbox and @ashb155 :)

    Will take us a moment to be able to work on this as we need the Scribe-Data update to be done, and then we need a Scribe-Server update after that. But hopefully at the start of next month we can foreseeably work on this.

  3. Mailos07 commented on Apr 14, 2026

    @Mailos07
    Contributor

    @andrewtavis I wanted to flag that I'm encountering the same issue while working on the onboarding tutorial. The tutorial's Verb Conjugation chapter relies on the conjugation feature working correctly, so this bug is currently blocking my ability to fully test and validate that section of the tutorial flow. I'll keep an eye on this issue and adapt my implementation once the fix is in place. Happy to help with testing once the data contract is updated!

  4. andrewtavis commented on Apr 23, 2026

    @andrewtavis
    Member

    Thanks for the confirmation, @Mailos07! Great to hear that you're working on the onboarding flows already! 🚀

  5. Mounil2005 commented on May 16, 2026

    @Mounil2005
    Contributor

    Hey, I'd like to work on this issue, can you pls assign it to me?

  6. andrewtavis commented on May 26, 2026

    @andrewtavis
    Member

    Thanks for checking in here, @Mounil2005 :) We're finalizing work on Scribe-Data and will be able to do a data update after that. From there we can start working on this issue 😊

  7. andrewtavis commented on Aug 8, 2026

    @andrewtavis
    Member

    Assigning this to you @angrezichatterbox as a way to check to make sure that all data is being integrated properly into the application. I assume that this will be the last issue that we do before release, with this issue depending on the following for Scribe-Data and Scribe-Server:

    Moving the above blocking issues to the description as well 😊

  8. andrewtavis commented on Oct 17, 2026

    @andrewtavis
    Member

    @prince-0408, assigning you here seeing as how #715 will close this :)

  9. andrewtavis commented on Oct 27, 2026

    @andrewtavis
    Member

    Note that closing scribe-org/Scribe-Data#725 and redeploying Scribe-Server should close this :)

  10. added
    blockedAnother issue is blocking
    and removed
    blockedAnother issue is blocking
    on Oct 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

-next release-Included in the next releasehelp wantedExtra attention is needed

Type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions