About16 y/o hobbyist developer.
Joined devRant on 6/4/2017
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Sometimes, certain features don't work in my app if it's uploaded to the production track in Google Play.
It works in debug mode.
It works in release mode.
It works in the internal testing track.
...but it won't work in the production track? Y'know, the one that actually matters? Theoretically, there shouldn't really be a difference if the same exact APK was uploaded to the internal testing and production track, but... idk dude.
As a result, I implemented a secret way to test a feature in the production build (it's an app to remotely control OBS Studio): if the first connection you added is named "yayeet_" and you open the disclaimer, it tests the feature. Luckily, I got some of the stuff figured out, but I just thought the way I had to test it in production was dumb.1
>commits to gitlab
>writes some extra stuff
>"resetting to previous commit should work"
>everything's broken on the previous commit
I'm still trying to process how this is even physically possible.10
My experience while learning C#:
>trying to print an HTML element of a website to console
>changes a few things in code
>runs code multiple times
>still doesn't work
>looks closely at code
>wait a second
>walks to wireless printer
>finds nearly 10 pieces of paper on the floor
>I hate myself5