IssueTracker

for the "out" bundle issue, this seems indeed an issue. for the second one reported adding "debugUpdateAPKArtifact" to the path, this WAI as there can more more than one transformer and we need to automatically separate them so they do not use the same output folder. for #3, I will look at it but it might be difficult to change it at this time.

Hello, this is a P1 S1 issue for a while now, and it's blocking us from upgrading to AGP 4.2 and further. What's the current status? And do you have plans to backport it to 4.2.x?

no we don't have a plan to backport this. why is this blocking you from upgrading ?

We sign apk's and bundles via internal service, and i don't know another way to interact with artifacts; Yesterday i ended up with some ugly workaround: https://github.com/avito-tech/avito-android/pull/1085/files#diff-b898cc20fedebe394439bb37ffb91d3366a1f9a6d359dbdebca79af8a079f911 I'd be glad if you'll point me out how can it be done better.

I commented on the merge request but to summarize :

you can set your signing tasks output folder to wherever you need to be :

artifacts.use(target.tasks.signedApkTaskProvider(this)).configure { signedDirProperty.set(File("/path/to/where/you/want/your/signed/files")) }

if you don't set it, then we will set a directory automatically.

Thanks, Jerome!

I checked that we do have correct behavior for FILE based artifacts like bundle :

> Task :app:debugUpdateArtifact
originalArtifact: /usr/local/google/home/jedo/src/studio-main/out/apiTests/Kotlin/bugTest/app/build/intermediates/bundle/debug/signDebugBundle/app-debug.aab
updatedArtifact: /usr/local/google/home/jedo/src/studio-main/out/apiTests/Kotlin/bugTest/app/build/outputs/bundle/debug/app-debug.aab

however, we still seem to not be consistent for the DIRECTORY based artifacts like APK:

> Task :app:debugUpdateAPKArtifact
Input folder: /usr/local/google/home/jedo/src/studio-main/out/apiTests/Kotlin/bugTest/app/build/outputs/apk/debug
Output folder: /usr/local/google/home/jedo/src/studio-main/out/apiTests/Kotlin/bugTest/app/build/intermediates/apk/debug
Input file: /usr/local/google/home/jedo/src/studio-main/out/apiTests/Kotlin/bugTest/app/build/outputs/apk/debug/app-debug.apk

Alex, can you have a look ?

correction, I was not correct about FILE being correct.

Instead of :

updatedArtifact: /usr/local/google/home/jedo/src/studio-main/out/apiTests/Kotlin/bugTest/app/build/outputs/bundle/debug/app-debug.aab

it should be

updatedArtifact: /usr/local/google/home/jedo/src/studio-main/out/apiTests/Kotlin/bugTest/app/build/outputs/app-debug.aab
``

Two requests are created as they are API changes b/241581686 (set artifact name for transformation) and b/241582907 (change string to OutputFile)

Fix will be available in Android Studio F/AGP 8.0 Canary 2 Release

I tried to use it and at first look, it looks like everything works as expected. Thanks!

The big issue is, that the current AGP 7.4.0 is broken. I tried to use this API and it is still broken in 7.4.0, it is probably really in AGP 8 :-(

That must be some really intense testing as we are 10 days later and still nothing on sight. I don't want to be a P2 issue if that's what a P1 is.

My bet is that Google still targets API 32 (or even lower) internally so they don't care and didn't even saw the issue before our report.

This issue is fixed. The fix has been rolled out via GMSCore and will also require using the latest com.google.android.gms:play-services-wearable:18.0.0 release.

Note that you don’t need to add BIND_LISTENER manually, it has been deprecated for a long time and it continue to remain so (read more at https://android-developers.googleblog.com/2016/04/deprecation-of-bindlistener.html).

Appreciate all the feedback and patience.

Hey @comment#23 I can confirm the fix doesn't work. Tested on Pixel 6 Pro running Android 13 and a Pixel Watch running WearOS 3.5, things are working great if my app targets API 32 but doesn't when targetting API 33 using com.google.android.gms:play-services-wearable:18.0.0.

After 4 months of testing, it looks like it's broken.

Well that's possible but I've tested things carefully and targetting API 32 immediately fixes the behavior so I'm confident this is the root cause of the issue

Can you share the configuration code you have for the affected service from your AndroidManifest.xml file?

Sure thing, you can find them both in the commit that rolls back to targetting API 32: https://github.com/benoitletondor/PixelMinimalWatchFace/commit/604bdc2b640431a1216653c65f3bb86feda9a124

Sorry, wrong link:

• https://github.com/benoitletondor/PixelMinimalWatchFace/blob/release/2.2.0/android/companionapp/src/main/AndroidManifest.xml
• https://github.com/benoitletondor/PixelMinimalWatchFace/blob/release/2.2.0/android/watchface/src/main/AndroidManifest.xml

I don't think it's that, it was installed from PlayStore so it's a release one built from command line with a version bump

Maybe there was something wrong but all I did between this build and the new one is roll back to targeting API 32 and things worked immediately so it's strange to me.

As a reminder the fix require an update to Play Services on the device too.

Indeed I can see PlayServices aren't updated on my device, like on a lot of Android devices right now auto-update of apps is broken.

I'll try again with up to date services and I'll let you know.

But that means it's far from production ready as we can't expect all of our users to be up to date right now so I'm glad I rollbacked to API 32 for now.

Which Play Services version is supposed to fix it? We might add a check using PackageManager APIs to direct users to perform the update.

Have you taken into account the situation of Chinese devices? It's hard for them to upgrade the Play Service and there are no official solutions about this issue.

Issue is not yet solved, as we face the exact same problem still.

• Using targetSdk=31 and com.google.android.gms:play-services-wearable:18.1.0: OK
• Using targetSdk=33 and com.google.android.gms:play-services-wearable:18.1.0: NOT OK

When using targetSdk 33, messages are no longer sent from the wearable to the phone (e.g. WearableListenerService.onMessageReceived()) is no longer called.

You do not have the Arabic language. I am not fluent in English

1.1.5.2.5.2.5.1.5.4.4.2