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
In Google Play - Release Azure devs ops task version 4, there doesn't seem to be any support for adding the legacy apks' mapping.txt file automatically if we choose the Action to be "Upload multiple apk/aab files".
Since app bundles file itself contains the mapping.txt file, we need a way to upload mapping.txt file for legacy apks. Is this a limitation from Googe Dev Console?
The text was updated successfully, but these errors were encountered:
In Google Play - Release Azure devs ops task version 4, there doesn't seem to be any support for adding the legacy apks' mapping.txt file automatically if we choose the Action to be "Upload multiple apk/aab files".
Since app bundles file itself contains the mapping.txt file, we need a way to upload mapping.txt file for legacy apks. Is this a limitation from Googe Dev Console?
The text was updated successfully, but these errors were encountered: