Add docs for Testing and publish on Google Play Store #2
Conversation
|
Use Dreamflow, not DreamFlow @pinkeshdarji |
Done! |
| :::info | ||
|
|
||
| - After the internal testing track is set up, Dreamflow can handle all future deployments directly. | ||
| - Even if the build status appears as FAILURE, you can still download the AAB file. |
There was a problem hiding this comment.
this should be a separate point / subheading like "Downloading AAB file"
its an important step and also a fallback if the build is not uploaded from dreamflow.
There was a problem hiding this comment.
Agree! updated accordingly.
|
|
||
| </summary> | ||
| <p> | ||
| For the initial deployment, you must manually upload the **.aab** file to Google Play Console to create the first release track. Once the initial track is set up, Dreamflow will handle all subsequent deployments automatically. |
There was a problem hiding this comment.
can link the "download the aab file" section here too. basically showing what to do if they had to manually do it?
|
@PoojaB26 you can review it again. |
|
|
||
| :::info | ||
|
|
||
| - If your device is not listed in the **Flutter Device Selection** dropdown, make sure you have properly completed the [**Android**](#android-setup) and [**iOS**](#ios-setup) setup. |
There was a problem hiding this comment.
i'm not sure we need to add this info because we don't handle flutter devices from our platform, so it depends on the IDE they use and they should look at the troubleshooting guide of that IDE. i'm removing it therefore. lmk if you feel otherwise.
3 participants
Description
Add docs for Testing and publish on Google Play Store
Linear ticket, Linear ticket, Linear ticket and magic word Fixes DEVR-1096
Fixes DEVR-1112
Fixes DEVR-1113
Type of change