Adding Jetpack Compose to Kotlin Android Extensions enabled project breaks the build [166927559]

Fixed

Bug

Status Update

No update yet.

Description

se...@gmail.com

created issue #1

Aug 30, 2020 03:26PM

Android studio: Android Studio 4.2 Canary 8 Build #AI-202.6397.94.42.6787931, built on August 25, 2020 Runtime version: 11.0.7+10-b765.53 amd64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o Windows 10 10.0 GC: G1 Young Generation, G1 Old Generation Memory: 1280M Cores: 12 Non-Bundled Plugins: monokai-pro

Kotlin version: 1.4.0 stable Jetpack Compose version: 1.0.0-alpha01

Adding Jetpack Compose to an existing Android project with enabled kotlin-android-extensions plugin breaks the build.

Kotlin compiler is throwing error: e: java.lang.AssertionError: Unbound symbols not allowed Unbound public symbol for public kotlinx.android.synthetic.main.activity_main/btn_text.<get-btn_text>|-3087750031117865751[0] at org.jetbrains.kotlin.psi2ir.Psi2IrTranslator.generateModuleFragment(Psi2IrTranslator.kt:96) at org.jetbrains.kotlin.backend.jvm.JvmBackendFacade.doGenerateFiles(JvmBackendFacade.kt:87) at org.jetbrains.kotlin.backend.jvm.JvmIrCodegenFactory.generateModule(JvmIrCodegenFactory.kt:40) at org.jetbrains.kotlin.codegen.KotlinCodegenFacade.compileCorrectFiles(KotlinCodegenFacade.java:35) at org.jetbrains.kotlin.cli.jvm.compiler.KotlinToJVMBytecodeCompiler.generate(KotlinToJVMBytecodeCompiler.kt:616) at org.jetbrains.kotlin.cli.jvm.compiler.KotlinToJVMBytecodeCompiler.compileModules$cli(KotlinToJVMBytecodeCompiler.kt:203) at org.jetbrains.kotlin.cli.jvm.K2JVMCompiler.doExecute(K2JVMCompiler.kt:164) at org.jetbrains.kotlin.cli.jvm.K2JVMCompiler.doExecute(K2JVMCompiler.kt:51) at org.jetbrains.kotlin.cli.common.CLICompiler.execImpl(CLICompiler.kt:86) at org.jetbrains.kotlin.cli.common.CLICompiler.execImpl(CLICompiler.kt:44) at org.jetbrains.kotlin.cli.common.CLITool.exec(CLITool.kt:98) at org.jetbrains.kotlin.incremental.IncrementalJvmCompilerRunner.runCompiler(IncrementalJvmCompilerRunner.kt:346) at org.jetbrains.kotlin.incremental.IncrementalJvmCompilerRunner.runCompiler(IncrementalJvmCompilerRunner.kt:102) at org.jetbrains.kotlin.incremental.IncrementalCompilerRunner.compileIncrementally(IncrementalCompilerRunner.kt:240) at org.jetbrains.kotlin.incremental.IncrementalCompilerRunner.access$compileIncrementally(IncrementalCompilerRunner.kt:39) at org.jetbrains.kotlin.incremental.IncrementalCompilerRunner$compile$2.invoke(IncrementalCompilerRunner.kt:81) at org.jetbrains.kotlin.incremental.IncrementalCompilerRunner.compile(IncrementalCompilerRunner.kt:93) at org.jetbrains.kotlin.daemon.CompileServiceImplBase.execIncrementalCompiler(CompileServiceImpl.kt:601) at org.jetbrains.kotlin.daemon.CompileServiceImplBase.access$execIncrementalCompiler(CompileServiceImpl.kt:93) at org.jetbrains.kotlin.daemon.CompileServiceImpl.compile(CompileServiceImpl.kt:1633) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at java.rmi/sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:359) at java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:200) at java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:197) at java.base/java.security.AccessController.doPrivileged(Native Method) at java.rmi/sun.rmi.transport.Transport.serviceCall(Transport.java:196) at java.rmi/sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:562) at java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:796) at java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:677) at java.base/java.security.AccessController.doPrivileged(Native Method) at java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:676) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834)

FAILURE: Build failed with an exception.

See minimal reproducing sample project in attachments.

JB team been notified as well: https://youtrack.jetbrains.com/issue/KT-41501

IssueSample.zip

988 KB

Download

Comments

pi...@gmail.com <pi...@gmail.com> #2Aug 30, 2020 03:38PM

Further information:

So, I made a test project with a blank wordpress app and a new yaml file and deployed it. It did not stop immediately like it has been with the ascii error, but it did give me a timeout error, which I would get 4 out of 5 times when the app was deploying.

Since it didn't get an ascii error, I took the contents of the app.yaml file and pasted it in the new test instance. That also did not give me an ascii error on deploy, but did get the timeout error.

Since that did not hang on an ascii error, I thought it was not my original app.yaml file that was the issue, which made me think that it was an issue in the project file name or something, so I took the contents of the new yaml file and tried to deployed my original app with that, and that also did not hang on an ascii file but did get the timeout error.

So, I don't know what is causing the timeout error, but it appears that the ascii problem is not my original app.yaml file nor is it a file name in my project, but something is happening when they are deployed together. I'm quite confused.

sh...@gmail.com <sh...@gmail.com> #3Sep 3, 2020 06:56AM

I have been able to make the ascii error go away by removing these lines...

```
skip_files:
- ^(.*/)?\.zip$
- ^(.*/)?\.bat$
- ^(.*/)?\.sh$
- ^(.*/)?\.md$
```

I am not sure why this would be causing the issue. None of those items showed up when I did a regex search across my project for non-ascii characters.

Also, I am not sure why I was able to start the deploy and not get the ascii error in the text project, as this text was in the app.yaml file at the time of testing.

cl...@google.com <cl...@google.com> Oct 6, 2020 10:28AM

Assigned to ag...@google.com.

ag...@google.com <ag...@google.com> #4Oct 6, 2020 01:06PM

Reassigned to st...@google.com.

This is happening every time now though...

Beginning deployment of service [default]...
Some files were skipped. Pass `--verbosity=info` to see which ones.
You may also view the gcloud log file, found at
[/Users/me/.config/gcloud/logs/2018.06.08/16.12.18.352564.log].
╔════════════════════════════════════════════════════════════╗
╠═ Uploading 1 file to Google Cloud Storage ═╣
╚════════════════════════════════════════════════════════════╝
ERROR: gcloud crashed (MultiError): One or more errors occurred:
MaxRetrialsException: last_result=(None, (<class 'socket.error'>, error(60, 'Operation timed out'), <traceback object at 0x10de05908>)), last_retrial=3, time_passed_ms=1188103,time_to_wait=0

st...@google.com <st...@google.com> #5Oct 6, 2020 01:59PM

Marked as fixed.

Thanks for the report and the clarification. I tried to use your “skip_files” element and reproduce the issue but I could deploy my app successfully. If the issue still persists, could you perform the 'gcloud app deploy' deployment again with the '--verbosity=debug' and '--no-user-output-enabled' options [1] and attach the full output here?

[1]

https://cloud.google.com/sdk/gcloud/reference/

Issue 166927559