API has changed - leads to LoginError

Open
#8 17 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
32/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
api, backend

Research direction

Start with both linked pastebin artifacts: run the reported snippet and compare the current traceback with the expected output. Then locate the library’s login/authentication path and determine which changed Google Voice API call causes the LoginError; no specific files or tests are named in the issue. Done means the snippet no longer raises LoginError, ideally with a regression test covering that login flow.

Written by the indexing model from the issue text.

Description

bug help wanted

Whenever I try to run this code I get this error
I have tried searching for solutions but most are a few years old and didn't work.
Any help would be appreciated

Dominant language
Python
Stars
134
Forks
40
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from jaraco/googlevoice

All issues in jaraco/googlevoice

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.