-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
-
0.11.1
Since 0.11.0 all our mapping.txt uploads with the plugin are not actually persisting that file in AppCenter. Logs say everything is fine, but when headed to AppCenter there's no mappings file.
16:35:13 File found matching pattern: **/app-production-release.apk 16:35:13 Symbols found matching pattern: **/mapping.txt 16:35:14 Creating an upload resource for app. 16:35:18 Create upload resource for app successful. 16:35:18 Creating an upload resource for debug symbols. 16:35:19 Create upload resource for debug symbols successful. 16:35:19 Setting metadata. 16:35:20 Setting metadata successful. 16:35:20 Uploading app to resource. 16:35:21 Upload app to resource chunk 1 / 2 successful. 16:35:23 Upload app to resource chunk 2 / 2 successful. 16:35:23 Uploading all symbols at once to resource. 16:35:24 Upload symbols to resource successful. 16:35:24 Finishing release. 16:35:25 Finishing release successful. 16:35:25 Updating release. 16:35:26 Updating release release successful.
We're calling it from our own Jenkins code with the appCenter(args) command:
def args = [ ownerName : ownerName, appName : appName, pathToApp : pathToApp, notifyTesters : notifyTesters, ] // Add optional debug symbols if (pathToDebugSymbols) { args.pathToDebugSymbols = pathToDebugSymbols } // Ensure we hide token withToken(tokenCredentialId) { // Enrich token args.apiToken = context.env.TOKEN // Post data context.appCenter(args) }
And pathToDebugSymbols has the ant string that is being showed above in the log (and actually finding files matching it, as logs also state) **/mapping.txt.
Version 0.10.1 works fine.
This is a big blocking issue for adopting 0.11 as our builds are done in the cloud so that mapping.txt file is not recoverable by any means and thus prevents to deobfuscate crashes reported in AppCenter.