LineageOS 14.1 and WiGLE WiFi Wardriving

Issues with the Android network detection software. Please include Software version, Android version, and device when reporting

22 posts • Page 2 of 2
new 2.25+ foss-master APK has been pushed to the repository for testing.

bobzilla++
Thank you, but would you mind compiling it ? I don't have the right tools to do that and it seems that this file hasn't been updated.
(or am I checking the wrong file? Sorry to be such a noob...)
Image
ah, sorry about that - it hadn't been updated yet - should be fixed now.
Sorry, I didn't find the time to test this early. I can confirm it's working now, good job and thank you very much for your hard work! Now I can stop uploading manually csv files :)

However, I can still see a stack trace in my logs while the app is booting. It's working nonetheless, so I guess it's just a minor detail (or maybe is it on purpose?...).

Gonna leave it here just in case : https://pastebin.com/cJ0QXBTe

Have a nice day!
Image
The exception on boot shows us that our work-around is working - we try and fail to initialize the old (standard) RSA keys, and if it bombs, we use AES - thanks for all the help.
Sorry for posting in an old thread, but this appears to still be relevant to the KeyStore error on FOSS 2.29 and master 2.48 (same exception). Running on Asus Zenfone 5 with an unofficial LineageOS 14.1 release.
After submitting the login form: https://pastebin.com/zmJPEcMk (Login credentials and auth key appear to be saved after the crash)
After attempting to view "Uploads" from the menu (or trying to upload): https://pastebin.com/mEGTsBMk
I can upload the errorstack files or test different versions, if that helps. If this LineageOS version is deemed obsolete or the issue stems from the ROM itself, that's also fine.
Edit: Also crashes with "Rankings" and "User Statistics". Deleting /storage/emulated/0/wiglewifi and reinstalling the apk or trying to create a blank "user-stats-cache.json" doesn't help one bit.
hm, when it fails, it shouldn't crash; we'll look into that.

Short version: deauthorize and re-authorize, you should be good-to-go.

Long version: we get stuck in these situations where the old cipher suite has been removed, but we never have both libraries on the same device at the same time to migrate the credentials. We'll work on making this more graceful, but unfortunately we can't prevent it entirely.

Thanks for the feedback, sorry for the difficulty.

22 posts • Page 2 of 2

Return to “WiGLE WiFi Wardriving Bugs”

Who is online

Users browsing this forum: No registered users and 2 guests