Hey everyone,
I'm reaching out because I've hit a wall with my app. I had it running perfectly in production on version 1.5, but after pushing a new version with several changes (about 50 commits), certain games in the app just stopped working. I reverted back to my backup build of version 1.5, but oddly enough, it started showing the same bugs as the new version.
To troubleshoot, I pulled version 1.5 directly from GitHub, deleted and reinstalled `node_modules`, ran a new `yarn build`, and deployed it again. But it's still broken, just like the latest version.
Nothing has changed in the config files or the database. It's baffling because both versions worked perfectly in my test environment. What could be going wrong? Any insights would really help me out!
4 Answers
Have you checked your logs? They might give you some clues about what’s going wrong in production. Sometimes the errors are logged, and they can point you in the right direction.
I’ve run into a similar issue before where the deployment grabbed a cached version of the app instead of the latest one. Maybe it’s possible that something like that is happening here? Worth investigating whether you're actually deploying the newest code.
It might be worthwhile to take a look at your database. Sometimes new code can insert bad data or even delete crucial information. It's possible that your production database isn't in the state you expect it to be, which can lead to issues like you're describing. Also, keep in mind that something like a bad firewall rule could be causing problems, particularly if you can’t reproduce the issue in your test environment.
Is 1.5 really the only version you’re tracking? If you had more granular versioning, you could check the specific builds and ensure that what you’re deploying is correct. But I know that doesn’t help your current situation.
+1 for checking the database! Issues like bad data can be tricky to spot, and you’d hope the logs would shed some light on any failures.