Setting up Frameio v4 for python

Help
,
21

Hi @CharlieAnderson ,

Thanks for the update. Still having the same problem unfortunately. I find directory to write the data to doesn’t play ball on line 43:

DATA_DIR = Path.home() / ".frameio-oauth"

It doesn’t write anything. Changing it to this fixes it.

DATA_DIR = Path.home() / "frameio-oauth"

However, nothing happens when it is run. It just prints:

Waiting for you to sign in and authorize..

Though not sure if the FrameioOAuth is looking for the path. I’ve renamed it to .frameio-oauth after writing it to text and it doesn’t hang it give me this in the shell:

Details: Did not receive redirect within timeout

Many thanks

Joe

22

Hi @joeleveson thanks for the detailed info. I’ll see if I can spin up a ubuntu VM so I can better test to get this working before I open another PR.

23

hi @joeleveson I was able to fix the issues and confirmed it working on my ubuntu vm. Please pull the latest from main and rebuild. Please note this won’t work for headless, it needs to have access to the browser on the desktop to auth.

cd frameio-python-oauth

git checkout main

git pull

cd electron-helper

npm run package:linux

cd ..

python src/cli.py auth

Let me know if you run into any issues! I might add headless support in the future but atm it’s desktop auth only.

24

Its good! Thanks very much @CharlieAnderson Sorry for the endless requests. Very grateful that we got there now and will great going forward with the new Frameio API. Many thanks

1 Like
25

Awesome glad you got it working!

1 Like
26

Hello @CharlieAnderson We’ve run into a slight problem with the FrameioOAuth.app on the mac. It runs fine on Linux and on our mac we use to test however it pauses on the other macs.

The webrowser opens and it goes to the allow user page as expected and goes to the next page. But unlike the working instance the shell just hangs and nothing happens.

This one is the details of the one that works:

working

And the one that doesn’t work

noworking

I wonder if its to do with the different installations on the macs.

Thanks

Joe

27

hi @joeleveson I’m unsure about the versions, but would guess it has something to do with needing Sonoma (I tested on Tahoe 26.2) as it requires Electron 35+, Node 18+, & Python 3.9+