Skip to content
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

Qt5 - QNetworkReply::NetworkError(ProtocolInvalidOperationError) #144

Closed
landas opened this issue Apr 27, 2017 · 4 comments
Closed

Qt5 - QNetworkReply::NetworkError(ProtocolInvalidOperationError) #144

landas opened this issue Apr 27, 2017 · 4 comments

Comments

@landas
Copy link
Member

landas commented Apr 27, 2017

This bug only show up when using non-english characters.

With the Qt5 build, I get the following error when writing back settings to movescount.

"writePersonalSettingsInThread error: " QNetworkReply::NetworkError(ProtocolInvalidOperationError)

Seems like the PUT-request is not supported or supported different in QNetworkRequest (Qt5).

return this->manager->put(req, postData);

This bug results in waypoints (POIs) added in the ambit2 user interface, gets just deleted when syncing.

I can confirm this is not a problem with Qt4 build.

@landas
Copy link
Member Author

landas commented Apr 27, 2017

This bug is related to #139.

When put-request do not contains non-english characters, the error does not show up.

landas added a commit to landas/openambit that referenced this issue Apr 27, 2017
@landas
Copy link
Member Author

landas commented Apr 27, 2017

This could still be a problem for log uploads to movescount.

@manisandro
Copy link
Member

Mh so I suppose everywhere we are constructing a QString ambit data we should be using fromLatin1?

@landas
Copy link
Member Author

landas commented Apr 27, 2017

This issue (network error) does only affect the navigation module for now (fixed). Log upload do not send custom text strings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants