What I’m trying to do: Make changes to a dependency. The app that uses it still uses a previously published version
What I’ve tried and what’s not working: I make a simple change like changing the text of a print statement, publish, but the app using the dependency app still prints the old text
Code Sample: Have not had time to put one together
I was able to resolve this. The issue was that the published version of the dependency was on a branch. When the branch version was merged into Master and the Master Version published then the changes were recognized. Not sure that is the way it is suppose to work, but I am back to coding business logic…
When you’re using a dependency, you can say whether you want to use the development or published version of the dependency (or a particular version tag, but that doesn’t apply to your case). The development version of the dependency uses the master branch, while the published version of the dependency uses the published branch. Other branches are not used by dependent apps.
Thank you. I did conclude/discover that ‘other branches are not recognized when used as dependent apps’.
The main app was configured to use the published version of the dependency app. The dependency app: had ‘published’ a particular version (commit) of a branch (not ‘master’ and not named ‘published’). I assumed the main app would recognize the ‘published’ version of the dependency app no matter what the branch was called. Looks like my assumption was wrong.
There is a published version AND a ‘published’ branch to consider?
A published version just means that the app is available through a particular URL, and any branch can be published in that sense.
A published dependency works differently, and uses the branch named published. So yeah, dependencies are different.
And, since there was no ‘published’ branch it must default to ‘master’? That would explain why, when the branch was merged, the changes to the dependency were effectively recognized.
That sounds right. In that case, depending on the development or published versions of the dependency are effectively the same.