Sure! @Shein These are the steps I followed, although if you can avoid the 3rd party service for the 1st step then avoid it…
-
Package app as .aab file - Google requires this file type and no longer allows uploading of .apk files.
For this step I paid for the services of www.webtonative.com - If you have the software to package the app yourself, do that instead because the file you receive from webtonative has some of the build elements locked on their servers. This means that you’d be unable to edit certain things in android studio afterwards, which is a royal pain. Right now I want to change the app’s play store splash screen but it’s tied the .aab build so I’d have to pay an extra $9 to change it through webtonative. -
Create a Google Play Developer Account - be ready beforehand with 2 forms of national identification that BOTH have your names written identically and one with your address which needs to be the same address entered in your initial account set-up. Be careful with this because everything needs to be consistent for them to verify you. I don’t believe using an ID that says John Anton Doe can be verified by another ID that says John A. Doe.
I followed iRekha’s videos throughout the process, which was super helpful (https://www.youtube.com/watch?v=L9sU_aGeQEY&t=1127s). I suggest you follow her advice on how to draft your Privacy Policy as well because it worked for me… The online policy generators were wayyyy too wordy, convoluted and added things that didn’t apply to my app into the policy! 
-
Find 20 people to test your app for 14 days continuously. - You will need them for the mandatory closed testing. I suggest finding people you know so that you can remind them regularly to open and use the app. Please note that your Google play console actually records the apps usage everyday so if the testers don’t actually use the app, it’ll show up in your statistics and you might have to redo the testing period.
-
Begin closed testing. - refer to iRekha’s videos again if needed.
-
Apply for production access. - In the post-testing questioneer, I recommend word counts >200 to answer requests for descriptions or explanations.
-
Publish your app. - If you are granted production access, go ahead and create your release by promoting your app from the closed test to production. Since your app is PWA, you shouldn’t need to rebuild a new .aab file since everything will be current as you update in the Glide editor - unless you want a new splash screen from webtonative or something like that.
Good luck!