-
-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Photoframe authorization not found #197
Comments
It shouldn't disappear like that for no reason. One thing that "might" be causing it is poor power supply that over time has started to corrupt your SD card. Other reasons would be revoking the OAuth from google's side but that is usually a manual process. Feel free to attach a log to this ticket next time it happens using the "Log Report" feature and I'll have a look and see if I see something odd. |
I might have found an issue. Might be related to the loss of network |
I started the photoframe again and waiting for it to lose the auth for the logs. Which logs should I review? |
Running version commit af9881a
On branch master nothing to commit, working tree clean Aug 28 06:00:54 photoframe photoframe[345]: 2021-08-28 06:00:54,913 - INFO - Starting presentation Aug 28 09:24:45 photoframe rngd[257]: stats: FIPS 140-2 failures: 0 ThreadID: -1291860896File: "/usr/lib/python2.7/threading.py", line 774, in __bootstrap ThreadID: -1246641056File: "/usr/lib/python2.7/threading.py", line 774, in __bootstrap ThreadID: -1266682784File: "/usr/lib/python2.7/threading.py", line 774, in __bootstrap ThreadID: -1225773040File: "./frame.py", line 185, in ThreadID: -1256197024File: "/usr/lib/python2.7/threading.py", line 774, in __bootstrap |
Every two weeks or so the photoframe looses it's authorization json. When I look into the logs it just says not found. What causes this and anyway to resolve this?
The text was updated successfully, but these errors were encountered: