Hello! We're trying to UI test our app that uses ...

# compose-destinations

[Nacho Ruiz Martin]

Hello!

We're trying to UI test our app that uses Compose Destinations. We don't want to test the navigation itself, because these are integration tests so what we do is we let the app work in the same way it does normally but we touch buttons and assert stuff.

The navigation in our app works as expected when run as a normal app but it's not working at all when run through a UI test. Only the first destination is displayed and further calls to navigate are ignored.

What could be the root issue here?
Thanks!

[Nacho Ruiz Martin]

@Rafael Costa
Sorry for the direct ping.
Do you reckon this be a bug on Navigation Component instead?

[Rafael Costa]

Hi @Nacho Ruiz Martin
I don't know, I would need more information. What steps have you taken to try and get to root cause?

[Rafael Costa]

I really doubt it's something on Compose Destinations library 🤔

[Rafael Costa]

but, is there a crash, logs, something?

[Nacho Ruiz Martin]

Yep, it sounds weird to me too, that’s why I asked.

No logs 😞 , it just doesn’t navigate.

At first, it wasn’t showing the start destination either, but we updated to the latest Compose Destinations v1 version + latest Compose BOM and it’s now displaying the starting one, but not the following.

[Nacho Ruiz Martin]

Let me remove Compose Destinations and try to make it work with vanilla NavComponent.

[Rafael Costa]

are you using onlyIfResumed parameter when calling navigate methods of Compose Destinations?

[Nacho Ruiz Martin]

No, we are not.

[Nacho Ruiz Martin]

It’s indeed happening with vanilla NavComponent 🥲