having trouble for the first time while building my bundle with the key hash discrepancy my gradle.properties file stores the key pass and keystore pass, and when I build, it wants to escape the characters in my password... any solutions, what other info would be needed to help if so?

Who is "it"? Who tries to escape something? And what does it try to escape? Is the problem maybe that you have something in your password that you should have escapce in the

properties

file but forgot to do so?

My apologies, my brain was frazzled when I wrote this. I got it working this morning! Trying to build from the CLI, the build process wound up changing some of my data, namely I noticed it change the entries for my key store and password by escaping whatever special characters were there. In the future I will change my password to remove # and other like characters that were escaped. However, when IO built it from the GUI, it handled everything correctly, and didn't change any thing. CLI code I tried:

./gradlew clean bundleRelease --info

My key pass info was stored in gradle.properties. But unlike the GUI, I was not asked for my password info, since it's stored in my gradle.properties file. I assume I should upload the "signing key" by accepting Google signing, get the "upload key", then request an upgrade to the signing key once that's done. I signed this already with one key, not realizing my password was going to be an issue. I'm told this is the avenue of approach with the least resistance. Again, sorry for the request blasted like my mind was being read, but I basically felt that it was written so heavily all over my face that you could read it too from your end. 😵‍💫

Actually I still cannot really follow. Gradle has no GUI, so I don't even know what you refer to when you say "building from GUI". Usually, it should not make a difference whether you build something from CLI or through some other way and if it does it sounds like something is not setup correctly. A little bit between the lines it seems like you might talk about something related and specific to Android. Android is always "special" and I'm no Android guy. So maybe you would want to ask in #CJYS1DAP5 or some Android community instead if this is something highly Android-specific which I assume.

I apologize, while building my bundle through Android Studio Build > Build app bundle/apk > build bundle, there's a pop-up in said GUI that allows input/storage of said passwords for building the bundle, required by Google to be consistent for integrity. When I used that command I mentioned earlier from the root folder, the build process, whichever cuprit that functionally does it, began escaping characters from my pawword strings. I couldn't find a fix that stopped it from happening. Ill change passwords and it will be fine

Ok, what you could do is printing the password to stdout in the buildscript to see what was read from the priorities file. If it does not print the expected password, you probably stored it wrongly in the file. It if you change it anyway, you could share the password and what you have put to the properties file.