We have moved to a new Sailfish OS Forum. Please start new discussions there.

Revision history [back]

click to hide/show revision 1
initial version

posted 2014-11-19 03:11:25 +0200

c:geo OKAPI authorization fails

I cannot get c:geo to consider itself authorized on http://opencaching.pl through OKAPI , and wondering if there is any known solution.

The app works fine in all aspects except the authorization step through 'OKAPI' ( http://opencaching.pl/okapi/introduction.html ) necessary to post to the opencaching website from the app.

In the app, upon clicking 'Authorize c:geo', and 'Start again', it opens the browser and loads the website in Sailfish' default browser. However, nothing happens upon clicking on 'I agree' button on the website. As if the app was expecting some data returned from browser, but getting none. Subsequent attempts simply load empty page. Clearly the website thinks the app authenticated just fine, ar the c:geo is listed as authenticated in my profile.

For comparison, on an Android phone clicking 'I agree' on the website takes me back to the app which receives some sort of authentication data and stores it in data/data/.

c:geo OKAPI authorization fails

I cannot get c:geo (an android geocachign app) to consider itself authorized on http://opencaching.pl through OKAPI , and wondering if there is any known solution.

The app works fine in all aspects except the authorization step through 'OKAPI' ( http://opencaching.pl/okapi/introduction.html ) necessary to post to the opencaching website from the app.

In the app, upon clicking 'Authorize c:geo', and 'Start again', it opens the browser and loads the website in Sailfish' default browser. However, nothing happens upon clicking on 'I agree' button on the website. As if the app was expecting some data returned from browser, but getting none. Subsequent attempts simply load empty page. Clearly the website thinks the app authenticated just fine, ar the c:geo is listed as authenticated in my profile.

For comparison, on an Android phone clicking 'I agree' on the website takes me back to the app which receives some sort of authentication data and stores it in data/data/.

c:geo OKAPI authorization fails

I cannot get c:geo (an android geocachign geocaching app) to consider itself authorized on http://opencaching.pl through OKAPI , and wondering if there is any known solution.

The app works fine in all aspects except the authorization step through 'OKAPI' ( http://opencaching.pl/okapi/introduction.html ) necessary to post to the opencaching website from the app.

In the app, upon clicking 'Authorize c:geo', and 'Start again', it opens the browser and loads the website in Sailfish' default browser. However, nothing happens upon clicking on 'I agree' button on the website. As if the app was expecting some data returned from browser, but getting none. Subsequent attempts simply load empty page. Clearly the website thinks the app authenticated just fine, ar the c:geo is listed as authenticated in my profile.

For comparison, on an Android phone clicking 'I agree' on the website takes me back to the app which receives some sort of authentication data and stores it in data/data/.

c:geo OKAPI authorization fails

I cannot get c:geo (an android geocaching app) to consider itself authorized on http://opencaching.pl through OKAPI , and wondering if there is any known solution.

The app works fine in all aspects except the authorization step through 'OKAPI' ( http://opencaching.pl/okapi/introduction.html ) necessary to post to the opencaching website from the app.

In the app, upon clicking 'Authorize c:geo', and 'Start again', it opens the browser and loads the website in Sailfish' default browser. However, nothing happens upon clicking on 'I agree' button on the website. As if the app was expecting some data returned from browser, but getting none. Subsequent attempts simply load empty page. Clearly the website thinks the app authenticated just fine, ar the c:geo is listed as authenticated in my profile.

For comparison, on an Android phone clicking 'I agree' on the website takes me back to the app which receives some sort of authentication data and stores it in data/data/.