-
Notifications
You must be signed in to change notification settings - Fork 21
Invalid Requests #5
Comments
Are you using HTTP or HTTPS? The api will redirect you if you are using HTTP. I’ll add an error for this so that it’s a little bit more obvious. |
It seems like the application can't contact the server because of a 301 error, that could be fixed by talking to the server by Https, but the app can't do it. This result in the app not working at all: |
After further inspection, it seems that fetching messages does redirect OK, but it's impossible to subscribe to a service, as this is not redirected. Here is a screenshot of a packet sniffer, and you can see that there is only the "regular" http request, no encrypted one. |
Odd, is this the PlayStore build? |
I'll be rolling out a new build tonight, hold tight! |
I've got the message fetching to work by registering a new UUID to a service, then changing the UUID in the xml file to match the one I added But the "push" still doesn't work, I still need to manually update it. |
I'm having problems as well, trying to add a new service to my android phone using the PushJet app but replies with Network issue. |
Same problems here |
Can you please give us an update because the app completely unusable? |
Hey, sorry for the delay. I've sadly been incredibly busy with work and college lately. I'm looking at it right now. |
The issue should be fixed, I'm uploading a new APK to the play store in a minute. A new issue has been opened to address the core problem (#6). |
Have not had time to sign the binary yet. For now a unsigned by is is available. Remember to back up your subscriptions. It should sync them with the server upon reinstalling but it's better to be safe then sorry. https://my.mixtape.moe/hqjmwm.apk I'm sorry for the delay but I sadly have an extremely busy life. |
Everytime I tried to register to a new service, A notification told me there was a network error, so after installing a packet sniffer, I found out that the request sent by pushjet is invalid, and returns a 301, moved permanently.
A screenshot of these packets can be found here:
http://imgur.com/7pJ3gzo
Forgetting to put https at the front of the URL also causes this error (with cURL at least)
The text was updated successfully, but these errors were encountered: