new reseed cert missing? #14

Closed
opened 2025-04-21 14:44:34 -04:00 by idk · 5 comments
Owner

Installed 1.6.0 on a new phone, checked the warning logs, the reseed from incognet.io failed because ramber@mail.i2p unknown key. This was added into i2p.i2p trunk a couple weeks before the release. Android build should have pulled it in, please check your build if it did. Reseeds from other sites worked. If the Android build wasn't built from i2p.i2p trunk release tag that's not good. But the reseed URL and cert would have gone into trunk in the same checkin. So must be an android build issue?

Installed 1.6.0 on a new phone, checked the warning logs, the reseed from incognet.io failed because ramber@mail.i2p unknown key. This was added into i2p.i2p trunk a couple weeks before the release. Android build should have pulled it in, please check your build if it did. Reseeds from other sites worked. If the Android build wasn't built from i2p.i2p trunk release tag that's not good. But the reseed URL and cert would have gone into trunk in the same checkin. So must be an android build issue?
idk self-assigned this 2025-04-21 14:44:34 -04:00
idk closed this issue 2025-04-21 14:44:34 -04:00
Author
Owner

I hadn't updated the certificates_zip file since 1.5.0, which is why the certs were outdated. It looks like it does get updated automatically, but only if I run ./gradlew clean first. I must have simply forgotten to do that and just done ./gradlew assembleRelease.

I hadn't updated the certificates_zip file since 1.5.0, which is why the certs were outdated. It looks like it does get updated automatically, but only if I run `./gradlew clean` first. I must have simply forgotten to do that and just done `./gradlew assembleRelease`.
Author
Owner

ok, if that was the only file missing, wasn't a big deal, but a new release can't hurt.

You didn't say what the root cause was, but if, for example making sure the resources are current could be automated, or at least added to the release process document, that should be part of the fix, and documented here.

ok, if that was the only file missing, wasn't a big deal, but a new release can't hurt. You didn't say what the root cause was, but if, for example making sure the resources are current could be automated, or at least added to the release process document, that should be part of the fix, and documented here.
Author
Owner

Fixes are out to both repos. Closing.

Fixes are out to both repos. Closing.
Author
Owner

It appears that the resources were not updated in my last build. In the course of fixing it Google Developer Console informed me that we were potentially mishandling the unpacking of that resource file. https://support.google.com/faqs/answer/9294009 I fixed both and cut a new build based on the 1.6.1 tag. I have verified that the resources and libraries are correct and pushed updates to GPlay and started uploads to our F-Droid repository.

It appears that the resources were not updated in my last build. In the course of fixing it Google Developer Console informed me that we were potentially mishandling the unpacking of that resource file. https://support.google.com/faqs/answer/9294009 I fixed both and cut a new build based on the 1.6.1 tag. I have verified that the resources and libraries are correct and pushed updates to GPlay and started uploads to our F-Droid repository.
Author
Owner

Thanks for the report, two possible culprits, I'll figure out which one it is.

Thanks for the report, two possible culprits, I'll figure out which one it is.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: I2P_Developers/i2p.android.base#14
No description provided.