[Beta] How do I depend from the development version of an app?

[stefano.menci]

I am not able to depend from the development version of an app.

I have tried the following steps, including a few variations at step 5 where I did or did not publish master, but the result is that the dependent app is always executing the master branch.

Create the dependency:

1. Create a new Material Design app and name it App1
2. Delete Form1
3. Add a module
4. Delete all the code in Module1 and type print('master')
5. Right click on the master branch and click on Publish master branch
6. Right click on the master branch, click on Create branch here... and create the dev branch
7. Change print('master') into print('dev')

Create the dependent:

1. Create another app
2. Add the dependency to the Published version of App1
3. Add import App1.Module1 to the code of Form1
4. Run → the console shows master
5. Change the dependency version from Published to Development
6. Run → the console still shows master

[owen.campbell]

I often find I need a step 8 within the dependency - make an explicit commit of your change.

[stefano.menci]

I tried, but didn’t help.

I have other older apps that allow me to depend from the published or the development version correctly, but I’m not able to create two new apps with a process similar to the one described above and depend on the development.

[owen.campbell]

Also, I often have to refresh the browser between 5 and 6 in the dependent app.

[stucork]

In terms of dependencies:

The dependency referred to as Development is always the branch named master.

The dependency referred to as Published is always the branch named published unless there is no branch named published in which case it’s also master.

I think that explains why the dev branch isn’t doing anything here?

This behaviour is inherited from how anvil did dependencies in the classic editor. For different behaviour you’ll probably want to make a feature request.