[bkuhl]

Since <native:emoji-picker> (#180), an app that also uses nativephp/mobile-scanner 1.1.0 no longer compiles on Android. I hit this with mobile-ui main (2bfd783) on nativephp/mobile 4.7:

e: .../com/nativephp/scanner/ScannerActivity.kt:323:58 Cannot access class 'com.google.common.util.concurrent.ListenableFuture'. Check your module classpath for missing or conflicting dependencies.
e: .../ScannerActivity.kt:325:30 Unresolved reference 'addListener'.
e: .../ScannerActivity.kt:349:32 Unresolved reference 'unbindAll'.
e: .../ScannerActivity.kt:350:32 Unresolved reference 'bindToLifecycle'.

Cause

#180 adds androidx.emoji2:emoji2-emojipicker:1.7.0. That artifact pulls in full Guava (com.google.guava:guava:32.0.1-android) only at runtime.

Guava declares com.google.guava:listenablefuture:9999.0-empty-to-avoid-conflict-with-guava. AGP's consistent resolution then applies that version to debugCompileClasspath as well. CameraX's listenablefuture:1.0 becomes the empty stub, and Guava itself isn't on the compile classpath, so ListenableFuture disappears for any code that calls ProcessCameraProvider.getInstance(...).

./gradlew :app:dependencyInsight --configuration debugCompileClasspath --dependency com.google.guava shows:

com.google.guava:listenablefuture:9999.0-empty-to-avoid-conflict-with-guava
   Selection reasons:
      - By constraint: version resolved in configuration ':app:debugRuntimeClasspath' by consistent resolution

Guava's only runtime source is androidx.emoji2:emoji2-emojipicker:1.7.0. The same app compiles on mobile-ui 0.8.0, which has no emoji picker, with the same CameraX and scanner dependencies.

Fix

This PR declares Guava next to the emoji picker in nativephp.json so it's on the compile classpath too. It's the same version that's already on the runtime classpath:

"androidx.emoji2:emoji2-emojipicker:1.7.0",
"com.google.guava:guava:32.0.1-android"

I verified this on the Android 16 emulator, with the dependency patched into an app's vendor copy. The build succeeds and the scanner works: scanning opens rounds, and cancelling and denying the camera behave as before.

It also adds a manifest test so the dependency doesn't get dropped later.

🤖 Generated with Claude Code

[bkuhl]

The root cause is in mobile-scanner; this PR only works around it from mobile-ui. It affects mobile-ui 0.9.0, the first release with the emoji picker, whose nativephp.json declares the picker without Guava. I reproduced it with mobile-scanner 1.1.0 on the commits just before 0.9.0 and nativephp/mobile 4.7.0 (mobile-ui 2bfd783, mobile 52de189); neither release changes these dependencies.

ScannerActivity.kt calls ProcessCameraProvider.getInstance(this).addListener(...), which uses Guava's ListenableFuture. mobile-scanner doesn't declare a dependency that provides that class. It compiles only because CameraX pulls in com.google.guava:listenablefuture:1.0.

That breaks as soon as any library adds full Guava at runtime only:

• Guava swaps listenablefuture for its empty 9999.0-empty-to-avoid-conflict-with-guava artifact.
• AGP's consistent resolution carries that onto the compile classpath, so ListenableFuture disappears.

The emoji picker (#180) is the first library to do this, but another plugin or an app's own dependencies could do the same. Fixing it here protects scanner users only from the emoji picker.

The proper fix is for mobile-scanner to declare the dependency it uses, e.g. com.google.guava:guava:32.0.1-android in its nativephp.json. I'd have opened that PR instead, but mobile-scanner's source isn't public. This PR keeps mobile-ui building for scanner users until mobile-scanner gets that fix. Close it once it does.