Loading ...Argh. It appears that the ad provider we were using decided to make a change to the format of the URLs they were providing to us. They used to send the entire URL (protocol, host, and all). Now they’re just sending relative paths. Unfortunately, every version of Encountr from the past 8 months or so depends upon being handed the full URL.
It took me a few days to notice, because the only time this particular ad even gets USED is when you’re launching Encountr for the first time after (re)installing, or after logging in and pulling your profile to a new device.
The long and short of it: I have to fix and release a new version of Encountr today. There’s nothing whatsoever I can do to retroactively fix copies that are already installed. Well, OK, I’m going to beg the ad network to change back to the old format for at least a few days, but I put the likelihood of that actually working at around .0001%. If your version of Encountr crashes immediately upon launch (or lives long enough to fetch nearby guys and starts displaying them, then crashes), you have to get the new version.
Lesson learned: never, ever allow the app to break if a thirdparty extension over which we have no control breaks. Anyway, I’m working on getting it fixed, and should have 2.96 ready by 8pm Eastern.
