You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Release this for RWB env. Testing in staging of RWB env would be sufficient. No need to release in open testing track since the app is not yet live and is in UAT stage.
When doing the previous release for RWB, a mistake was done with versionCode. To correct that, this line, should be changed to the below in the main codebase(for all flavors since maintenance is difficult) itself:
since when the bundle was generated lastly the versionCode in circle-ci env variable was mentioned adding 4 * 1048576 and another 4 * 1048576 got added by the build. And this issue was realised only after sending the app to review and it became irrevertible. Doing the above will not cause issue for us in future, considering google supports longer version codes as max.
As part of the steps mentioned here looks like just updating the RWB release tracker and tagging would be sufficient. No need to update release notes or merge. Make sure Avni tag for the commit in prod is rightly differentiated from the RWB tag and both updated in release tracker.
The text was updated successfully, but these errors were encountered:
since when the bundle was generated lastly the versionCode in circle-ci env variable was mentioned adding
4 * 1048576
and another4 * 1048576
got added by the build. And this issue was realised only after sending the app to review and it became irrevertible. Doing the above will not cause issue for us in future, considering google supports longer version codes as max.The text was updated successfully, but these errors were encountered: