# Changes to Google Play Store Build Upload Requirements

**URL:** <https://forum.adalo.com/t/changes-to-google-play-store-build-upload-requirements/15435>\
**Category:** Resources & Tutorials\
**Created:** [July 29, 2021, 4:25pm UTC](https://forum.adalo.com/t/changes-to-google-play-store-build-upload-requirements/15435 "2021-07-29T16:25:02Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![pford](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.adalo.com/pford/32/4648_2.png) [@pford](https://forum.adalo.com/u/pford)\
**Post date:** [July 29, 2021, 4:25pm UTC](https://forum.adalo.com/t/changes-to-google-play-store-build-upload-requirements/15435/1 "2021-07-29T16:25:02Z")

</div>

Hello all! Google has recently made a change (as of August 1st, 2021) to the app file types that are uploaded. The main difference is that .APK files are no longer accepted for new apps after this date, but can still be uploaded to update Play Store apps published before August 1st, 2021. Google’s new required format is an .AAB file which affords greater security, greatly reduced app size (~50% reduction or more), and greater control of your app releases should you ever leave Adalo or want to move an existing app _to_ Adalo.

No immediate action is required on your part as our devs have updated the build server to automatically generate the correct build file type based on if your Adalo app has builds before or after August 1, 2021. However, **please be sure to check the updated documentation for publishing to Google Play Store (see link below)**! As always, if you have questions or concerns, please post here in the forum or for major issues, please [submit a ticket](https://info.adalo.com/submit-a-support-ticket).

> **[Upload Your App to Google for Testing](https://help.adalo.com/testing-your-app/publishing-to-the-google-play-store/upload-your-app-to-google-and-create-your-store-listing)**
>
> Now that you have your app's build file, it's time to upload it to the Google Play Store so you can test it, market it, and release it to the world!

---

<div class="post-metadata">

**Author:** ![iAppsNi](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.adalo.com/iappsni/32/7851_2.png) [@iAppsNi](https://forum.adalo.com/u/iAppsNi)\
**Post date:** [July 29, 2021, 7:31pm UTC](https://forum.adalo.com/t/changes-to-google-play-store-build-upload-requirements/15435/2 "2021-07-29T19:31:20Z")

</div>

> [@pford](#):
>
> and greater control of your app releases should you ever leave Adalo.

Thanks a lot for this, I was worried about when this would happen. Just wondering what you mean by the above quote?

---

<div class="post-metadata">

**Author:** ![pford](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.adalo.com/pford/32/4648_2.png) [@pford](https://forum.adalo.com/u/pford)\
**Post date:** [July 29, 2021, 7:37pm UTC](https://forum.adalo.com/t/changes-to-google-play-store-build-upload-requirements/15435/3 "2021-07-29T19:37:39Z")

</div>

Good question! With APKs, all Adalo apps are signed by Adalo before they are packaged, but with the new AAB file, you get more control over the signing key and can revoke it at any time to keep better reins on who can publish a build to your Play Store bundle ID.

---

<div class="post-metadata">

**Author:** ![iAppsNi](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.adalo.com/iappsni/32/7851_2.png) [@iAppsNi](https://forum.adalo.com/u/iAppsNi)\
**Post date:** [July 29, 2021, 7:39pm UTC](https://forum.adalo.com/t/changes-to-google-play-store-build-upload-requirements/15435/4 "2021-07-29T19:39:58Z")

</div>

Excellent. The signing of keys has caught me out in the past switching from Native Dev to Expo to Adalo. Thats good news then also 🙂

---

<div class="post-metadata">

**Author:** ![pford](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.adalo.com/pford/32/4648_2.png) [@pford](https://forum.adalo.com/u/pford)\
**Post date:** [July 29, 2021, 8:13pm UTC](https://forum.adalo.com/t/changes-to-google-play-store-build-upload-requirements/15435/5 "2021-07-29T20:13:14Z")

</div>

Yes good point! This also makes it much easier to switch TO Adalo as well. I’ve updated the post to mention this as well. Thank you!

---

<div class="post-metadata">

**Author:** ![schalk](https://avatars.discourse-cdn.com/v4/letter/s/a9a28c/32.png) [@schalk](https://forum.adalo.com/u/schalk)\
**Post date:** [August 1, 2021, 6:59pm UTC](https://forum.adalo.com/t/changes-to-google-play-store-build-upload-requirements/15435/6 "2021-08-01T18:59:37Z")

</div>

Is there a way to replace your current app in playstore which is apk with .aab?

---

<div class="post-metadata">

**Author:** ![pford](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.adalo.com/pford/32/4648_2.png) [@pford](https://forum.adalo.com/u/pford)\
**Post date:** [August 2, 2021, 2:17pm UTC](https://forum.adalo.com/t/changes-to-google-play-store-build-upload-requirements/15435/7 "2021-08-02T14:17:29Z")

</div>

There is, but it requires opting in to Google Play Store app signing. It’s not difficult to do, but at the moment it does require that makers [submit a support ticket](https://info.adalo.com/submit-a-support-ticket). In the future, there will be a way for makers to self-service this process.

---

<div class="post-metadata">

**Author:** ![schalk](https://avatars.discourse-cdn.com/v4/letter/s/a9a28c/32.png) [@schalk](https://forum.adalo.com/u/schalk)\
**Post date:** [August 2, 2021, 3:54pm UTC](https://forum.adalo.com/t/changes-to-google-play-store-build-upload-requirements/15435/8 "2021-08-02T15:54:12Z")

</div>

Will .aab make app faster?

---

<div class="post-metadata">

**Author:** ![pford](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.adalo.com/pford/32/4648_2.png) [@pford](https://forum.adalo.com/u/pford)\
**Post date:** [August 4, 2021, 1:03pm UTC](https://forum.adalo.com/t/changes-to-google-play-store-build-upload-requirements/15435/9 "2021-08-04T13:03:07Z")

</div>

The smaller size could possibly improve speed some, but there’s nothing about the .aab itself that would increase speed dramatically. Mainly because much of your app’s functionality is handled off-device.
