To update the app in Google Play Console, build the app via your admin portal, upload the required Firebase SDK file if needed, download the AAB file, and handle permission errors using provided video links. Submit the app for review,
Follow the below steps to update the App in google pay console.
Step 1: Access your school admin portal.
- Go to your school admin portal.
Step 2: Navigate to the "Mobile Apps" section.
- Under "Websites & Apps," select "Mobile Apps."
Step 3: Initiate the app build process.
- Click on "Build App."
Step 4: Proceed without changes.
- Do not make any changes and click "Next."
Step 5: Upload the required files.
- If the "Next" button is not clickable, it means you may have missed a previous update from us. In that case, you'll need to add an additional file that must be generated in your Firebase account. For instructions on how to generate and upload this file, please refer to this article: https://support.learnyst.com/deprication-of-cloud-messaging-api-legacy-and-updation-of
- Once you've uploaded the Firebase Admin SDK file, continue following the steps outlined in this article to avoid any confusion.
Step 6: Continue without changes.
- Again, do not make any changes and click "Next."
Step 7: Submit the build.
- Click on "Submit build."
Once the app is built, proceed with the following steps.
- Step 8: Download the AAB file.
- Step 9: After downloading the AAB file, initiate the app release process in the Google Play Console.
- Step 10: Navigate to the Google Play Console using this link: https://play.google.com/console/about/?utm_source=google&utm_medium=cpc&utm_campaign=PMAX&utm_term=%7c&utm_content=&gad_source=1&gclid=Cj0KCQiApOyqBhDlARIsAGfnyMocibnay1oaKr5fhvDfZC3Xsq5AJ09EgXKPCYucYZmgkkiQo-WJ0Q8aAjOeEALw_wcB
- Step 11: Click on "Go to Play Console."
- Step 12: Select the account in which the app is created.
- Step 13: Choose your developer account (we've selected Learnyst).
- Step 14: Select your app (we've chosen Nomigrat).
- Step 15: You'll be redirected to the dashboard.
- Step 16: Navigate to production.
- Step 17: Click on "Create New Release."
- Step 18: Scroll down and click on "Upload."
- Step 19: Select the AAB file downloaded in the earlier step.
- Step 20: Wait for the AAB file to upload; this may take 5 to 10 minutes depending on internet speed.
- After uploading, you'll see the bundle below. now click the next button.
- Step 21 : Here, you can see a few errors. To solve the Intent permission error, click the Go to declaration button.
- Step 22 : You will land on this page. now select the Other option and Click the Save button.
- Step 23 : Once you click it, the overview pop-up will appear on the screen. Simply click the Not Now button.
- Step 24 : Now go back to the previous page. to solve the foreground service permission error, click the Go to declaration button.
- Step 25 : Now you will land on this page. to customise the connected device option, select the "Other".
- Once you select it, it asks video link and description.
- For that, paste the following video link and description.
- Video Link -https://drive.google.com/file/d/1p5dv6qMRXgQJOZVuJHtrSgcc41d5ZZzS/view?usp=sharing
- Connected device description: We are using "FOREGROUND_SERVICE_CONNECTED_DEVICE" permission for Many users connect Bluetooth headphones, headsets, or speakers to their phones during Zoom calls. The SDK needs the permission to route audio to and from these Bluetooth devices".
- Likewise, select the other option for the Microphone, paste the same video link in the field and enter the below description in the description field.
- Video Link -https://drive.google.com/file/d/1p5dv6qMRXgQJOZVuJHtrSgcc41d5ZZzS/view?usp=sharing
- Microphone description - We are using "FOREGROUND_SERVICE_MICROPHONE" for Zoom meeting, participants need to speak and listen in real time. The SDK accesses the microphone to capture the user's voice and transmit it to other participants.
- Likewise, select the other option for the phonecall, paste the same video link in the field and enter the below description in the description field.
- Video Link -https://drive.google.com/file/d/1p5dv6qMRXgQJOZVuJHtrSgcc41d5ZZzS/view?usp=sharing
- Phonecall : We are using ConnectionService API for handling call connections in its architecture. The ConnectionService API is part of the Android Telephony framework that allows applications to manage phone calls more efficiently. This API provides functionalities like managing call states, holding and unholding calls, and merging calls, which are crucial for any video conferencing or VoIP application, such as those built with the Zoom SDK.
- Once you have entered the necessary details, click the Save button.
- Now the overview pop-up will appear. Simply click the Not Now option.
- Step 26 : Here, you can see a few warnings. To solve the photo and video permissions waring, click the Show more option.
- Step 27 : Now under "All developers requesting access to the photo and video permissions are required to tell Google Play about the core functionality of their app"
click on "Go to declaration" - Step 28 : Here we need to explain why we are using video and image permission.
A . For Read media images copy the below given description and past under "Describe your app's use of the READ_MEDIA_IMAGES permission". - Description : We have removed the android.permission.READ_MEDIA_IMAGES permission in the latest version of the app that is being published.
B. For Read media video copy the below given description and past under "Describe your app's use of the READ_MEDIA_VIDEO permission". - Description : We have removed the android.permission.READ_MEDIA_VIDEO permission in the latest version of the app that is being published.
- Step 29 : Now click on The "Save" Button.
- Step 30 : Now select "Not now"
- Step 31 : Now scroll up and select "Review release".
- Then, go back to the previous page. now you can ignore the warning and click the Save button.
- Now the overview option will appear. At this time, click the Go to Overview button.
- Now you will land on this page. Now review the changes by clicking the send 2 changes for the review button.
- Now click the Send changes for review option.
- The review process takes 24 hours to 7 days. Please be patient while the app goes live; most of our apps are live within 24 to 48 hours.