I'd like to try my first 64/32 bit upload to the Playstore, but it looks like I need to upload a signing key.
IGoogle says I must be enrolled in App Signing. I can see the Tab named App Signing, but it's unclear to me how to proceed.
Would I need to use the same key as was used for the existing app? To make sure it's a valid update to an existing app?
Export something from the Provisioning tab in the Project Options?And how to upload? Google gives me examples based on Android Studio and Java stuff. How about Delphi?
Maybe I missed something on the Wiki... If so, can someone provide me a link?Tia!John
The page athttp://docwiki.embarcadero.com/RADStudio/Rio/en/Submitting_Your_Android_App_to_Google_Play#Android_App_Bundle_Support
mentions the option "Let Google create and manage my app signing key (recommended)"But I don't see this option?
I am simply adding my voice to yours John. I am ready to put an Alpha version on the Google Play Store. The only link I found for using Delphi to upload the App Bundle does not appear to show the new way of letting Google handle the key for you. Here is the link I was looking at:http://docwiki.embarcadero.com/RADStudio/Rio/en/Submitting_Your_Android_App_to_Google_PlayIn order to work with adds or payments you need an ID. You get the ID by uploading the app to the Google Play Store. I want to do this as an Alpha version so I can get the ID, then use the ID to implement adds and payments. Only when all of this is done will the app be ready to go out for people to use.I hope someone at Embarcadero will be able to help with this soon!
Hi Absa,Yes, they're probably very busy solving issues with the new Rio release. Lots of things we testers should have tested in the beta but didn't dare to do so because afraid to break existing code, connections to paserver on the Mac, trouble with the Stores etcetera Let's give it some time. We still can upload 32 bits apps :)
I think I got it....1. Download the PEPK-Tool that Google offers on the app-signing page2. Put it in the same directory as where your keystore file is. (if you uploaded APK's before, you can find this directory under Projects/Options/Provisioning and make sure you select the release configuration, Android 64 bit Application Store.)
3. Open a command-prompt and navigate to this directory4. copy/paste the command that google suggests, like java -jar pepk.jar ......make sure to completely copy it, including the encryption key5. replace the foo.keystore with the name of your keystorefile (path not needed, you're in the directory)6. Replace the alias foo with your aliasname as also visible on provisiong-page of your android project7. provide a file name for the output. I just used epk8. Press Enter, the command is executed and asks you for both the password of the keystore and if set, the password for the alias..It now generates the file 'epk' that you can upload to Google using the App Signing Private Key upload button.I could upload my AAB-file now and Google accepted. I have not tried to publish the app yet, I just wanted to try if I could get passed the upload...
I am working on using a switch component in an FMX frame and I want to change the color of the button. There seems to be no property for that. There also seems to be no "edit custom style" for anything. I think it may be because I am using a frame... I will have to look into that...Any other ideas?
Thanks for the info! The app signing page you mentioned is... under the app page for the app on the web site? I have never managed to get anything accepted on the google play store yet. A detailed accounting of everything required, step by step, would certainly be helpful. Better yet, the tools should be able to handle more of this on their own.
Put a switch on the mainform and edit the customstyle. It will propagate to the frame.
afterwards you can delete it from the mainform
Thanks. I thought I vaguely remembered something about that. It would be nice if they just got the styles to work on the frames. Frames are an integral part of advanced UI design. They need to stop treating them like second class citizens.
I tried doing that. It shows a Thumb property for the TBitmapSwitchObject. This property is a basic list of TBitmapLink. All that class has for published properties is CapInsets, Scale, and SourceRect. Nothing linking to a bitmap...The main TBitmapSwitchObject has no properties that seem to be any help in changing the color. Any ideas?