-
Notifications
You must be signed in to change notification settings - Fork 2
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
AttributeError: 'Request' object has no attribute 'json' #13
Comments
|
Nevermind, the latest error is |
Trying this on a brand new Pebble and still getting the error. Any way to fix this @integraloftheday ? |
Hello! |
Hi! Yes, I have a config.json and have been through the above steps in Watch App Configuration. Just in case, I redid the key generation and reinserted it into my .json, and I'm still having the same error. |
Okay that’s good. What are you specifically doing on the watch when the
error occurs?
…On Thu, Jun 2, 2022 at 5:49 PM fn1y ***@***.***> wrote:
Hi! Yes, I have a config.json and have been through the above steps in
Watch App Configuration. Just in case, I redid the key generation and
reinserted it into my .json, and I'm still having the same error.
—
Reply to this email directly, view it on GitHub
<#13 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALFJMVE4BBEO2Y2M6XWW7YLVNFJAJANCNFSM5W6IY6FQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I go to Settings > Data Fetch. My pebble gives me a “Server cannot be reached” error while the aforementioned appears in my Mac terminal at the exact same time. |
Are you using http or https? Sorry for all the questions just trying to
debug!
…On Thu, Jun 2, 2022 at 6:23 PM fn1y ***@***.***> wrote:
I go to Settings > Data Fetch. My pebble gives me a “Server cannot be
reached” error while the aforementioned appears in my Mac terminal at the
exact same time.
—
Reply to this email directly, view it on GitHub
<#13 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALFJMVFGS7JXTYBCDYKL3FDVNFNC3ANCNFSM5W6IY6FQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Https, I'm using port forwarding for global access. No need to apologise! |
I think I should mention that before I set up port forwarding I was still getting the same error. |
By chance are you using the version of the app present on the rebble store? Or did you side load the version from the github. |
I actually have tried both, but right now I'm on the version side loaded from Github. |
The side loaded version from GitHub should be the one you want. This is odd, not an error I have encountered before. Could you share your config.json file, with the key field redacted. |
Alright, here it is
|
Everything looks good there... I don't have a current server set up right now, so I can't try to do a full debug until 6/11ish. |
Alright, here's what was printed (followed with the error) |
Is the key actually in an array, or is it how you redacted it? |
I redacted it like that, the key is actually "key":"value" |
Any updates? I understand this might be a tricky problem, I'm completely alright if it can't be fixed |
My Pebble will find my Mac on my network but won't connect. I keep getting error AttributeError: 'Request' object has no attribute 'json'.
Sorry if this is a stupid mistake on my part, I've found this tricky to set up.
The text was updated successfully, but these errors were encountered: