I was an Android developer in a company, I was told to generate a release APK file to test it locally.

So, to sign the apk, I created a keystore file and the password is my name. they decided to publish the file on Play Store.

I left the company years ago, and still on every update they have to put my name as a password.

Client comes to me after a year to publish an update to his app.

I accept, start looking for my release key.... Found it.

Fuuuuuuucccck what's the password? I can't remember

Googled what to do if forgot password of keystore: Nope can't do shit other than brute Force. You've to forget your app and publish as a new app. Nice.

I must have written it somewhere... I'm sure. Check my password manager: Nope.

Start brute forcing:
Default pass: android. Nope
Name of app? Nope

After 10 mins of brute forcing:
Why would I not store the password in my password manager? The only reason I can think is the password is too stupid to be stored.

Try "password". App signed successfully.

I'm ashamed of 1 year older me xD

This is my worst day ever just formatted my laptop and forgot to backup my Android keystore........😤😤😬 Just visited stack overflow only to learn that without the keystore you can't make updates for your app.I will never update my apps on playstore now.... Shit. Am fucked totally...👹👹

I miss old times rants...So i guess, here it goes mine:

Tomorrow is the day of the first demo to our client of a "forward-looking project" which is totally fucked up, because our "Technical Quality Assurance" - basically a developer from the '90-s, who gained the position by "he is a good guy from my last company where we worked together on sum old legacy project...".
He fucked up our marvellous, loose coupling, publish/subscribe microservice architecture, which was meant to replace an old, un-maintainable enormous monolitch app. Basically we have to replace some old-ass db stored functions.
Everyone was on our side, even the sysadmins were on our side, and he just walked in the conversation, and said: No, i don't like it, 'cause it's not clear how it would even work... Make it an RPC without loose coupling with the good-old common lib pattern, which made it now (it's the 4th 2 week/sprint, and it is a dependency hell). I could go on day and night about his "awesome ideas", and all the lovely e-mails and pull request comments... But back to business

So tomorrow is the demo. The client side project manager accidentally invited EVERYONE to this, even fucking CIO, legal department, all the designers... so yeah... pretty nice couple of swallowed company...

Today was a day, when my lead colleague just simply stayed home, to be more productive, our companys project manager had to work on other prjects, and can't help, and all the 3 other prject members were thinking it is important to interrupt me frequently...

I have to install our projects which is not even had a heart beat... not even on developer machines. Ok it is not a reeeeaaally big thing, but it is 6 MS from which 2 not even building because of tight coupling fucktard bitch..., But ok, i mean, i do my best, and make it work for the first time ever... I worked like 10 ours, just on the first fucking app to build, and deploy, run on the server, connect to db and rabbit mq... 10 FUCKING HOURS!!! (sorry, i mean) and it all was about 1, i mean ONE FUCKING LINE!

Let me explain: spring boot amqp with SSL was never tested before this time. I searched everything i could tought about, what could cause "Connection reset"... Yeah... not so helpful error message... I even have to "hack" into the demo server to test the keystore-truststore at localhost... and all the fucking configs, user names, urls, everything was correct... But one fucking line was missing...
EXCEPT ONE FUCKING LINE:
spring.rabbitmq.ssl.enabled=false # Whether to enable SSL support.

This little bitch took me 6 hours to figure out...so please guys, learn from my fault and check the spring boot appendix for default application properties, if everything is correct, but it is not working...

And of course, if you want SSL then ENABLE it...
spring.rabbitmq.ssl.enabled=true

BTW i really miss those old rants from angry devs, and i hope someone will smile on my fucking torture

When you want to update your app on Playstore but you forgot your keystore password

Okay. So my dumbass boss took this project that had a steep timeline. I told him straight up, it won't work because we won't make the timeline. If we do this, I will be the one bending over backwards to deliver. I don't like to promise and fail. I got the oh don't worry let's just try. If we don't make it that's fine. Unfortunately that's not how I work. I refuse to deliberately fail. So I say okay and we begin. I suggested open source is the fastest way to deliver bit the fucked up part is, I am the only senior dev in the team. I will be expected to reverse engineer the open source app to connect our own deployment parameters. Use tech I have never used before. Connect frontend and backend. Handle dns bullshit. I have literally been working on Vibes and coffee for the past two weeks because ofcourse I ran into so many issues. Now I have an extension for Monday and I hate to fail. So I am not sleeping or resting just working on a fucking java app I didnt build and I am expected to make it work seemlessly on our production environment. I made some progress. Deployed frontend, deployed backend. Forgot to connect production dB so I decided to go with azure database for mysql driver since we have credits on azure. Now my java app is pissing itself over ssl handshake. I generate my keystore and add it and now java socket just times out. I want to pummel somebody or a punching bag that looks like my boss.

Made an Android app a while ago. I needed some pet project so I decided to go with Java for Android. First time, no experience at all.

So everything went ok, I had a little help from a colleague, structuring code, and pushing to the store. Work done app was doing ok.

A year later I came back to this project. I needed to fix a bug - date time and daylight savings crap. 😥

Spent a week on it. Ready to push a new version to the store, with some extra features! Build apk. All good.

Wait. I need to sign the APK? Wtf. I had to format my hard drive. How do I recover my fucking certificate?

*Google's for a while*

No fucking way. I can't restore the certificate. Or get the keystore back. The solution is to create a new app with a brand new package name?

Thanks for nothing, I'm done with Android development.

When I corrupted the keystore for my production android app apk. Oh the panic! I ended up uploading it again and telling the users to download the new app.

WHAT THE FUCK!!!
Whoever says that MacOS is superior or at least on par with Linux in terms of ease of maintenance -- feel free to stick a backwards pinecone up your asshole and push it down with a baseball bat with 5" nails.

The FUCK is this nightmare. You can't even start a process w/o logging in via GUI, password changes are another horror story, esp. for users who have never logged in [warning says to change keystore pass separately... Which doesn't exist...], vnc uses some proprietary protocol, ...

Seriously, even SunOS is easier to maintain, not to mention AIX, compared to this BSD nightmare of a UNIXoid....

Wtf....

Lost the keystore to one of my Android Studio projects...

Some of our applications use a Java keystore that requires a password. The password is encrypted and stored in a database. The applications retrieve it when needed, decrypts it and uses it. The password is..... password

Yesterday and today combined I spent about 8 hours trying to get my PGP / GPG passphrase to work. Absolutely magically, somehow a newline character had gotten into the passphrase. Yes. That's possible. On macOS, that is.

On my Windows machine I have the same fucking private key protected with the same password. Now try and get a non-windows newline character into any Windows password field, be it a command line or some GUI input. WTF! You'll lose a year of your life with every passphrase error while you have the actual passphrase.

So after all these hours trying to hack my own GPG keystore without success, I remembered how the private key got on my Windows machine in the first place: see tags.

Fuck...
Just recognized I whiped my keystore.

After not using Intel XDK for a year. I just noticed that they dropped support for this tool in early 2018 and removed all the keystores stored in their system.

Now I'm unable to update my android app because I don't have the key anymore.

And now soon google play will remove my app due to security issue on certain module.

I should've kept the keystore myself...
Oh well mistakes were made and lessons are learned the hard way.

Does anyone have any suggestion to retrieve a keystore file?

Why does symfony freezer the container after compiling it? I understand that because of its shit design they require to pre-compile the container because if they didnt their framework would be the slowest piece of shit ever and nobody would use it, but why freeze the parameter bag?

Load the compiled container from the cache, then let me override and set dynamic variables on top if I want, its just a keystore, so it just seems pedantic, unhelpful and utterly pointless

Correct me if I'm wrong but my understanding of Keystore file is like a passwords database for an app/s that need to connect to others servers over the network.

How though does each component inside the app know which entry to use from the file?

Me just now:
> finishes adapting an app for my purposes in android studio
Time to export a signed apk!
> successfully locates the keystore I generated a year ago
> even remembers the passwords
Nice! Now I can finally close Android Studio!

One second after I close it:
Shit, I forgot to enable dark mode
> reopens android studio

(The dark mode normally becomes accessible through in-app purchases, but since I built the app from source those don't work)