Closed inhaledesign closed 5 years ago
fastlane-bot
commented
5 years ago It seems like this issue might be related to code signing :no_entry_sign:
Have you seen our new Code Signing Troubleshooting Guide? It will help you resolve the most common code signing issues :+1:
inhaledesign
commented
5 years ago It seems like this issue might be related to code signing
Have you seen our new Code Signing Troubleshooting Guide? It will help you resolve the most common code signing issues
Yes, all of that information appears to be for iOS, which is not my platform.
janpio
commented
5 years ago Per the logfile:
| apk_paths | ["/home/robert/Development/compass/src/androidtests/build/outputs/apk/debug/androidtests-d |
| | ebug.apk", |
| | "/home/robert/Development/compass/src/app/build/outputs/apk/release/app-release.apk"] |Does your gradle call maybe build both those files? Somehow the upload action gets those both APKs, and to upload only the release one it shouldn't.
inhaledesign
commented
5 years ago Yeah I saw that, but I'm at a loss as to how that could be happening (or where to even look tbh).
janpio
commented
5 years ago You will hate that answer, but: Does it happen if you build with gradle on the command line as well? Then this really is not a fastlane problem, but a gradle problem. Probably better asked at StackOverflow or some gradle forum/community.
inhaledesign
commented
5 years ago No that's a fair question. I feel a little dumb for not having checked it already. Will give it a go later and report back.
inhaledesign
commented
5 years ago Here's what I did.
So, not really sure what was going on. Can't get the original issue to replicate.
Incidentally, apk_paths has changed:
| apk_paths | ["/home/robert/Development/compass/src/app/build/outputs/apk/debug/app-debug.apk", | | | "/home/robert/Development/compass/src/app/build/outputs/apk/androidTest/debug/app-debug-an | | | droidTest.apk", | | | "/home/robert/Development/compass/src/app/build/outputs/apk/release/app-release.apk", | | | "/home/robert/Development/compass/src/billingdsl/build/outputs/apk/androidTest/debug/billi | | | ngdsl-debug-androidTest.apk", | | | "/home/robert/Development/compass/src/utils/build/outputs/apk/androidTest/debug/utils-debu | | | g-androidTest.apk", | | | "/home/robert/Development/compass/src/compassapi/build/outputs/apk/androidTest/debug/compa | | | ssapi-debug-androidTest.apk", | | | "/home/robert/Development/compass/src/permissiondsl/build/outputs/apk/androidTest/debug/pe | | | rmissiondsl-debug-androidTest.apk", | | | "/home/robert/Development/compass/src/locationapi/build/outputs/apk/androidTest/debug/loca | | | tionapi-debug-androidTest.apk"]
janpio
commented
5 years ago Try adding a gradle clean in your Fastfile to make sure there are not old artifacts that could be picked up for apk_paths.
inhaledesign
commented
5 years ago I tried that before posting here, didn't help. But yeah, was probably just a pernicious artifact.
janpio
commented
5 years ago Ok, then let's jump into the code:
If both apk an apk_paths is not set, it gets the value from Actions.lane_context[SharedValues::GRADLE_ALL_APK_OUTPUT_PATHS]:
https://github.com/fastlane/fastlane/blob/e8e7a3ed5146a36d9e94731b8457f57b26255e00/fastlane/lib/fastlane/actions/upload_to_play_store.rb#L10-L17
That one is filled by gradle by taking all files from a specific path:
https://github.com/fastlane/fastlane/blob/273f726bced1026601b16f3b717b904c1004cbb0/fastlane/lib/fastlane/actions/gradle.rb#L66-L72
Which means that your gradle calls seems to either create or already find existing a lot more files than we expect.
I think a normal release build doesn't empty that path, so first doing a debug build, then a release build, could cause that - but that doesn't really match what you are describing. Hm.
inhaledesign
commented
5 years ago I'm not sure if it's possible to dig into this issue any longer, since I can't actually replicate the original issue (i.e. everything is working now).
My guess is that when I was having this issue, gradle was failing to overwrite the APK that was created before I added the signing config to the Gradle file.
janpio
commented
5 years ago Ok, I will close this for now - and you just comment again if you encounter this again, then we can open the issue again.
New Issue Checklist
Issue Description
When trying to deploy to the Play Store, I get an error: "[!] Google Api Error: apkDebuggable: APK is marked as debuggable."
I added my code signing config to my Gradle build per this issue, but the error still occurs. It appears that Fastlane is attempting to upload my test APK "[11:23:29]: Preparing apk at path '/home/robert/Development/compass/src/androidtests/build/outputs/apk/debug/androidtests-debug.apk' for upload..."
I'm using the ldefinition from the docs, so unsure what could be going wrong. I've attached a copy of my Gradle build file for the app module. build.gradle.txt
Command executed
fastlane deploy_alpha
Complete output when running fastlane, including the stack trace and command used
Environment