-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to upload the deobfuscation file #210
Comments
Hi @liumiaojq do you use self-hosted or ms hosted agent? Could you please also share logs in diagnostic mode? |
I'm using hosted agent. Can you let me know how can I get logs in diagnostic mode? Please note this only happens in our release to production pipeline and I'm not able to run it again until our next production roll out. |
@liumiaojq for release pipeline you can set System.Debug variable as 'true' - to enable diagnostic mode |
I'm able to repro when releasing to internal test track. Here are the logs in diagnostic mode: 2020-11-17T18:35:19.9693265Z ##[debug]Evaluating condition for step: 'Release to internal test debug' |
Hello, is there any progress? This still repros consistently. Let me know what I can help here |
@liumiaojq is 'D:/a/r1/a' intended to be deobfuscation file for you application? According to EISDIR error - it seems to be the directory instead of a file |
Hi @liumiaojq is this issue still actual for you? |
@liumiaojq closing this due to inactivity - please feel free to reopen or ask any further questions. |
@anatolybolshakov Sorry for late response. I got more clues from the logs. Can you reopen this issue? The extension correctly picked up the apk in the path I provided, but it attempted to find the mapping file in a different path: 2021-02-26T03:44:25.1457035Z ##[debug]Uploaded D:/a/r1/a/XXXXXX-CI/ProductionLtw21Release/XXX-1.12345.67.0.apk with the version code xxxxxx There is no way to specify a mapping file path in the parameter of the extension, so I have no idea why this path is being used here. Actually "ProductionLtw15Release" was a build flavor we used before and has been renamed to ProductionLtw21Release. we tried to reconfigure the build artifacts in release pipeline, but that doesn't help. |
@liumiaojq sure, reopening this - let us take a look |
Hi,
We have set up a ADO pipeline to release our app to Google play store and it works fine till today. We don't change anything but get the following error:
2020-11-13T00:31:27.8716691Z ##[section]Starting: Release to production 10%
2020-11-13T00:31:27.8850893Z ==============================================================================
2020-11-13T00:31:27.8851252Z Task : Google Play - Release
2020-11-13T00:31:27.8851563Z Description : Release an app to the Google Play Store
2020-11-13T00:31:27.8852020Z Version : 3.174.0
2020-11-13T00:31:27.8852275Z Author : Microsoft Corporation
2020-11-13T00:31:27.8853095Z Help : ms-resource:loc.helpMarkDown
2020-11-13T00:31:27.8853426Z ==============================================================================
2020-11-13T00:31:29.1414109Z 074b9815-d7e4-4077-9087-5781e70dc5cc exists true
2020-11-13T00:31:29.2248407Z Found main APK to upload: D:/a/r1/a/ProductionName-CI/ProductionFlavor/ProductionAPK.apk (version code 0000001)
2020-11-13T00:31:29.3277605Z Authenticated with Google Play and getting new edit
2020-11-13T00:31:39.6266541Z Found deobfuscation (mapping) file: D:/a/r1/a
2020-11-13T00:31:39.6360057Z ##[error]Unhandled: EISDIR: illegal operation on a directory, read
2020-11-13T00:35:39.6631398Z ##[error]Error: Failed to upload the deobfuscation file D:/a/r1/a. Failed with message: Error: socket hang up.
2020-11-13T00:35:39.6898489Z ##[section]Finishing: Release to production 10%
I have rerun the job several times but it keeps failing with the same error. I'm able to manually upload the deobfuscation file to play store.
The text was updated successfully, but these errors were encountered: