-
Notifications
You must be signed in to change notification settings - Fork 107
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
Can't open category in showcase browser #310
Comments
@oas004 Do you think it could be related to any of your recent changes? |
This is also a suspicious PR that could impact this behavior - #222 |
I tried it out in the sample app in the project, is that screenshot above from the project you sent me @polivmi1 ? Or from another internal project? :) I can't quite imagine what can cause this, but I will debug it further |
I tried also removing all the typography as that is in the screenshot, but I can't reproduce it :( |
@oas004 I have quickly tried adding more stuff to the sample (+fixing the context to run it) and with colors or more previews and combinations I wasn't able to reproduce. I guess there will be some preview composable that has problems. Is there any way to allow or see more logs from Showkase? I will try tomorrow to see if I can reduce my project to the way when it starts to work... |
I was able to reproduce same crash as mentioned by the author. Still can't get a smaller reproducible sample. I wonder if this is correct "uri=android-app://androidx.navigation/SHOWKASE_CATEGORIES" and shouldn't it have the app package name there.
|
Reverting the showkase version shows the same problem, so it isn't a 1.0.0-beta18 problem, but some project configuration that got updated and broke the showkase lib navigation. (previously it worked with 1.0.0-beta17) |
@oas004 this is related to https://github.com/raamcosta/compose-destinations/releases where most likely some dependencies got overwritten due to mismatching compose or other setup versions. That then caused this strange behavior. 1.8.36-beta of that library doesn't work, but 1.8.38-beta works normally. (same will be most likely with the native compose destination or accompanist dependency) |
hmm, okay. I don't know if I quite got that. Is it because you are using the compose-destination library and we are transitively downgrading it? 🤔 |
I managed to find the cause for this problem. Recently in my project there was libraries update, which caused showkase to stop working correctly. I checked all of them and it seems that updating accompanist from 0.29.1-alpha to 0.29.2-rc and navigation-compose from 2.6.0-alpha05 to 2.6.0-alpha07 are what caused the issue. Reverting those updates fixed it. |
I encountered the same issue and none of the suggested solutions worked for me. However, I found a solution that resolved the problem, and I'd like to share it in case it helps others facing a similar issue. I'm using Showkase version The issue was related to the navigation-compose library (I also have Accompanist, but it wasn't causing the problem). I initially had version @vinaygaba |
When I open showkase browser I can see categories correctly, but when I click on one, the screen title changes, but rest of the screen stays the same, still showing the same categories. Then no matter how many times I click on category - nothing changes. When I press physical back button, the app crashes. Error I see:
E/MessageQueue-JNI: java.lang.IllegalArgumentException: Navigation destination that matches request NavDeepLinkRequest{ uri=android-app://androidx.navigation/SHOWKASE_CATEGORIES } cannot be found in the navigation graph NavGraph(0x0) startDestination={Destination(0x7bb10103) route=COMPONENT_GROUPS}
I would really appreciate some help.
The text was updated successfully, but these errors were encountered: