Crash when installing apk from file manager

This is the logcat after two crashes. Filtered with the string "fdroid"

(removed since it's attached in the comments)

Sorry about the garbage, i wasn't given an option to attach a file in the bug report. Here it is fdroid_log.txt

Edited the description to save space.

What did you do to get to this point? Did you upgrade from a previous version? If so, which?

My bad, i totally forgot to add some details. I have version 0.64-test installed. F-Droid wasn't open, i was installing some other app whet this popped up. I only got a message saying F-Droid had crashed, nothing else, not even the option to report it.

Definitely something to do with broadcast receivers and how they interact with the database. Ping @pserwylo, could you look at this?

Set the milestone to 0.65, since this is important to fix. Added tags too, never done that before here.

Sebastian, thanks for the bug report. Although I'm not quite sure what caused this, I can see how to fix it.

Out of curiosity, were you just installing a .apk that you had downloaded, installing from Google Play or somewhere else all together? F-Droid is indeed listening for when apps are installed, because it helps us when deciding to put them in the list of installed apps or not. The bug occurred when the Android package manager sent a notification to F-Droid, so that explains the F-Droid crash, even though it wasn't open. FYI - this doesn't mean F-Droid is perpetually running in the background, but rather it gets started by Android in order to notify it of package installs, and then closed again.

Yeah, i noticed by carefully reading the logcat. I was installing an apk, but it was from a file manager, neither F-Droid nor Google Play. Thanks for the info!

Glad i was able to help ;)

Status changed to closed by commit 71db32

That should fix it. We'll probably wait until we've polished off some of these other minor bugs before making a release that should fix this for you, but keep an eye out for updates.