Notices

Hmm, I don't know, go to xterm and delete the file /home/user/.zaploc/facebook.dat, e.g.

BTW, ZapLoc should be shown as "Zap's Location Updater for N900" in facebook.

I really don't know what is going on for you

What version of ZapLoc are you running?

/Z

FYI, Just checked by loading Zaploc on my N900 and it seems to check into facebook fine, so it's not a protocol issue. I'm betting it's a permissions issue on individual facebook accounts.

Also, good to know that the connection data for each service is in the .zaploc folder. Worst case if I can't connect to a service, deauthenticating and removing the files there should reset everything for that service, yes? Always good to know how to do that, since sometimes services change how things work under the hood and re-auth is needed to make it go.

I had problems with the N900 service updating pictures until I did this with that connection on FB and on the device. (And that was much harder, involving teh gconftool to remove entries. )

the facebook part of zaploc stopped working for me as well, whenever I tried to load up facebook places, it just had an error 404 frowny face something... and if I tried to go look at ATTACHED SERVICES it hung forever on the facebook part.

doing the
rm /home/user/.zaploc/facebook.dat
then re-authorizing has it back to normal, thanks :-)

Hi, thanks, this is working again now after doing the m /home/user.zaploc/facebook.dat too... although it didn't seem to have done anything the first couple of times I tried using ZapLoc after doing this? Kinda gave up and was scratching my head, then tried it again today on the off chance and it asked me to reauthorise and is now working fine again.

Thanks for your help.

Good.. it IS possible it was an issue on Facebook's end... I know they have been doing some strange changes to how the search returns results (for which I added a workaround in build 55) and maybe they broke someting else while mucking about with that? I dunno.

I try to make my software as robust as possible, but it's pretty hard to know what kind of errors various sites may decide to return in various conditions, there isn't like there is a magic "test mode" where I can force facebook to throw errors at my app for testing. (They should have exactly that, though, would help developers immensly)

/Z

Yeah I guess you're just having to react every time they go meddling with things without informing you what they've done! Thanks again.

Great app! Thanks so much for all the huge efforts developing and talking on here to us about it and debugging issues despite it only starting as a personal project. I started an app ages ago and got it basically usable before I lost the code for the latest version and then gave up..

I've been hunting for something like the Duke-Nukem-Forever-esque-in-delays (except that's now out, damnit) Shepherd that was in development to do locationy stuff and doing something when I'm at a place, so I'm wondering how easy it is to repurpose this to make it do something different instead of updating location-services. Queen Beecon now has location stuff but the docs don't make it easy and nothing else really matches it. I prefer the features this has to the latitude script that updates on cell-towers. Maybe I could strip unused parts out of the daemon and rewrite a UI (prob. in Gtk, or I'd learn Qt).


Excuse the long and aggregated-comments post, but having just read the whole thread...

You figured this out? I know there are ways using other tools/apps for the purpose. You probably haven't added any libs for a while to test this with.

Did you fix this? Wasn't sure from the posts between then and now - I think you could probably set a timer callback somehow or use the signal stuff to receive a SIGALRM with the appropriate system call (which there must be a python equivalent of). Or better ways..

Do you still exec a "ps" and grep/awk it? Do we have pgrep on maemo? (aha.. yes we do, answered my own Q!) That might be simpler if so (not sure how much detail you need). Simpler/less work for the system. Google for the man page/usage.

PS all working great, but the first run after I installed it, I went straight to Latitude and enabled it, then clicked the now-green Authorise button; it then just hung showing the busy 0101011-thingummy waiting animation. No browser opened, nothing happened at all. I had to kill it as the "Cancel" (or Abort or whatever it was) button didn't do anything.

When I tried again it did exactly the same thing; when on the next run (this is all having not yet rebooted the N900 since I installed it), I went to facebook places first - that worked just fine. Once I'd auth'd facebook, latitude then worked and opened a browser, but that might be a bug to look at. Unless my browser was just acting up (its the regular microb, no browser switchboard or anything I can think of that might mess with running a browser from an app).

If one removes the /home/user/.zaploc directory, apparently some other configuration breadcrumbs are left that lead to Zaploc not to recreate it and then authorizing services does not proceed after the browser window states it can be closed.

If one then creates /home/user/.zaploc directory manually, all works well.

Don't suppose you know why loads of Facebook places don't show up for me in the program? Case in point somewhere like "Bushey Railway Station"

Additionally, Latitude shows up no icons whatsoever, even for places that have places in Google's database, like this pub.

...any ideas?