File Exchange is not picking up toolbox file on new releases

I've connected File Exchange to my github account and am using it to track releases of a toolbox. My toolbox is packaged and added to the release but File Exchange is not picking it up. It had been working for a few releases before but on one release it didn't connect and I ended up deleting the File Exchange post, giving my toolbox a new uuid, and re-publishing it. It collected the toolbox on the initial release, but I just pushed a new release and the mltbx file is not showing up again. Is there anyway to debug this? I don't see an option to manually upload the toolbox either.

[Walter Roberson]

(I have brought this to the attention of some back channels.)

[Randy Souza]

Hi David, so sorry for the trouble. I am looking into this and will update here once I have more information.

[Randy Souza]

Hi David, I was able to get the toolbox attached to version 0.1.8 of matlab-igraph in File Exchange. Do you recall whether, when you created the release in GitHub, you saved the release and then attached the toolbox file, or attached the toolbox file while creating the release? Feel free to contact me directly (firstinitiallastname at mathworks.com) if it's faster/easier.

[DGM]

I've had what seem like similar problems before, but I don't use mtlbx files, so I don't know if it's relevant. I was able to fix it by simply re-asserting the repository location on the FEX page.

https://www.mathworks.com/matlabcentral/answers/1993513-fex-submission-not-updating-to-new-release-on-github#answer_1270738

If that's unrelated, then just ignore it.

[David Connell]

Hey DGM, I tried something similar without success. For me, the new release was created on FEX but only the source file zip was attached. When I tried to re-release it from the edit page I couldn't without incrementing the version number, which is hard coded into the release. I also tried making a phony release but when it got picked up by FEX it once again only grabbed the zip file and not the toolbox.

Randy, I did send an email so if you didn't get it let me know and I can post it here instead. But yes the toolbox was attached when creating the release in the same manner it had been in previous successful uploads.

[David Connell]

@Randy Souza having the issue again. It grabbed the toolbox for 0.1.9 but didn't for 0.1.10. Releases are automated with github actions so the files will always always be attached at the same time, before the release.

[David Connell]

@Randy Souza I'm still having this problem. The toolbox is atteched to the release at creation not afterwards.

[Randy Souza]

@David Connell Sorry that this problem is recurring. I will look into it and reply here.

[Randy Souza]

@David Connell - I've updated your File Exchange submission so that the toolbox is now attached.

I believe that I've identified the cause of the problem, though not yet a solution.

As far as I can tell the problem is that GitHub does not provde a way to create a release and attach files to the release (in this case the .mltbx file) at the same time. So, some of the time:

1. The GitHub Action that you are using to create releases starts.
2. The Action creates the release.
3. GitHub sends a "release created" webhook event to File Exchange.
4. File Exchange updates your submission with the source code for the new release.
5. The Action attaches the .mltbx file to the release
6. GitHub does not send webhook events when files are attached to releases, so File Exchange is never notified that the .mltbx file is available.

In most cases, step #5 occurs before step #4, so when File Exchange updates the submission we can "see" the attached .mltbx file. But when it does not happen in that order, it looks like we end up not picking up the toolbox.

I'll continue to investigate and work with GitHub. I'll update this post when I have a more stable solution.

[David Connell]

The file is attached immediately after the release so add a pause in the update function to ensure the release is complete. It should only require ~100ms. Otherwise can add an action to directly submit to FEX rather than going through github releases like pypi does (publishing to pypi). That would require a command line tool for pushing releases, which I don't think exists at the moment, and a way to authenticate it with github's tokens.

Also the reason the toolbox was getting picked up in previous releases is I had been manually creating the releases to get around this. I think it's less often than not that the toolbox is attached before FEX creates the submission in the automated release case.