You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I will make sure to have the issue written in English with an English title.
I made sure that there are no existing issues - open or closed - which I could contribute my information to.
I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
This issue contains only one bug.
App version
1.1.1
Android version
None
How did you download the software?
Github (Release)
Bug description
The key used to sign the apk is changed. The user can't update to 1.1.1. Since reproducible build is enabled, F-Droid build also uses your key. Is the old key lost?
Steps to reproduce the bug
Install 1.1.0 then update to 1.1.1.
Expected behavior
No response
Screenshots/Screen recordings
No response
Logs
No response
Additional information
No response
Terms and Conditions
I have read all the rules above and filled in the requiered fields to the best of my ability.
I accept that if I fail to follow the rules stated above that I will recieve a 30 day block.
Yes that key is lost as the computer I signed with had damaged the file and I didn't have a backup so I had to make a new one but I updated from the GitHub releases on my own phone fine so didn't think it would break anything else this time I have backed up the sign key.
Activity
Gitbot-Actions commentedon Jun 28, 2023
👋 Thanks for reporting!
We will get back to you soon about this issue.
CreativeCodeCat commentedon Jun 28, 2023
Yes that key is lost as the computer I signed with had damaged the file and I didn't have a backup so I had to make a new one but I updated from the GitHub releases on my own phone fine so didn't think it would break anything else this time I have backed up the sign key.