-
Notifications
You must be signed in to change notification settings - Fork 214
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
Layoutlib Bridge initialization failed #489
Comments
I was able to make it work by isolating the paparazzi tests in a new module. Is that required? |
@theomota Can you clarify what you meant about a new module? I just created an Android library module, added paparazzi to it, and I'm seeing this exact same issue. |
@AdamMc331 Sure, let me try to explain what happened step-by-step.
I hope that helps |
Hmm okay. I will give this a try, too! |
@theomota Any chance you can share the build.gradle file of your |
Sure, but it's a pretty regular gradle file.
|
Hmm, well I was still getting the same issue after all. I guess we'll see if one of the maintainers can weigh in in a bit. I'll try to make a reproducible repo that has less fluff. |
Well, this whole plan backfired. I created a brand new project, and the https://github.com/AdamMc331/PaparazziComposeSample I guess I'll try to do some comparisons to see if I can figure out what makes this project different from my other one. |
Yep I'm stumped, it's not a minimal reproducible project but here is my setup: AdamMc331/TOA#146 |
@AdamMc331 You should also try the 1.1.0-SNAPSHOT version. |
Same issue. :( |
@theomota Can you provide a minimal reproduction sample? Is your project also KMM? @AdamMc331 I tried to open your project in AS, but was unable to get it to sync. That said, running from the command line yields a different stack trace than what's posted above. |
Hmm, I wonder if KMM is the issue, though if it's specifically within an Android lib module I'm not sure why that would be the case. |
Sorry, I was not able to create a reproduction sample. |
I'm seeing the |
Paparazzi (read: layoutlib) doesn't support compileSdk 33 at the moment.
This would be a helpful scenario to confirm/eliminate. Can you try and relay your results? |
For the compileSdk 32 issue, you can backport Paparazzi to use earlier platform versions in snapshot tests, like so:
|
@theomota any luck on obtaining a sample repro? |
Closing due to lack of activity. Please re-file with sample repro. |
Any reason this can't be part of the upstream |
Is there any idea if this support will be released soon? |
In my case I was getting the same error no matter the version of the Paparazzi library I was using. My first quick thought was it had something to do with the Apple Silicon architecture like some other cases with other libraries, however it hasn't. Since I successfully achieved to run the sample project provided here. I just tried to find the 7 differences between this project and my personal one. After simplifying it to the maximum, it turns out that applying the JetBrains Kover gradle plugin for code coverage caused the Bridge error. Commenting out that plugin, everything worked as expected (applying the |
Description
I was not able to use the Paparazzi in my projects. I'm always getting the same error, it seems like Paparazzi is crashing during the rendering of my Composables. I've tried different types of combinations changing CompileSDK and lib version, but I'm always getting the same error.
Steps to Reproduce
Using compose version 1.1.1 and testing a simple button.
It fails when I try to run the test with the message
SEVERE: broken: Layoutlib Bridge initialization failed
Additional information:
Log
The text was updated successfully, but these errors were encountered: