After the SSL certificate update, is it sufficient to simply rebuild and upload it to the store again?

Solar2D General Questions/Discussion
#1

Hi everyone, I’ve recently encountered a problem and hope someone with similar experience can help me solve it.

SSL certificates need to be reissued annually according to regulations. I have a utility app on the Play Store, but it’s currently unable to connect to MongoDB to store or retrieve data.

My desktop version works fine, indicating that my server is functioning correctly after an update, but the Play Store version seems unable to read the new certificate.

Furthermore, I accidentally lost my keystore when I switched to a new computer three months ago, so I can’t perform update tests now.

I’m hoping someone familiar with similar issues can tell me if rebuilding a new version of the AAB file and uploading it to the Play Store will allow it to read the new certificate?

Thank you.

#2

If I understand you correctly, you’re missing the upload key that issued the AAB to Play Console?
See How to request a new upload key - Google Play Developer Community

#3

Yes, the app I uploaded was only for testing purposes, and after switching to a new computer, I didn’t retain the original keystore, which prevented me from uploading it.

The Play Store doesn’t allow me to apply for a new key, so I had to abandon the app.

That app is connected to my personal server, using MongoDB to store and retrieve data.

My server’s SSL certificate expired after a year, so I replaced it with a new one, which worked fine in the new environment.

However, the Play Store version is still reading the old version. I’d like to know if rebuilding the app and re-uploading it will fix the problem?
Since I can’t test it myself, I hope someone with similar experience can share their findings. Thank you.

#4

Most likely is it an invalid keychain. Go to SSL Labs to verify.

PC browsers can auto-correct an invalid CA or root cert but mobile devices fail.

I had this with a new cert where the CA had changed and I was still using the old CA.

2 Likes
#5

Hello, thank you, the problem is solved.

I originally wanted to say that I had already tested this website yesterday and there were no problems, but I only tested one of my two servers, and the other one that wasn’t tested had the problem.

The problematic server seemed to have a problem with its key format; the number of lines was different from the working one.

After I redirected it to a new domain and reconfigured a clean key and CRT file, it worked fine.

Thank you very much.