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
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.
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.
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
Awesome glad you got it working!
1 Like
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:
And the one that doesn’t work
I wonder if its to do with the different installations on the macs.
Thanks
Joe
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+
Hello @CharlieAnderson ,
How you are well. Sorry to bring this up again but we are still struggling with our macs to get this to run.
The script hangs when you click allow and no code is returned. Everything seems up to date.
If there is anything you can do to help with this that would be great. More than happy to arrange a teams call if that helps?
Kind regards
Joe
hi @joeleveson in reality native app is not the proper way to authenticate via python since it needs to be registered at the OS level, which is more akin to typescript or electron (my hack essentially just used electron to do this) to be able to handle the callback. I would recommend WebApp or SinglePageApp instead, but will require you to host a server for the callback.
Otherwise you can view the dev tools console in the webbrowser where it was authenticated and it will give you the auth code to use to exchange for an access token (it will error out and say it can’t access that url but it will contain the code= in the url that you need)
Thanks for your reply Charlie. There is no error in the console it literally just hangs and returns nothing.
Its strange as it works on one of our macs but not the others.
Just wondering, is it possible to turn off the authentication and directly upload like before the update to v4 or is it essential now?
Thanks
hi @joeleveson weird that it works on one machine but not the other. Sounds like something claude code could tackle to see what the solution might be.
Just wondering, is it possible to turn off the authentication and directly upload like before the update to v4 or is it essential now?
If your account was forced migrated, we still allow the dev tokens to work, but it is a temp solution atm. I have an update to the python SDK coming soon that should help with auth.
1 Like
Thanks for your response Charlie. On google chrome it does try to redirect to the full response but gives the error in the console:
Failed to launch ‘adobe…..’ because the scheme does not have a registered handler.
Trying and failing to find a fix yet no joy yet. Thanks